I am experiencing an issue with a broken desktop manager so networkmanager applet could not run, so I need to switch to wicked to get my wifi working.
Nothing I do in wicked results in dhcp obtaining an IP address for the wireless device.
I discovered I can run openbox and run nm-applet, where my wifi connection failed at first because it just didn't save the credentials after I typed them in. I did this three or four times in a row (immediately in a row, just clicking save, connection failes, reopen applet and edit connection, passphrase is missing, enter again) and then it just saved the value correctly after several tries. That might be an unrelated issue.
I can't copy/paste from the machine where the failure occurs, so I don't have logs or exact error messages.
The various wicked status commands report "device-not-running" and it is stuck at "setup-in-progress". I don't recall exactly which commands produced this output, and I don't have a good way to check while writing this post.
journtalctl showed the device refresh appear to succeed but then a few lines later the device is listed with "deviceUp: failed".
By logging in to openbox and checking snapper, I discovered that although I had disabled auto updates, the system had autoupdated for LAN configuration on April 16 and 17. I think it is likely that these problems are caused by the updates or issues described here:
https://bugzilla.suse.com/show_bug.cgi?id=1165266
https://bugzilla.opensuse.org/show_bug.cgi?id=1166933
https://bugzilla.opensuse.org/show_bug.cgi?id=1156920
and various other similar reports.
Could those same auto updates have somehow broken KDE?
This is ridiculous. This is not user error. I have a perfectly working system one day, I don't use auto updates, installed nothing, and made no system changes. I shut down and boot up the next day and the desktop manager is broken. I drop to terminal and network is broken.
Needless to say, this makes troubleshooting very difficult. I don't know if the desktop manager issue is related to the network issue. But I don't want to troubleshoot this. The system should not be pushing updates with auto updates not enabled. There should not be updates being pushed that break the non-gui network stack. The argument between the two people in the bugzilla threads I pasted above is absurd. One of them denies that wicked has problems, and the other one denies that they just pushed updates that broke the network, if my cursory reading is correct.
I think at this point I'm just going to stop using OpenSUSE, after like 15 years. I have a desktop that has a working OpenSUSE that I have been IN-PLACE UPGRADING since version 10 or so in 2009. That's how much I liked Suse. But I don't have time for this **** anymore.
Nothing I do in wicked results in dhcp obtaining an IP address for the wireless device.
I discovered I can run openbox and run nm-applet, where my wifi connection failed at first because it just didn't save the credentials after I typed them in. I did this three or four times in a row (immediately in a row, just clicking save, connection failes, reopen applet and edit connection, passphrase is missing, enter again) and then it just saved the value correctly after several tries. That might be an unrelated issue.
I can't copy/paste from the machine where the failure occurs, so I don't have logs or exact error messages.
The various wicked status commands report "device-not-running" and it is stuck at "setup-in-progress". I don't recall exactly which commands produced this output, and I don't have a good way to check while writing this post.
journtalctl showed the device refresh appear to succeed but then a few lines later the device is listed with "deviceUp: failed".
By logging in to openbox and checking snapper, I discovered that although I had disabled auto updates, the system had autoupdated for LAN configuration on April 16 and 17. I think it is likely that these problems are caused by the updates or issues described here:
https://bugzilla.suse.com/show_bug.cgi?id=1165266
https://bugzilla.opensuse.org/show_bug.cgi?id=1166933
https://bugzilla.opensuse.org/show_bug.cgi?id=1156920
and various other similar reports.
Could those same auto updates have somehow broken KDE?
This is ridiculous. This is not user error. I have a perfectly working system one day, I don't use auto updates, installed nothing, and made no system changes. I shut down and boot up the next day and the desktop manager is broken. I drop to terminal and network is broken.
Needless to say, this makes troubleshooting very difficult. I don't know if the desktop manager issue is related to the network issue. But I don't want to troubleshoot this. The system should not be pushing updates with auto updates not enabled. There should not be updates being pushed that break the non-gui network stack. The argument between the two people in the bugzilla threads I pasted above is absurd. One of them denies that wicked has problems, and the other one denies that they just pushed updates that broke the network, if my cursory reading is correct.
I think at this point I'm just going to stop using OpenSUSE, after like 15 years. I have a desktop that has a working OpenSUSE that I have been IN-PLACE UPGRADING since version 10 or so in 2009. That's how much I liked Suse. But I don't have time for this **** anymore.