I think i have this exact problem. https://bbs.archlinux.org/viewtopic.php?id=193980
pgrep nm-applet
2819
So the applet is running it is just not in the tray?
Please Advise
one thing asserted is that that person was missing this package
https://archlinux.org/packages/community/x86_64/lxqt-panel/
and another suggested installing network-manager-applet which is also in the artix repos. have you tried either of those solutions?
sudo pacman -Ss network-manager-applet
world/network-manager-applet 1.26.0-1 [installed]
Applet for managing network connections
extra/network-manager-applet 1.26.0-1 [installed]
Applet for managing network connections
sudo pacman -Ss lxqt-panel
galaxy/lxqt-panel 1.1.0-1 (lxqt) [installed]
The LXQt desktop panel
community/lxqt-panel 1.1.0-1 (lxqt) [installed]
The LXQt desktop panel
both installed, right?
device is here
lsusb
Bus 008 Device 012: ID 0bda:8812 Realtek Semiconductor Corp. RTL8812AU 802.11a/b/g/n/ac 2T2R DB WLAN Adapter
which init are you using?
networkmanager-[your-init]
nm-connection-editor
???
rfkill shows it blocked at all?
sudo pacman -Ss networkmanager-openrc
world/networkmanager-openrc 20210505-6 (openrc-world) [installed]
OpenRC networkmanager init script
rfkill
ID TYPE DEVICE SOFT HARD
0 bluetooth hci0 unblocked unblocked
2 wlan phy1 unblocked unblocked
nm-connection-editor popped the GUI, but no wifi was configured. I can add a wifi, but am unable to discover the ssids
Please Advise
chipset driver is in the aur with or without dkms
RTL8812AU
this is what i cloned and built
https://aur.archlinux.org/packages/rtl88xxau-aircrack-dkms-git
how do i know if the driver is working?
it seems...
https://aur.archlinux.org/packages/rtl88xxau-aircrack-dkms-git#comment-867269
It appears that after the release of kernel 5.18 this module does not build; in the interim, downgrading to 5.17.9 allows me to continue to use my WiFi adapter.
weird, it built without errors for me
Ok, i see, i should have got this https://aur.archlinux.org/rtl8812au-dkms-git.git
Do i need to uninstall the last one before i build the proper driver?
new build removed the other one
Do i have to restart a service now?
restart, logout, in, reboot. anything you like
is it working now?
no
I got a pop up on first reboot that wireless networks were available, but clicking view connections did nothing and still no applet in the tray. that popup never reappeared.
when i plug in wired connection to post answer, the system will take instructions, but all hang i have to reboot to do anything.
Any thoughts on how to get the NM-applet to work on Artix LXQt?
i doubt this is going to help, but you do have "system tray" as a widget '(right click bar and manage widgets) cause thats what allows "old" applets, mine went a bit f'd up when lxqt upgraded, but adding this sorted it (along with a couple of others like the battery indicator and stuff). One way to know if it is due to the lxqt upgrade is whether it was there when you first installed (from the tested .iso) and could connect then, which I'm assuming was the case as that allowed a connection to do a full upgrade that resulted in this now. I just checked my notes and i didn't have to install anything new for networking when i first installed btw |(that's with dinit, not that that would make any difference i think)
(https://bayimg.com/8d83461806287950519feffeba58201c66063276.jpg)
Its there. the networkManager widget will not add.
If there is no other options, is there another network manager I could install?
https://bayimg.com/LABGiAAhG
sorry, i really don't know the answer to that, but i just added than and it went in fine. when you first installed, was it there (from the .iso from jan 2022), and it allowed a connection to upgrade or you not updated yet? If you whip out that system tray, then re-add it perhaps? lxqt is still a work in progress and a little quirky from what i see! but worth sticking with too.
I had so many bugs on my first set of installs in JAN that I resorted to a hard line.
I never had the wifi working, and now it does not at all.
oh, I found another post (that i also used but had forgot about!) about nm, try sudo pacman -S libstatgrab .
https://forum.artixlinux.org/index.php/topic,3989.0.html
personally I'd just wipe the lot and start again from the sound of your pc, but never having the wi-fi working even on a live boot on the jan .iso) kind of flags a firmware issue for your card to me - do you know what it is? Personally, i keep a cheat sheet when installing/configuring a new install, otherwise those commands that don't work begin to get lost in the ones that do - that way if and when i need to reinstall, i can just copy and paste down the list and it all goes smoothly and quickly too (and cleanly!)
I thank you
libstatgrab allowed me to add the network monitor applet.
But the applet does not let me configure my network, nor the wifi
You can see above (reply #6) I built the firmware for it , and I think it is installed correctly. But I am open to the idea I did it wrong.
I also see it flash, as it does when the driver is working on ClearLinux.
But I could be wrong.
I am loath to wipe and redo, as I have several configurations like SSH that I did not keep track of, and am sure to miss on a reload.
About my third reinstall I started doing that, but did not keep it up with all the changes.
But if that is the only way to fix my wifi, I guess I'll have to.
Is there a known set of things I should back up to make recovery easy?
sorry, my mistake for not reading the whole thread. The link for aur doesn't resolve for me, but is this the same?:
https://aur.archlinux.org/packages/rtl8812au-dkms-git
yes.
is there an alternative to networkmanager i could use? that works with Artix LXQt
i really don't think that is the problem - my reasoning for that is that I just live booted the stable .iso (albeit for dinit) and nothing required to add to the wi-fi network for this thinkpad, so I'm assuming the only difference is just the init, which shouldn't make a difference, and the chip, for which mine is a realtech 8822. But when you live boot, you cannot connect to wi-fi from the live boot, so i'm pretty much out of idea's. Sorry.
I am not arguing that netmanger CANNOT work.
It is obviously misconfigured/missing a component/whatever.
I just figured if I could replace it with something that works, then, it would work.
okay....on a live boot, can you connect to wi-fi? If the answers "no", its not a little widget thats the problem but points more to firmware etc - otherwise this or indeed 2 other machines I tried this afternoon would not be able to connect either without adding "a missing component" too either. As an aside, seriously, i can't remember the last time i installed anything linux without verifying wi-fi connections first for obvious reasons!
I do not know much, but I do not see how my wifi could work on a live CD?
If one needs to build a driver for the wifi to work and install it on a standard install, then, i assume, i would need to do that with for the live CD.
How do i do that with a live CD?
I mean another option is to have them include the drive on the live CD, but I do not see that happening.
You mean you tried it on machines that had wifi drivers that were included with the live CD?
Did you try it on any machines that did not have the correct wifi driver on the live CD?
But I tried it. i downloaded a weekly, 30May, and booted it. The panel crashed right out to a error message and blank screen on boot.
I happened to have a 06Mar, which booted, but it did not have a driver. I started to update it, then i realized, any updates were useless.
I just assume I need a hardline, will have to update, and then fight with the wifi.
good, glad you see it - besides i was only trying to help and steer you away from an alternative to nm which would be fruitless because you have another issue behind it. maybe the aircrack you install didn't completely uninstall, maybe the updated firmware ver is the answer - either way, there's a selection of 4 for that chip, and we know one certainly doesn't work, one is orphaned so that leaves two - the time taken on this thread is a lot longer than the time to do a clean install, twice if necessary, just saying. And with that, I shall leave it. Goodnight, G
https://aur.archlinux.org/packages?O=0&SeB=nd&K=rtl8812au&outdated=&SB=p&SO=d&PP=50&submit=Go
What are you saying i saw?
I know it worked well in clearlinux.
That you need a driver for your wifi
I've skimmed through this thread and unless I'm mistaken I've not seen dmesg (or the kernel.log) mentioned.
sudo dmesg
will show you all the the devices setup at at boot and since.
sudo dmesg >~/dmesg.txt
will place a text file with it all in your home dir for easier searching.
If your device is a dongle remove and reinsert and you should find some messages relating to your device right at the end if you run dmesg again.
Post them.
Also search dmesg for any errors, especially relating to firmware.
For the time being consider downgrading to the most recent lts kernel
sudo pacman -Syu linux-lts linux-lts-headers
When the kernel goes up a point release, as it very recently did, this can sometimes cause compile and other issues with 'out of tree' drivers. Which from my skim I guess yours is ?
sudo dmesg >~/dmesg.txt
sudo dmesg >~/dmesgreinsert.txt
@gripped if dmesg has no errors, is there a need for downgrading the kernel?
Cheers.
No driver is being loaded. After
There should be some messages with the actual driver / kernel module setting up the device.
With a device name like wlan0 or wlp5s0 or fairly similar.
ip link show
will list all your network devices
cat /proc/net/wireless
should list your wireless network devices (I haven't used wifi on my pc in years so no expert)
So the other posters are right, no working driver. You need to keep trying to build a working driver from the AUR and / or downgrade the kernel as I suggested until the above commands show a wireless network interface.
Any errors encountered post in full and be as detailed in the steps taken as you can.
Alternatively get a wifi dongle which is well supported by linux with an in kernel driver. Not saying you should. Just that it's an option.
ip link show
1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: eth0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
link/ether 40:8d:5c:50:51:89 brd ff:ff:ff:ff:ff:ff
5: tun0: <POINTOPOINT,MULTICAST,NOARP,UP,LOWER_UP> mtu 1434 qdisc fq_codel state UNKNOWN mode DEFAULT group default qlen 500
link/none
6: wlan0: <NO-CARRIER,BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc mq state DORMANT mode DORMANT group default qlen 1000
link/ether ae:1b:2f:5c:ae:88 brd ff:ff:ff:ff:ff:ff permaddr 08:10:7a:66:af:d7
7: wlan1: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc mq state DOWN mode DORMANT group default qlen 1000
link/ether d6:05:0d:f1:b2:f1 brd ff:ff:ff:ff:ff:ff permaddr 0a:10:7a:66:af:d7
cat /proc/net/wireless
Inter-| sta-| Quality | Discarded packets | Missed | WE
face | tus | link level noise | nwid crypt frag retry misc | beacon | 22
wlan0: 0000 0. 0. 0. 0 0 0 0 0 0
wlan1: 0000 0. 0. 0. 0 0 0 0 0 0
wireless devices do show.
this dongle, as the github.com/morrownr/8812au-20210629 doc explain, allow dual devices. currently they are wlan0 and 1
Does this not support that there is a working driver installed?
lsmod shows it too, i think?
lsmod
Module Size Used by
tun 61440 2
rfcomm 94208 4
snd_seq_dummy 16384 0
snd_hrtimer 16384 1
snd_seq 94208 7 snd_seq_dummy
snd_seq_device 16384 1 snd_seq
fuse 176128 6
qrtr 57344 4
cmac 16384 2
algif_hash 16384 1
algif_skcipher 16384 1
af_alg 36864 6 algif_hash,algif_skcipher
bnep 32768 2
edac_mce_amd 57344 0
kvm_amd 167936 0
ccp 131072 1 kvm_amd
rng_core 20480 1 ccp
kvm 1118208 1 kvm_amd
irqbypass 16384 1 kvm
vfat 24576 3
fat 90112 1 vfat
amdgpu 8941568 30
crct10dif_pclmul 16384 1
snd_hda_codec_realtek 167936 1
crc32_pclmul 16384 0
snd_hda_codec_generic 98304 1 snd_hda_codec_realtek
btusb 65536 0
snd_hda_codec_hdmi 86016 1
ledtrig_audio 16384 1 snd_hda_codec_generic
ghash_clmulni_intel 16384 0
btrtl 28672 1 btusb
btbcm 20480 1 btusb
8812au 3039232 0
mxm_wmi 16384 0
snd_hda_intel 61440 4
btintel 49152 1 btusb
snd_intel_dspcfg 36864 1 snd_hda_intel
aesni_intel 380928 3
btmtk 16384 1 btusb
snd_intel_sdw_acpi 20480 1 snd_intel_dspcfg
crypto_simd 16384 1 aesni_intel
snd_hda_codec 184320 4 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec_realtek
cryptd 28672 3 crypto_simd,ghash_clmulni_intel
joydev 28672 0
r8169 106496 0
bluetooth 872448 36 btrtl,btmtk,btintel,btbcm,bnep,btusb,rfcomm
k10temp 16384 0
snd_hda_core 118784 5 snd_hda_codec_generic,snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek
mousedev 24576 0
fam15h_power 16384 0
pcspkr 16384 0
realtek 36864 1
mdio_devres 16384 1 r8169
cfg80211 1085440 1 8812au
snd_hwdep 16384 1 snd_hda_codec
libphy 172032 3 r8169,mdio_devres,realtek
sp5100_tco 20480 0
snd_pcm 172032 5 snd_hda_codec_hdmi,snd_hda_intel,snd_hda_codec,snd_hda_core
ecdh_generic 16384 1 bluetooth
i2c_piix4 36864 0
rfkill 36864 5 bluetooth,cfg80211
snd_timer 49152 3 snd_seq,snd_hrtimer,snd_pcm
gpu_sched 53248 1 amdgpu
drm_ttm_helper 16384 1 amdgpu
snd 126976 19 snd_hda_codec_generic,snd_seq,snd_seq_device,snd_hda_codec_hdmi,snd_hwdep,snd_hda_intel,snd_hda_codec,snd_hda_codec_realtek,snd_timer,snd_pcm
ttm 86016 2 amdgpu,drm_ttm_helper
soundcore 16384 1 snd
drm_dp_helper 167936 1 amdgpu
mac_hid 16384 0
wmi 45056 1 mxm_wmi
acpi_cpufreq 32768 0
crypto_user 24576 0
ext4 1011712 3
crc32c_generic 16384 0
crc16 16384 2 bluetooth,ext4
mbcache 16384 1 ext4
jbd2 192512 1 ext4
uas 32768 0
usb_storage 81920 5 uas
hid_elecom 16384 0
crc32c_intel 24576 6
xhci_pci 20480 0
usbhid 73728 0
xhci_pci_renesas 24576 1 xhci_pci
A driver at least. Hopefully working.
I'm surprised there's no mention of wlan0 (or wlan1) in the dmesg output. But there you go.
Let me have a think.
On my PC I use a wired connection with no NetworkManager or systray applets so can't help with that. But I used to use something terminal based to set up wifi on my Arch chromebook. Going to see if I can remember what it was. And what I use now. It did have lxqt on it but switched KDE. Only use it on holidays (so once in the last three years!)
I thank you for your think.
And I look forward to and thoughts that may develop.
Can you get network access at all ? To install packages.
Like ethernet temporarily or are you wifi only ?
Thinking back you mentioned installing packages so I'm going with you can.
https://snippets.leeharris.me.uk/manually-connect-to-wifi-in-a-terminal/
A note I made myself about bringing up a wifi connection on the command line
You'd need wireless_tools installed.
sudo in front of everything and you have wlan0 not mlan0
Doing things on the command line tends to give more feedback if things go wrong. Easier to debug.
Going to fire up this chromebook and have a look.
The terminal based program I was thinking of is 'wifi-menu'.
But it's part of the netctl package and based around systemd so no use here.
It's years ago now but I do remember having a real struggle getting wifi working on my ARM based chromebook at one point. Only manually or with wifi-menu worked. But I did get it working with NetworkManger in the end. No clue how now though.
I still suggest trying to do some wifi related things on the the command line.
See if the the driver is working and /or where it stops working.
Better than my notes!
https://linuxconfig.org/connect-to-wifi-from-the-linux-command-line
But if you just search "linux wifi command line" you'll find lots of examples.
https://github.com/morrownr/8812au-20210629/issues/39#issuecomment-1067025837
How could this driver get mainlined?
Complicated subject and it shouldn't make a huge difference.
That driver is in the AUR https://aur.archlinux.org/packages/rtl8812au-dkms-git
Maybe it's the one you have installed ? It's actively maintained on github which is always a promising sign
The fact that ip link show does show up your wifi network devices is also a promising sign.
Did you try any of the terminal commands I linked to.
Install wireless_tools
sudo ip link set wlan0 up
sudo iwlist wlan0 scan
Should bring up wlan0 and list any SSID's found.
I can see my local ssid's.
So the driver seems to be working, right?
nm-connection-editor cannot see them though
This didn't...
sudo wpa_cli
wpa_cli v2.10
Copyright (c) 2004-2022, Jouni Malinen <
[email protected]> and contributors
This software may be distributed under the terms of the BSD license.
See README for more details.
Interactive mode
Could not connect to wpa_supplicant: (nil) - re-trying
Got to this in your notes
sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/my.conf -B
Successfully initialized wpa_supplicant
ioctl[SIOCSIWAP]: Operation not permitted
Off to bed but try it again and post the commands plus output pasted into a code tag. Or pastebin or attached. I didn't fully follow that. Did you do the
wpa_passphrase ESSID PASSWORD > /etc/wpa_supplicant/my.conf
step ?
Replace ESSID and PASSWORD withg the relevant details (In case that is not obvious)
Yes I'd say the driver is probably working. But it's worth making sure by connecting manually on the terminal. Once that is known to be true it's time to try and figure out what's wrong with NetworkManager.
Ya. I had to sudo make the file, then the wpa_passphrase command worked and it did populate it.
sudo wpa_supplicant -Dwext -iwlan0 -c /etc/wpa_supplicant/my.conf -B
still gave
Successfully initialized wpa_supplicant
ioctl[SIOCSIWAP]: Operation not permitted
I do appreciate the re/stating the obvious. Make no assumptions of my skill.
I thank you.
Do you have network-manager-applet installed? That is a GTK3 thing and lxQT is QT, same as KDE plasma. This is just a guess, as I mostly use GTK desktops (for no especial reason) but perhaps a QT nm applet would work better in a QT desktop. If I do:
$ pacman -Ss network applet
I get several possible results for example, even more performing that search with an AUR helper. Varying the search terms could help too. "plasma-nm" might be worth a try instead.
In the first post i show pgrep nm-applet, so ya, i have it installed. but it never shows up.
It is my understanding, and I am often wrong, that GTK things run fine on a QT system and vice versa? I mean, with the things installed they do, right?
But I am fully willing to remove nm-applet, if i should, and install a QT one, or whatever.
But, Artix has LXQt. and it would seem that such systems work with wifi. I mean I know it does, I have installed it on laptops that worked fine. And I have used it on said laptops.
But I cannot diagnose why it will not work with my DKMS driver that works fine on lots of distros.
yes, gtk stuff runs fine on a qt environment and vice versa.
i didn't follow this thread closely, but as i use lxqt too, i have no problems with the status bar. even legacy stuff shows if i add ''system tray' together next to 'status notifier'.
to reply to your last question there is connman as alternatine for networkmanager, it has a gui/status bar/applet too. maybe your problems are also due to wpa_supplicant being too hard to set up on it's own (which it is, honestly, that's why OpenRC make their own scripts for easier setup)
sudo wpa_supplicant -Dwext -iwlan0 -c /etc/wpa_supplicant/my.conf -B
Would be a typo.
Correct
sudo wpa_supplicant -Dwext -iwlan0 -c/etc/wpa_supplicant/my.conf -B
No space between the -c and /etc/wpa_supplicant/my.conf.
That's how wpa_supplicant's man page states to format the options. I've no clue if it actually makes a difference?
As I said the notes I linked were just the the result of of my own debugging and experimentation some years ago when I was also having problems with desktop gui wifi applets
The -Dwext may be incorrect.? (It must have been what I needed). From the man page.
Try this (with the other steps)
wpa_supplicant -iwlan0 -c/etc/wpa_supplicant.conf -d
And this
wpa_supplicant -Dnl80211 -iwlan0 -c/etc/wpa_supplicant.conf -d
The -d at the end enables debugging output.
I wouldn't be suggesting using wpa_supplicant if things were working already
But imho when things aren't working it is sometimes best to go down to the basic level, with no scripts and gui's and see what is happening.
Also maybe worth mentioning. If I switch to LXQT on my chromebook the package network-manager-applet (nm-applet) is what is providing the wifi applet is the systray. So even though GTK it can work on lxqt.
did you mean...
wpa_supplicant -iwlan0 -c/etc/wpa_supplicant/my.conf -d
which worked, but keeps going forever, right?
then, following your guide
sudo dhcpcd wlan0
dhcpcd-9.4.1 starting
<snip>
wlan0: offered 192.168.1.134 from 192.168.1.254
wlan0: probing address 192.168.1.134/24
forked to background, child pid 5588
So, connected?
now what?
So we've proved that the wifi kernel driver works.
You should be able to ping ip addresses
ping 1.1.1.1
If you have, or do, set up /etc/resolve.conf
eg
nameserver 1.1.1.1
you can ping domains and use the internet.
When I jumped onto this thread you were being told, and it was also my initial belief due to the dmesg output, that you did not have a working wifi kernel driver. There's little point in trying to troubleshoot why your wifi applet isn't working until sure the wifi driver is working. We are now.
You can write a bash script with the commands you've used to connect to your wifi. You can also write one to disconnect.
It's a handy thing to know how to connect on the command line. Both wired and wifi.
As for the applet issue if me I'd start by figuring out where NetworkManager is logging to. And increase the logging verbosity if possible. A lot of what you'll find on the internet will be systemd related i.e. the journal. You don't have a journal. My NetworkManager is on the Arch Arm chromebook so I can't instantly help with that as I do have a journal.
If that fails to shed any light I'd try uninstalling NetworkManager and applets plus removing all the associated config files and installing again.
What init are you using ?
Are you sure the NetworkManager service is enabled ?
NetworkManager I know little about as I try to avoid such things on my PC. It makes sense on the chromebook but I use that very infrequently.
To give you a headstart as going from the username only you're fairly new to all of this ?
pacman -Ql networkmanager
shows all the files installed by networkmanager.
Of immediate interest
shows the programs installed by networkmanager
nmtui I imagine would be a Text User Interface (tui), have a play.
shows the configuration files locations as installed. That's not to say others might not have been created? Normally under ~/..config
shows the man pages available.
So if you wanted to know more about nmtui
man nmtui
If you wanted to know more about NetworkManager.conf
man NetworkManager.conf
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
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
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?
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.
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.
/usr/bin/NetworkManager --no-daemon --log-level=INFO
You could also try DEBUG as a log level (though probably overkill and likely to confuse.)
yes, and neither can nm-connection-editor
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.
Mentioned a few times it is OpenRC, and the log shows network manager is working, yes?
better to use log, or do it manually?
Sorry, I did say I'd only skimmed the thread up until the point I jumped on.
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.
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
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?
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.
/usr/bin/NetworkManager --no-daemon --log-level=INFO
should have been
sudo /usr/bin/NetworkManager --no-daemon --log-level=INFO
so if you ran as a normal user that would explain the permissions error.
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
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
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
rc-update show
please
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
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
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
Acknowledged
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.
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
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 ?
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.
That's very possible
From what the rest of your post states there's a chance you do.
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.
You're welcome