Skip to main content ↑ ↓
Topic solved
This topic has been marked as solved and requires no further attention.
Topic: LXQt nm-applet missing [SOLVED] (Read 5613 times) previous topic - next topic
0 Members and 4 Guests are viewing this topic.

Re: LXQt nm-applet missing

Reply #45 –
To give you a headstart as going from the username only you're fairly new to all of this ?
Code: [Select]
pacman -Ql networkmanager
shows all the files installed by networkmanager.
Of immediate interest
Quote
networkmanager /usr/bin/NetworkManager
networkmanager /usr/bin/nm-online
networkmanager /usr/bin/nmcli
networkmanager /usr/bin/nmtui
networkmanager /usr/bin/nmtui-connect
networkmanager /usr/bin/nmtui-edit
networkmanager /usr/bin/nmtui-hostname
shows the programs installed by networkmanager
nmtui I imagine would be a Text User Interface (tui), have a play.
Quote
networkmanager /etc/NetworkManager/
networkmanager /etc/NetworkManager/NetworkManager.conf
networkmanager /etc/NetworkManager/conf.d/
networkmanager /etc/NetworkManager/dispatcher.d/
networkmanager /etc/NetworkManager/dispatcher.d/no-wait.d/
networkmanager /etc/NetworkManager/dispatcher.d/pre-down.d/
networkmanager /etc/NetworkManager/dispatcher.d/pre-up.d/
networkmanager /etc/NetworkManager/dnsmasq-shared.d/
networkmanager /etc/NetworkManager/dnsmasq.d/
networkmanager /etc/NetworkManager/system-connections/
shows the configuration files locations as installed. That's not to say others might not have been created? Normally under ~/..config
Quote
networkmanager /usr/share/man/man1/nm-online.1.gz
networkmanager /usr/share/man/man1/nmcli.1.gz
networkmanager /usr/share/man/man1/nmtui-connect.1.gz
networkmanager /usr/share/man/man1/nmtui-edit.1.gz
networkmanager /usr/share/man/man1/nmtui-hostname.1.gz
networkmanager /usr/share/man/man1/nmtui.1.gz
networkmanager /usr/share/man/man5/
networkmanager /usr/share/man/man5/NetworkManager.conf.5.gz
networkmanager /usr/share/man/man5/nm-settings-dbus.5.gz
networkmanager /usr/share/man/man5/nm-settings-keyfile.5.gz
networkmanager /usr/share/man/man5/nm-settings-nmcli.5.gz
networkmanager /usr/share/man/man5/nm-settings.5.gz
networkmanager /usr/share/man/man5/nm-system-settings.conf.5.gz
networkmanager /usr/share/man/man7/
networkmanager /usr/share/man/man7/nm-openvswitch.7.gz
networkmanager /usr/share/man/man7/nmcli-examples.7.gz
networkmanager /usr/share/man/man8/
networkmanager /usr/share/man/man8/NetworkManager-dispatcher.8.gz
networkmanager /usr/share/man/man8/NetworkManager.8.gz
networkmanager /usr/share/man/man8/nm-initrd-generator.8.gz
shows the man pages available.

So if you wanted to know more about nmtui
Code: [Select]
man nmtui
If you wanted to know more about NetworkManager.conf
Code: [Select]
man NetworkManager.conf

Re: LXQt nm-applet missing

Reply #46 –
would it be fair for me to suggest that most of networkmanager man assumes systemd.

So how useful is that to me?

Re: LXQt nm-applet missing

Reply #47 –
Quote from: n00b – on
would it be fair for me to suggest that most of networkmanager man assumes systemd.

So how useful is that to me?
My point was that a lot of the info you'll find on the net will assume systemd. So searching out a solution will prove more challenging when not using systemd.

But nm-applet is a front end to networkmanager. If you run
Code: [Select]
pacman -Qi nm-applet
you'll see it depends on networkmanager.
So if nm-applet is not working it's quite likely that networkmanager is not working.

Unless someone else pops up with the knowledge, you may have to use net searches, logs and man pages to help you troubleshoot your issue. Which is why I gave you some hints. man pages are very useful.

