Bug#1069739: plasma-nm: loses connection when NetworkManager.service is restarted
Package: plasma-nm
Version: 4:5.27.10-1+b1
Severity: normal
When I run "systemctl restart NetworkManager.service" or an equivalent
operation is performed as part of a system upgrade the plasma-nm connection
to the NetworkManager daemon is lost. Currently it seems that the only way
to reestablish the connection is to logout and login again or to run
"systemctl --user restart plasma-plasmashell.service", but restarting the
plasmashell doesn't seem to put it in a state where it can operate, I tell
it to connect to a widi network and then it immediately says "disconnected".
But it does at least show the current connection status correctly after the
restart of the plasmashell.
The plasma-nm should be able to detect that NetworkManager restarted and
talk to the new daemon without problems.
When the plasmashell is restarted the plasma-nm should be able to work with
full functionality including connecting to wifi networks.
-- System Information:
Debian Release: trixie/sid
Architecture: amd64 (x86_64)
Kernel: Linux 6.7.9-amd64 (SMP w/4 CPU threads; PREEMPT)
Kernel taint flags: TAINT_WARN
Locale: LANG=en_AU.UTF-8, LC_CTYPE=en_AU.UTF-8 (charmap=UTF-8), LANGUAGE=en_AU:en
Shell: /bin/sh linked to /usr/bin/dash
Init: unable to detect
Versions of packages plasma-nm depends on:
ii kio 5.107.0-1+b2
ii libc6 2.37-18
ii libglib2.0-0t64 2.78.4-6
ii libkf5completion5 5.107.0-1+b2
ii libkf5configcore5 5.107.0-1+b2
ii libkf5configwidgets5 5.107.0-2+b2
ii libkf5coreaddons5 5.107.0-1+b2
ii libkf5dbusaddons5 5.107.0-1+b2
ii libkf5i18n5 5.107.0-1+b2
ii libkf5kiogui5 5.107.0-1+b2
ii libkf5kiowidgets5 5.107.0-1+b2
ii libkf5modemmanagerqt6 5.107.0-1+b2
ii libkf5networkmanagerqt6 5.107.0-1+b1
ii libkf5notifications5 5.107.0-1+b2
ii libkf5solid5 5.107.0-1+b2
ii libkf5wallet-bin 5.107.0-1+b2
ii libkf5wallet5 5.107.0-1+b2
ii libkf5widgetsaddons5 5.107.0-1+b2
ii libkf5windowsystem5 5.107.0-1+b2
ii libnm0 1.46.0-1+b2
ii libopenconnect5 9.12-1+b2
ii libqca-qt5-2 2.3.8-1+b1
ii libqt5core5t64 5.15.10+dfsg-7.2+b1
ii libqt5dbus5t64 5.15.10+dfsg-7.2+b1
ii libqt5gui5t64 5.15.10+dfsg-7.2+b1
ii libqt5network5t64 5.15.10+dfsg-7.2+b1
ii libqt5qml5 5.15.10+dfsg-2+b2
ii libqt5quickwidgets5 5.15.10+dfsg-2+b2
ii libqt5widgets5t64 5.15.10+dfsg-7.2+b1
ii libqt5xml5t64 5.15.10+dfsg-7.2+b1
ii libstdc++6 14-20240330-1
ii mobile-broadband-provider-info 20230416-1
ii network-manager 1.46.0-1+b2
ii plasma-framework 5.107.0-1+b2
ii qml-module-org-kde-kcoreaddons 5.107.0-1+b2
ii qml-module-org-kde-kirigami2 5.107.0-1+b2
ii qml-module-org-kde-prison 5.107.0-2+b2
Versions of packages plasma-nm recommends:
ii systemsettings 4:5.27.10-1+b1
Versions of packages plasma-nm suggests:
pn network-manager-fortisslvpn <none>
pn network-manager-iodine <none>
pn network-manager-l2tp <none>
pn network-manager-openconnect <none>
pn network-manager-openvpn <none>
pn network-manager-pptp <none>
pn network-manager-ssh <none>
pn network-manager-strongswan <none>
pn network-manager-vpnc <none>
-- debconf-show failed
Reply to: