I only have a very small idea of what could be wrong. I noticed that the internet icon has disappeared from the panel. It used to be on the right side of the bottom panel (in the same group as the clock, for example). And it is no longer found in the settings.
May 30 11:41:22 localhost.localdomain systemd[15085]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.
May 30 11:41:29 localhost.localdomain NetworkManager[1439]: <info> [1748594489.8765] device (wlp3s0): set-hw-addr: set MAC address to 32:EB:62:67:5E:63 (scanning)
May 30 11:41:29 localhost.localdomain NetworkManager[1439]: <info> [1748594489.8988] device (wlp3s0): supplicant interface state: inactive -> interface_disabled
May 30 11:41:29 localhost.localdomain NetworkManager[1439]: <info> [1748594489.8989] device (p2p-dev-wlp3s0): supplicant management interface state: inactive -> interface_disabled
May 30 11:41:29 localhost.localdomain NetworkManager[1439]: <info> [1748594489.9088] device (wlp3s0): supplicant interface state: interface_disabled -> inactive
May 30 11:41:29 localhost.localdomain NetworkManager[1439]: <info> [1748594489.9088] device (p2p-dev-wlp3s0): supplicant management interface state: interface_disabled -> inactive
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 30 11:41:32 localhost.localdomain systemd[15085]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.
^C
localhost:~ #
I’m still wondering about this log amount.
I’ve done the following:
updated the router
downloaded the entire .config directory from the backup disk
updated the computer (zypper dup)
But I still can’t find the networkmanager command anywhere, and I don’t know how to start it from the console. Yast says that the network is managed with networkmanager.
The network itself works. Both wired and wireless connections.
If I understand correctly, drKonqi should tell you what it’s about, but I don’t understand anything from the text below Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system)
And I also couldn’t find the parameter NETWORKMANAGER_DNS_FORWARDER in the /etc/sysconfig/network/config file.
May 31 20:56:09 localhost.localdomain systemd[2917]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 31 20:56:09 localhost.localdomain systemd[2917]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 31 20:56:09 localhost.localdomain systemd[2917]: drkonqi-coredump-launcher.socket: Unit needs to be started because active unit sockets.target upholds it, but not starting since we tried this too often recently. Will retry later.
May 31 20:56:09 localhost.localdomain systemd[1]: Starting Network Manager Script Dispatcher Service...
May 31 20:56:09 localhost.localdomain systemd[1]: Started Network Manager Script Dispatcher Service.
May 31 20:56:09 localhost.localdomain dns-dnsmasq.sh[3062]: <debug> NETWORKMANAGER_DNS_FORWARDER is not set to "dnsmasq" in /etc/sysconfig/network/config -> exit
May 31 20:56:11 localhost.localdomain systemd[1]: systemd-localed.service: Deactivated successfully.
May 31 20:56:14 localhost.localdomain kded6[2143]: org.kde.colorcorrectlocationupdater: Geolocator stopped
May 31 20:56:19 localhost.localdomain systemd[1]: NetworkManager-dispatcher.service: Deactivated successfully.
May 31 20:56:19 localhost.localdomain systemd[2917]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 31 20:56:19 localhost.localdomain systemd[2917]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
May 31 20:56:19 localhost.localdomain systemd[2917]: Socket to launch DrKonqi for a systemd-coredump crash was skipped because of an unmet condition check (ConditionUser=!@system).
I’ll end the monologue this time. I found help on another forum on the internet.
The instructions were simple: 1) remove drkonqi6 2) reboot 3) install drkonqi back 4) reboot.
Well, networkmanager is still missing, but I wonder if it can be found somehow.
Thank you very much for the clear instructions. NetworkManager and Drkonqi are really not related to each other when the problem is the absence of NetworkManager. I mean they are not related to each other.
I think that the Drkonqi system was just somehow messed up because it was fixed only by reinstalling it and a couple of resets.
I think that NetworkManager and Kwallet are somehow related. When I removed Kwallet as an unnecessary program, NetworkManager was probably also removed. I know this because I tried to reinstall NetworkManager, but it couldn’t be installed because there was no Kwallet (or any of its plugins).
All in all, this created such a mess that I have spent many days investigating and fixing the situation. The root cause is probably that the Chrome browser does not start properly if Kwallet is not in use. On the other hand, I removed Kwallet because I use the Keepassxc plugin. And removing Kwallet removed NetworkManager?
Well, I finally abandoned Chromium (which I really like) and switched to Firefox, which doesn’t seem to have this problem.
Yes, by default Kwallet is used to save things like WiFi passwords for the Network Manager. It can also run without but that needs some configuration.
I am also not using Kwallet, I use KeePassXC instead. I tried deinstalling it but when I tried that it wanted to deinstall KDE completely so instead I did disable it:
(KDE) System Settings, search for wallet, KDE Wallet, deactivate the checkbox Enable the KDE wallet subsystem
The root cause is probably that the Chrome browser does not start properly if Kwallet is not in use.
The only problem I know is that chrome was slow to start or did you have other problems?
Anyhow with the latest update that should be solved with the last update.
karl@erlangen:~> journalctl -S 6:00 --user -u app-chr* --no-pager
Jun 03 07:21:58 erlangen systemd[1401]: Started Chromium Web Browser - Web Browser.
Jun 03 07:22:23 erlangen chromium-browser[305321]: [305315:305315:0603/072223.992127:ERROR:s/object_proxy.cc:590] Failed to call method: org.kde.KWallet.isEnabled: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jun 03 07:22:23 erlangen chromium-browser[305321]: [305315:305315:0603/072223.992172:ERROR:ponents/os_crypt/sync/kwallet_dbus.cc:117] Error contacting kwalletd6 (isEnabled)
Jun 03 07:22:23 erlangen chromium-browser[305321]: [305315:305315:0603/072223.992381:ERROR:s/object_proxy.cc:590] Failed to call method: org.kde.KLauncher.start_service_by_desktop_name: object_path= /KLauncher: org.freedesktop.DBus.Error.ServiceUnknown: The name is not activatable
Jun 03 07:22:23 erlangen chromium-browser[305321]: [305315:305315:0603/072223.992390:ERROR:ponents/os_crypt/sync/kwallet_dbus.cc:86] Error contacting klauncher to start kwalletd6
Jun 03 07:22:49 erlangen chromium-browser[305321]: [305315:305315:0603/072249.017812:ERROR:s/object_proxy.cc:590] Failed to call method: org.kde.KWallet.close: object_path= /modules/kwalletd6: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.
Jun 03 07:22:49 erlangen chromium-browser[305321]: [305315:305315:0603/072249.017850:ERROR:ponents/os_crypt/sync/kwallet_dbus.cc:412] Error contacting kwalletd6 (close)
Jun 03 07:22:49 erlangen chromium-browser[305321]: [305315:305315:0603/072249.183139:ERROR:tent/browser/network_service_instance_impl.cc:586] Network service crashed, restarting service.
Jun 03 07:22:49 erlangen chromium-browser[305321]: [305315:305315:0603/072249.337263:ERROR:ensions/browser/service_worker/service_worker_task_queue.cc:197] DidStartWorkerFail cfhdojbkjhnklbpkdaibdccddilifddb: 3
Jun 03 07:22:49 erlangen chromium-browser[305321]: [305315:305338:0603/072249.357906:ERROR:pto/nss_util.cc:344] After loading Root Certs, loaded==false: NSS error code: -8018
Jun 03 07:22:56 erlangen chromium-browser[305321]: libpng warning: iCCP: known incorrect sRGB profile
Jun 03 07:23:19 erlangen chromium-browser[305321]: [305315:305478:0603/072319.109762:ERROR:tent/browser/browser_main_loop.cc:278] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Jun 03 07:23:19 erlangen chromium-browser[305321]: [305315:305479:0603/072319.109769:ERROR:tent/browser/browser_main_loop.cc:278] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
Jun 03 07:23:19 erlangen chromium-browser[305321]: [305315:305477:0603/072319.109762:ERROR:tent/browser/browser_main_loop.cc:278] GLib: g_main_context_pop_thread_default: assertion 'stack != NULL' failed
karl@erlangen:~>