Have you tried running
Code: [Select]
sudo nmtui
and seeing what happens ?

Re: LXQt nm-applet missing

Reply #48 –
Quote from: gripped – on
My point was that a lot of the info you'll find on the net will assume systemd. So searching out a solution will prove more challenging when not using systemd.

But nm-applet is a front end to networkmanager. If you run
Code: [Select]
pacman -Qi nm-applet
you'll see it depends on networkmanager.
So if nm-applet is not working it's quite likely that networkmanager is not working.

Unless someone else pops up with the knowledge, you may have to use net searches, logs and man pages to help you troubleshoot your issue. Which is why I gave you some hints. man pages are very useful.

Have you tried running
Code: [Select]
sudo nmtui
and seeing what happens ?

afaict nmtui us the same as nm-connection-editor

Both can see my wired connection and VPN.

If the premise is NM is broken, how do i confirm it is not?

Re: LXQt nm-applet missing

Reply #49 –
Quote from: n00b – on
afaict nmtui us the same as nm-connection-editor

Both can see my wired connection and VPN.
I read from this that nmtui CANNOT see the wifi networks which iwlist wlan0 scan could ?
Quote
If the premise is NM is broken, how do i confirm it is not?
If it's not showing the wifi networks then it's not working correctly.
I've already told you, find the location it's logging to, Edit the config file to increase the log level. Look in /var/log. Start with /var/log/daemon.log  & /var/log/messages.log
I did ask what init you are using and if you were sure the networkmanager service was enabled but don't recall an answer to that.
But another way to approach it would be to stop the service (how depends on your init) and then run networkmanager on the command line, in a terminal, in the foreground. That way you'll see the output.
Code: [Select]
/usr/bin/NetworkManager --no-daemon --log-level=INFO
You could also try DEBUG as a log level (though probably overkill and likely to confuse.)

Re: LXQt nm-applet missing

Reply #50 –
Quote from: gripped – on
I read from this that nmtui CANNOT see the wifi networks which iwlist wlan0 scan could ?If it's not showing the wifi networks then it's not working correctly.
yes, and neither can  nm-connection-editor
Quote from: gripped – on
I've already told you, find the location it's logging to, Edit the config file to increase the log level. Look in /var/log. Start with /var/log/daemon.log  & /var/log/messages.log
Quote from: gripped – on
Code: [Select]
/usr/bin/NetworkManager --no-daemon --log-level=INFO
You could also try DEBUG as a log level (though probably overkill and likely to confuse.)
Ran this first. here is some log, right after removal and reinsert of the USB wifi dongle

Jun  9 09:47:33 box NetworkManager[5772]: <info>  [1654782453.5733] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun  9 13:49:50 box rtkit-daemon[2826]: Supervising 8 threads of 7 processes of 1 users.
Jun  9 13:49:50 box rtkit-daemon[2826]: Supervising 8 threads of 7 processes of 1 users.
Jun  9 14:04:37 box rtkit-daemon[2826]: Supervising 8 threads of 7 processes of 1 users.
Jun  9 14:04:37 box rtkit-daemon[2826]: Supervising 8 threads of 7 processes of 1 users.
Jun  9 14:05:13 box rtkit-daemon[2826]: Supervising 8 threads of 7 processes of 1 users.
Jun  9 14:05:13 box rtkit-daemon[2826]: Supervising 8 threads of 7 processes of 1 users.
Jun  9 14:09:45 box rtkit-daemon[2826]: Supervising 8 threads of 7 processes of 1 users.
Jun  9 14:09:45 box rtkit-daemon[2826]: Supervising 8 threads of 7 processes of 1 users.
Jun  9 10:13:42 box NetworkManager[15225]: <info>  [1654784022.2474] NetworkManager (version 1.38.0-1) is starting... (after a restart)
Jun  9 10:13:42 box NetworkManager[15225]: <info>  [1654784022.2475] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Jun  9 10:13:42 box NetworkManager[15225]: <warn>  [1654784022.2475] config: state: error reading state file "/var/lib/NetworkManager/NetworkManager.state": Permission denied
Jun  9 10:13:42 box NetworkManager[15225]: <error> [1654784022.2489] bus-manager: fatal failure to acquire D-Bus service "org.freedesktop.NetworkManager: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Connection ":1.195" is not allowed to own the service "org.freedesktop.NetworkManager" due to security policies in the configuration file
Jun  9 10:13:42 box NetworkManager[15225]: <info>  [1654784022.2489] exiting (error)
Jun  9 10:16:27 box NetworkManager[5772]: <info>  [1654784187.7916] dhcp6 (eth0): state changed new lease, address=2600:1702:2ff0:d630::c

