I am running KDE on an X260. Since the latest updates, after suspending
the machine, network-manager doesn't connect the network again and the taskbar applet says "no connections found". Logging out of the Plasma
session and logging in again fixes the issue until next suspend.
Hi,
On Mon, Aug 14, 2023 at 01:46:52PM +0200, Marc Haber wrote:
I am running KDE on an X260. Since the latest updates, after suspending
the machine, network-manager doesn't connect the network again and the
taskbar applet says "no connections found". Logging out of the Plasma
session and logging in again fixes the issue until next suspend.
Am I really the only one?
Greetings
Marc
Hi,
I am running KDE on an X260. Since the latest updates, after suspending
the machine, network-manager doesn't connect the network again and the taskbar applet says "no connections found". Logging out of the Plasma
session and logging in again fixes the issue until next suspend.
Is anybody else seeing this behavior and has already debugged?
than it helps to manually switch on the network again:
nmcli networking on
I am running KDE on an X260. Since the latest updates, after suspending
the machine, network-manager doesn't connect the network again and the taskbar applet says "no connections found". Logging out of the Plasma
session and logging in again fixes the issue until next suspend.
Is anybody else seeing this behavior and has already debugged?
Am Montag, 14. August 2023, 13:46:52 CEST schrieb Marc Haber:
I am running KDE on an X260. Since the latest updates, after suspending
the machine, network-manager doesn't connect the network again and the taskbar applet says "no connections found". Logging out of the Plasma session and logging in again fixes the issue until next suspend.
Is anybody else seeing this behavior and has already debugged?
No, but the audio applet exposes funny behaviour here, too (audio sinks are displayed multiple times after resume or if I reconnect the dock, at least sometimes).
Restarting plasmashell only (killall plasmashell; plasmashell&) fixes at least
that issue until next suspend/resume cycle (for me).
On Sat, Aug 19, 2023 at 04:01:15PM +0200, Dietz Proepper wrote:
No, but the audio applet exposes funny behaviour here, too (audio sinks
are
displayed multiple times after resume or if I reconnect the dock, at least sometimes).
Restarting plasmashell only (killall plasmashell; plasmashell&) fixes at least that issue until next suspend/resume cycle (for me).
Restarting plasmashell doesn't help here.
The nm applet seems to
reconnect and shows the available connections, but clicking on one immediately yields a toast "Connection (name) deactivated" without even trying to conect. I didn't know that behavior before.
Am Sonntag, 20. August 2023, 10:44:19 CEST schrieb Marc Haber:
The nm applet seems toAnything interesting in /var/log/syslog? The other thing I'd try first is to play a little with nmctl so you can narrow down who might be the culprit.
reconnect and shows the available connections, but clicking on one
immediately yields a toast "Connection (name) deactivated" without even
trying to conect. I didn't know that behavior before.
On 20/08/2023 10:58, Dietz Proepper wrote:
Am Sonntag, 20. August 2023, 10:44:19 CEST schrieb Marc Haber:
The nm applet seems toAnything interesting in /var/log/syslog? The other thing I'd try first is to >> play a little with nmctl so you can narrow down who might be the culprit.
reconnect and shows the available connections, but clicking on one
immediately yields a toast "Connection (name) deactivated" without even
trying to conect. I didn't know that behavior before.
Or 'journalctl -f' whilst attempting...things.
alexd
On Sat, Aug 19, 2023 at 04:01:15PM +0200, Dietz Proepper wrote:
Am Montag, 14. August 2023, 13:46:52 CEST schrieb Marc Haber:
I am running KDE on an X260. Since the latest updates, after suspending the machine, network-manager doesn't connect the network again and the taskbar applet says "no connections found". Logging out of the Plasma session and logging in again fixes the issue until next suspend.
Is anybody else seeing this behavior and has already debugged?
No, but the audio applet exposes funny behaviour here, too (audio sinks are
displayed multiple times after resume or if I reconnect the dock, at least sometimes).
Restarting plasmashell only (killall plasmashell; plasmashell&) fixes at least
that issue until next suspend/resume cycle (for me).
Restarting plasmashell doesn't help here. The nm applet seems to
reconnect and shows the available connections, but clicking on one immediately yields a toast "Connection (name) deactivated" without even trying to conect. I didn't know that behavior before.
Logout/Login => network fine.
Am Sonntag, 20. August 2023, 10:44:19 CEST schrieb Marc Haber:
Restarting plasmashell doesn't help here.
Ok, then that smells not like a kde problem to me.
The nm applet seems to
reconnect and shows the available connections, but clicking on one immediately yields a toast "Connection (name) deactivated" without even trying to conect. I didn't know that behavior before.
Anything interesting in /var/log/syslog?
What kind of network btw? WLAN? Mobile?
Not really sure if helps, but just in case: Could you check whether kded5 process is alive when you experience the problem?
On Sun, Aug 20, 2023 at 04:46:09PM +0200, Raúl Sánchez Siles wrote:
Not really sure if helps, but just in case: Could you check whether kded5 process is alive when you experience the problem?
I recorded kded5's pid before suspending and verified after using nmtui
to get back connectivity that the pid isstill the same. It is.
Do you want me to do more checks with kded5?
Greetings
Marc
-- >----------------------------------------------------------------------------- >Marc Haber | "I don't trust Computers. They | Mailadresse im Header >Leimen, Germany | lose things." Winona Ryder | Fon: *49 6224 1600402 >Nordisch by Nature | How to make an American Quilt | Fax: *49 6224 1600421
On Sun, Aug 20, 2023 at 11:58:48AM +0200, Dietz Proepper wrote:
Am Sonntag, 20. August 2023, 10:44:19 CEST schrieb Marc Haber:
Restarting plasmashell doesn't help here.
Ok, then that smells not like a kde problem to me.
It does to me. At least on a WPA Perosnalnetwork, I can connect using
nmtui alright. This smells to me like the nm applet not talking
properly to NetworkManager (which got updated on 09 Aug 2023, current
version being 1.44.0-1). Will try a downgrade tomorrow.
Note the "Activation: (wifi) access point 'Zugschlus_Netgear' has
security, but secrets are required." and "no secrets: No agents were available for this request." In my understanding, the agent in question
would be a KDE component since the secret was entered in the nm applet.
Now, where does nm applet store the secrets?
I am running KDE on an X260. Since the latest updates, after suspending
the machine, network-manager doesn't connect the network again and the taskbar applet says "no connections found". Logging out of the Plasma
session and logging in again fixes the issue until next suspend.
Is anybody else seeing this behavior and has already debugged?
I am running KDE on an X260. Since the latest updates, after suspending
the machine, network-manager doesn't connect the network again and the taskbar applet says "no connections found". Logging out of the Plasma
session and logging in again fixes the issue until next suspend.
Is anybody else seeing this behavior and has already debugged?
Sysop: | Keyop |
---|---|
Location: | Huddersfield, West Yorkshire, UK |
Users: | 546 |
Nodes: | 16 (1 / 15) |
Uptime: | 160:34:25 |
Calls: | 10,385 |
Calls today: | 2 |
Files: | 14,056 |
Messages: | 6,416,493 |