Is that error interesting?

Is it odd the time is wrong and out of order? "Jun  9 14:04:37 " is in the future.

Quote from: gripped – on
I did ask what init you are using and if you were sure the networkmanager service was enabled but don't recall an answer to that.
Mentioned a few times it is OpenRC, and the log shows network manager is working, yes?
Quote from: gripped – on
But another way to approach it would be to stop the service (how depends on your init) and then run networkmanager on the command line, in a terminal, in the foreground. That way you'll see the output.
better to use log, or do it manually?

Re: LXQt nm-applet missing

Reply #51 –
Quote from: n00b – on
Mentioned a few times it is OpenRC,
Sorry, I did say I'd only skimmed the thread up until the point I jumped on.
Quote
and the log shows network manager is working, yes?
Depends how you define working? AFAIK NetworkManger should be automatically scanning for local wifi and allowing you to connect to them. As none show up in nmtui then I'd say it not working as intended even if running.  I just tried nmtui (I'd never even heard of it before this thread) on my chromebook and from the 1st page "Activate connections" then shows a list of all the local wifi networks.
Quote
better to use log, or do it manually?
I don't think that matters though if me I'd do it manually and then check the logs as well to see if there's anything extra in there.
What is important is to make sure the NetworkManger service is not running before you do start it manually.

It would make this easier if you could put both the command as you entered it and the output in code tags when you are posting.
It's easier to read but also I'm sure what command you entered.

If you get the same output when sure only a single instance of NetworkManager is running then we can see you have a warning followed by an error
Code: [Select]
Jun  9 10:13:42 box NetworkManager[15225]: <warn>  [1654784022.2475] config: state: error reading state file "/var/lib/NetworkManager/NetworkManager.state": Permission denied
Jun  9 10:13:42 box NetworkManager[15225]: <error> [1654784022.2489] bus-manager: fatal failure to acquire D-Bus service "org.freedesktop.NetworkManager:
I've a feeling the warning may be a problem, NetworkManager should be able to read (and write) it's own files.
But I suspect the error is simply because NetworkManager is already running before you start it again manually. The warning maybe the same issue though?
Code: [Select]
rc-service NetworkManager stop
before running manually.

Unfortunately I'm not sure how much more I can help as not having NetworkManager on Artix I don't know how it should be working compared to the NetworkManager I have on arch.

But if no one else jumps in I'll try!

If me I'd be tempted to purge NetworkManager, its config files and dependencies and then reinstall.


Edit: Just had a thought. Probably my fault.
Code: [Select]
/usr/bin/NetworkManager --no-daemon --log-level=INFO
should have been
Code: [Select]
sudo /usr/bin/NetworkManager --no-daemon --log-level=INFO
so if you ran as a normal user that would explain the permissions error.




Re: LXQt nm-applet missing

Reply #52 –
sudo /usr/bin/NetworkManager --no-daemon --log-level=INFO

was the issue, it ran without error after that.

Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3754] NetworkManager (version 1.38.0-1) is starting... (after a restart)
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3755] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3776] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3831] manager[0x5643b4749020]: monitoring kernel firmware directory '/lib/firmware'.
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3841] hostname: hostname: using hostnamed
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3841] hostname: static hostname changed from (none) to "localhost"
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3844] dns-mgr[0x5643b4718450]: init: dns=default,systemd-resolved rc-manager=symlink
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3851] manager[0x5643b4749020]: rfkill: Wi-Fi hardware radio set enabled
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3851] manager[0x5643b4749020]: rfkill: WWAN hardware radio set enabled
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3886] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-bluetooth.so)
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3888] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-wifi.so)
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3940] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-team.so)
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3942] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-wwan.so)
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3945] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-ovs.so)
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3947] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-adsl.so)
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3949] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3950] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3950] manager: Networking is enabled by state file
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3952] settings: Loaded settings plugin: keyfile (internal)
Jun  9 17:43:27 box dbus-daemon[1669]: [system] Activating service name='org.freedesktop.nm_dispatcher' requested by ':1.261' (uid=0 pid=29533 comm="/usr/bin/NetworkManager --no-daemon --log-level=IN") (using servicehelper)
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3971] dhcp-init: Using DHCP client 'internal'
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3971] device (lo): carrier: link connected
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3974] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3982] device (eth0): carrier: link connected
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3986] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)

and so on.

So, no errors, and it says it is monitoring... directory '/lib/firmware'

I saw networkmanager and nm-applet had an update, and hoped that helped, but no

Re: LXQt nm-applet missing

Reply #53 –
Quote from: n00b – on
and so on.
No worries but don't 'And so on'.
Paste the lot. And please in code tags. Helps my eyes. I'm an old man :) You just select it all and click the '#' to the left above the smilies. Or upload to pastebin and paste a link.

Because at the end you have
Code: [Select]
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3971] device (lo): carrier: link connected
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3974] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3982] device (eth0): carrier: link connected
Jun  9 17:43:27 box NetworkManager[29533]: <info>  [1654811007.3986] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
No mention of wlan0
Also once it's running click on your applet. Start nmtui in another terminal and select 'Activate connections'. There may be extra, possibly relevant, output. Also there may not be ;)

Edit:
Also post the output of 
Code: [Select]
rc-update show
please

Re: LXQt nm-applet missing

Reply #54 –
sudo rc-service NetworkManager stop
NetworkManager    | * Stopping NetworkManager ...                                                                                                                                                            [ ok ]

sudo rc-service NetworkManager start
NetworkManager    | * Starting NetworkManager ...                                                                                                                                                            [ ok ]
Connecting...............    1s [online]

posted all after the start of
/var/log/daemon.log

Code: [Select]
Jun 10 09:09:06 box NetworkManager[4166]: <info>  [1654866546.7988] exiting (success)
Jun 10 09:09:06 box /etc/init.d/NetworkManager[5299]: status: stopping
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9228] NetworkManager (version 1.38.0-1) is starting... (after a restart)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9229] Read config: /etc/NetworkManager/NetworkManager.conf (lib: 20-connectivity.conf)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9243] bus-manager: acquired D-Bus service "org.freedesktop.NetworkManager"
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9308] manager[0x55d2fcf9d020]: monitoring kernel firmware directory '/lib/firmware'.
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9320] hostname: hostname: using hostnamed
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9320] hostname: static hostname changed from (none) to "localhost"
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9323] dns-mgr[0x55d2fcf75a50]: init: dns=default,systemd-resolved rc-manager=symlink
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9335] rfkill1: found Wi-Fi radio killswitch (at /sys/devices/pci0000:00/0000:00:09.0/0000:02:00.0/usb8/8-1/8-1.1/8-1.1.1/8-1.1.1:1.0/ieee80211/phy0/rfkill1) (driver rtl8812au)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9338] manager[0x55d2fcf9d020]: rfkill: Wi-Fi hardware radio set enabled
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9338] manager[0x55d2fcf9d020]: rfkill: WWAN hardware radio set enabled
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9374] Loaded device plugin: NMBluezManager (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-bluetooth.so)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9376] Loaded device plugin: NMWifiFactory (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-wifi.so)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9428] Loaded device plugin: NMTeamFactory (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-team.so)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9429] Loaded device plugin: NMWwanFactory (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-wwan.so)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9433] Loaded device plugin: NMOvsFactory (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-ovs.so)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9435] Loaded device plugin: NMAtmManager (/usr/lib/NetworkManager/1.38.0-1/libnm-device-plugin-adsl.so)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9437] manager: rfkill: Wi-Fi enabled by radio killswitch; enabled by state file
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9438] manager: rfkill: WWAN enabled by radio killswitch; enabled by state file
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9438] manager: Networking is enabled by state file
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9440] settings: Loaded settings plugin: keyfile (internal)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9455] dhcp-init: Using DHCP client 'internal'
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9456] device (lo): carrier: link connected
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9458] manager: (lo): new Generic device (/org/freedesktop/NetworkManager/Devices/1)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9467] device (eth0): carrier: link connected
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9472] manager: (eth0): new Ethernet device (/org/freedesktop/NetworkManager/Devices/2)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9476] manager: (eth0): assume: will attempt to assume matching connection 'Wired connection 1' (8b68f201-8d59-3d7e-bf66-a34fac8f29c8) (indicated)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9477] device (eth0): state change: unmanaged -> unavailable (reason 'connection-assumed', sys-iface-state: 'assume')
Jun 10 09:09:09 box NetworkManager[5334]: <warn>  [1654866549.9480] device (eth0): connectivity: "/proc/sys/net/ipv4/conf/all/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9482] device (eth0): state change: unavailable -> disconnected (reason 'connection-assumed', sys-iface-state: 'assume')
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9502] device (eth0): Activation: starting connection 'Wired connection 1' (8b68f201-8d59-3d7e-bf66-a34fac8f29c8)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9507] device (wlan0): driver supports Access Point (AP) mode
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9516] manager: (wlan0): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/3)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9519] device (wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9541] device (wlan0): set-hw-addr: set MAC address to DA:0D:78:83:74:37 (scanning)
Jun 10 09:09:09 box NetworkManager[5334]: <warn>  [1654866549.9545] device (wlan0): connectivity: "/proc/sys/net/ipv4/conf/all/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9551] device (wlan1): driver supports Access Point (AP) mode
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9555] manager: (wlan1): new 802.11 Wi-Fi device (/org/freedesktop/NetworkManager/Devices/4)
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9558] device (wlan1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9569] device (wlan1): set-hw-addr: set MAC address to A6:B8:F2:61:02:5E (scanning)
Jun 10 09:09:09 box NetworkManager[5334]: <warn>  [1654866549.9573] device (wlan1): connectivity: "/proc/sys/net/ipv4/conf/all/rp_filter" is set to "1". This might break connectivity checking for IPv4 on this device
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9625] ovsdb: disconnected from ovsdb
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9626] device (eth0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'assume')
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9630] device (eth0): state change: prepare -> config (reason 'none', sys-iface-state: 'assume')
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9680] agent-manager: agent[6e12cd8b1656bfe0,:1.26/org.freedesktop.nm-applet/1000]: agent registered
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9681] modem-manager: ModemManager available
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9681] device (eth0): state change: config -> ip-config (reason 'none', sys-iface-state: 'assume')
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9684] dhcp4 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jun 10 09:09:09 box /etc/init.d/NetworkManager[5359]: status: starting
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9831] dhcp4 (eth0): state changed new lease, address=192.168.1.136
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9850] device (eth0): state change: ip-config -> ip-check (reason 'none', sys-iface-state: 'assume')
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9866] device (eth0): state change: ip-check -> secondaries (reason 'none', sys-iface-state: 'assume')
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9868] device (eth0): state change: secondaries -> activated (reason 'none', sys-iface-state: 'assume')
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9870] manager: NetworkManager state is now CONNECTED_LOCAL
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9873] manager: NetworkManager state is now CONNECTED_SITE
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9874] policy: set 'Wired connection 1' (eth0) as default for IPv4 routing and DNS
Jun 10 09:09:09 box NetworkManager[5334]: <info>  [1654866549.9931] device (eth0): Activation: successful, device activated.
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0478] dhcp6 (eth0): activation: beginning transaction (timeout in 45 seconds)
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0483] policy: set 'Wired connection 1' (eth0) as default for IPv6 routing and DNS
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0540] dhcp6 (eth0): state changed new lease, address=2600:1702:2ff0:d630::c
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0578] device (wlan0): supplicant interface state: internal-starting -> disconnected
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0579] Wi-Fi P2P device controlled by interface wlan0 created
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0581] manager: (p2p-dev-wlan0): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/5)
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0584] device (p2p-dev-wlan0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0593] device (wlan1): supplicant interface state: internal-starting -> disconnected
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0593] Wi-Fi P2P device controlled by interface wlan1 created
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0596] manager: (p2p-dev-wlan1): new 802.11 Wi-Fi P2P device (/org/freedesktop/NetworkManager/Devices/6)
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0598] device (p2p-dev-wlan1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0606] device (wlan0): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0610] device (p2p-dev-wlan0): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0613] device (wlan1): state change: unavailable -> disconnected (reason 'supplicant-available', sys-iface-state: 'managed')
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.0617] device (p2p-dev-wlan1): state change: unavailable -> disconnected (reason 'none', sys-iface-state: 'managed')
Jun 10 09:09:10 box NetworkManager[5334]: <info>  [1654866550.2297] manager: NetworkManager state is now CONNECTED_GLOBAL
Jun 10 09:09:30 box NetworkManager[5334]: <info>  [1654866570.7239] device (wlan0): supplicant interface state: disconnected -> inactive
Jun 10 09:09:30 box NetworkManager[5334]: <info>  [1654866570.7240] device (p2p-dev-wlan0): supplicant management interface state: disconnected -> inactive
Jun 10 09:09:30 box NetworkManager[5334]: <info>  [1654866570.7243] manager: startup complete

It seems NetworkManager can see it? but I have no idea what this means
 device (wlan1): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'external')

you asked for
Code: [Select]
rc-update show 
       NetworkManager |      default                           
                acpid |      default                           
          agetty.tty1 |      default                           
          agetty.tty2 |      default                           
          agetty.tty3 |      default                           
          agetty.tty4 |      default                           
          agetty.tty5 |      default                           
          agetty.tty6 |      default                           
               binfmt | boot                                   
           bluetoothd |      default                           
             bootmisc | boot                                   
              cgroups |                                 sysinit
          consolefont | boot                                   
               cronie |      default                           
                 dbus |      default                           
                devfs |                                 sysinit
                dmesg |                                 sysinit
              elogind | boot                                   
                 fsck | boot                                   
             hostname | boot                                   
              hwclock | boot                                   
              keymaps | boot                                   
            killprocs |                        shutdown        
    kmod-static-nodes |                                 sysinit
                local |      default nonetwork                                                                                                                                                                     
           localmount | boot                                                                                                                                                                                       
             loopback | boot                                                                                                                                                                                       
              modules | boot                                                                                                                                                                                       
             mount-ro |                        shutdown                                                                                                                                                            
                 mtab | boot                                                                                                                                                                                       
               net.lo | boot                                                                                                                                                                                       
             netmount |      default                           
         opensysusers | boot                                   
     opentmpfiles-dev |                                 sysinit
   opentmpfiles-setup | boot                                   
               procfs | boot                                   
                 root | boot                                   
         save-keymaps | boot                                   
    save-termencoding | boot                                   
            savecache |                        shutdown        
                 sddm |      default                           
                 swap | boot                                   
               sysctl | boot                                   
                sysfs |                                 sysinit
            syslog-ng |      default                           
         termencoding | boot                                   
                 udev |                                 sysinit
         udev-trigger |                                 sysinit
              urandom | boot                                  

Quote from: gripped – on
No worries but don't 'And so on'.
Acknowledged
Quote from: gripped – on
Also once it's running click on your applet.
I still have no visible applet. And cannot add it to the LXQt panel, and it is not an optional widget to add
But it is running.
Quote from: gripped – on
Start nmtui in another terminal and select 'Activate connections'.
nmtui is not the same as nm-connection-editor
nmtui allowed 'Activate connections'.

WHICH showed the wifi ssids and connecting to them.

THE WIFI WORKS!

SO, while I have an actual wifi connection, I cannot see them on the NM applet.

I can see them on nmtui and nm-connection-editor

EDIT.
On a hunch, i removed the systray and status tray and added them back. and it all appeared as it should.
My guess is the update fixed the problem, but they still require a delete and re-add

Re: LXQt nm-applet missing [SOLVED]

Reply #55 –
Quote from: n00b – on

EDIT.
On a hunch, i removed the systray and status tray and added them back. and it all appeared as it should.
My guess is the update fixed the problem, but they still require a delete and re-add

Cool. Glad you got it working. A version of the old turn it off and on again :D
And maybe picked up a thing or two along the way, which may serve you in the future ?

Re: LXQt nm-applet missing [SOLVED]

Reply #56 –
Many things, yes.

Also thank you for your help.

A version of turn it off, i guess, but I suspect the updates fixed the problem, and needed uninstalled and reinstalled.
I did remove the systray before, to no effect.

I do wish I knew better why it didn't work, and now does.

https://archlinux.org/packages/extra/x86_64/networkmanager/ seems to suggest networkmanager was updated in may, but I thought we just had an update?

So i went looking in pacman.log, and found

[2022-06-08T11:16:27-0400] [ALPM] upgraded nm-connection-editor (1.26.0-1 -> 1.28.0-1)
[2022-06-08T11:16:27-0400] [ALPM] upgraded network-manager-applet (1.26.0-1 -> 1.28.0-1)

So, ya the applet was updated. And Connection-editor.

But I also found this.
[2022-06-08T11:16:31-0400] [ALPM-SCRIPTLET] ==> dkms install --no-depmod rtl8812au/5.13.6.r119.gedb17ca -k 5.18.2-artix1-1
[2022-06-08T11:16:32-0400] [ALPM-SCRIPTLET] Error! Bad return status for module build on kernel: 5.18.2-artix1-1 (x86_64)
[2022-06-08T11:16:32-0400] [ALPM-SCRIPTLET] Consult /var/lib/dkms/rtl8812au/5.13.6.r119.gedb17ca/build/make.log for more information.
[2022-06-08T11:16:32-0400] [ALPM-SCRIPTLET] ==> WARNING: `dkms install --no-depmod rtl8812au/5.13.6.r119.gedb17ca -k 5.18.2-artix1-1' exited 10
[2022-06-08T11:16:32-0400] [ALPM-SCRIPTLET] ==> dkms install --no-depmod rtl8812au/5.13.6 -k 5.18.2-artix1-1
[2022-06-08T11:16:33-0400] [ALPM-SCRIPTLET] Error! Bad return status for module build on kernel: 5.18.2-artix1-1 (x86_64)
[2022-06-08T11:16:33-0400] [ALPM-SCRIPTLET] Consult /var/lib/dkms/rtl8812au/5.13.6/build/make.log for more information.
[2022-06-08T11:16:33-0400] [ALPM-SCRIPTLET] ==> WARNING: `dkms install --no-depmod rtl8812au/5.13.6 -k 5.18.2-artix1-1' exited 10

 /var/lib/dkms/rtl8812au/5.13.6.r119.gedb17ca/build/make.log

DKMS make.log for rtl8812au-5.13.6.r119.gedb17ca for kernel 5.18.2-artix1-1 (x86_64)
Wed Jun  8 11:16:32 EDT 2022
make: uname: No such file or directory
make: pwd: No such file or directory
make ARCH=x86_64 CROSS_COMPILE= -C /lib/modules/5.18.2-artix1-1/build M=  modules
make: pwd: No such file or directory
make: make: No such file or directory
make: *** [Makefile:2514: modules] Error 127

So, it choked on a dkms make after a kernel update?

Should I post this as a driver issue?

P.S. I think I am also showing I did learn a few things that i can use.
Thanks again.
 

Re: LXQt nm-applet missing [SOLVED]

Reply #57 –
Quote from: n00b – on
A version of turn it off, i guess, but I suspect the updates fixed the problem, and needed uninstalled and reinstalled.
That's very possible

Quote
I do wish I knew better why it didn't work, and now does.

From what the rest of your post states there's a chance you do.
Quote
So, it choked on a dkms make after a kernel update?

Should I post this as a driver issue?
I would say that would take a whole lot more testing and investigation, which might be futile if it's been resolved anyway. It's not uncommon for out of kernel - kernel drivers to need patching when the kernel goes up a full point release, which it did recently to 5.18. I'm just guessing though. A way to check that out, if you are curious, is to look at at the recent commits on the drivers github.
Quote
P.S. I think I am also showing I did learn a few things that i can use.
Thanks again.
You're welcome