info
Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss
network managed applet not seeing connections after suspend
4 views
Skip to first unread message
Marc Haber
Aug 14, 2023, 7:50:03 AM8/14/23
to
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?
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
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?
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
Marc Haber
Aug 17, 2023, 2:40:05 PM8/17/23
to
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?
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.
Marc
Aug 18, 2023, 6:00:04 AM8/18/23
to
Am 17.08.23 um 20:37 schrieb Marc Haber:
for me it indeed happen to from time to time. mostly when the machine
suspended itself due to low battery.
than it helps to manually switch on the network again:
nmcli networking on
Marc
> 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,
>
> 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
>
for me it indeed happen to from time to time. mostly when the machine
suspended itself due to low battery.
than it helps to manually switch on the network again:
nmcli networking on
Marc
Lisandro Damián Nicanor Pérez Meyer
Aug 18, 2023, 2:40:04 PM8/18/23
to
El lunes, 14 de agosto de 2023 08:46:52 -03 Marc Haber escribió:
> 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?
Mmm, that might bemy issue on my laptop... Does not happens on my desktop. I'll try to reproduce.
> 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?
Marc Haber
Aug 19, 2023, 1:10:02 AM8/19/23
to
On Fri, Aug 18, 2023 at 11:43:23AM +0200, Marc wrote:
> than it helps to manually switch on the network again:
>
> nmcli networking on
No, that doesnt help on my system. nmcli networking off makes the nm
> than it helps to manually switch on the network again:
>
> nmcli networking on
applet show "lo disabled", but nmcli networking on doesn't bring the
contents back to the connection list.
Dietz Proepper
Aug 19, 2023, 10:20:04 AM8/19/23
to
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
> 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?
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).
Regards,
Dietz
Marc Haber
Aug 20, 2023, 4:50:04 AM8/20/23
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.
Dietz Proepper
Aug 20, 2023, 6:10:04 AM8/20/23
to
Am Sonntag, 20. August 2023, 10:44:19 CEST schrieb Marc Haber:
> 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.
Ok, then that smells not like a kde problem to 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.
play a little with nmctl so you can narrow down who might be the culprit.
What kind of network btw? WLAN? Mobile?
Regards,
Dietz
Alex DEKKER
Aug 20, 2023, 8:10:03 AM8/20/23
to
alexd
Raúl Sánchez Siles
Aug 20, 2023, 10:50:03 AM8/20/23
to
Hi All:
Not really sure if helps, but just in case: Could you check whether kded5 process is alive when you experience the problem?
HTH,
Not really sure if helps, but just in case: Could you check whether kded5 process is alive when you experience the problem?
HTH,
Lisandro Damián Nicanor Pérez Meyer
Aug 21, 2023, 9:10:04 AM8/21/23
to
El domingo, 20 de agosto de 2023 05:44:19 -03 Marc Haber escribió:
> 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.
I have a similar issue... but in my case the connections are established but no packet goes out or in.
> 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.
Same here, but seems that I have less issues with WiFi rather than ethernet...
Marc Haber
Aug 21, 2023, 1:20:04 PM8/21/23
to
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
> Not really sure if helps, but just in case: Could you check whether kded5 process is alive when you experience the problem?
to get back connectivity that the pid isstill the same. It is.
Do you want me to do more checks with kded5?
Marc Haber
Aug 21, 2023, 1:20:04 PM8/21/23
to
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
> 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.
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.
> > 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?
memory from before the suspend, then logs the wakeup. NetworkManager
restarts, does some housekeeping and finally tries to bring up
lanw0, which is the Wifi interface in question:
2023-08-21T18:49:31.974702+02:00 drop wpa_supplicant[1567]: lanw0: CTRL-EVENT-REGDOM-CHANGE init=DRIVER type=COUNTRY alpha2=DE
2023-08-21T18:49:32.017119+02:00 drop NetworkManager[266999]: <info> [1692636572.0166] policy: auto-activating connection 'Zugschlus_Netgear' (919eeee7-7cfb-4d27-abcb-65ea81d39d8b)
2023-08-21T18:49:32.017435+02:00 drop NetworkManager[266999]: <info> [1692636572.0172] device (lanw0): Activation: starting connection 'Zugschlus_Netgear' (919eeee7-7cfb-4d27-abcb-65ea81d39d8b)
2023-08-21T18:49:32.017648+02:00 drop NetworkManager[266999]: <info> [1692636572.0174] device (lanw0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2023-08-21T18:49:32.018157+02:00 drop NetworkManager[266999]: <info> [1692636572.0180] manager: NetworkManager state is now CONNECTING
2023-08-21T18:49:32.044987+02:00 drop systemd-networkd[932]: lanw0: Link DOWN
2023-08-21T18:49:32.045231+02:00 drop NetworkManager[266999]: <info> [1692636572.0447] device (lanw0): set-hw-addr: set-cloned MAC address to BE:A4:6B:EA:FD:DB (stable)
2023-08-21T18:49:32.050770+02:00 drop systemd-networkd[932]: lanw0: Link UP
2023-08-21T18:49:32.051017+02:00 drop NetworkManager[266999]: <info> [1692636572.0506] device (lanw0): state change: prepare -> config (reason 'none', sys-iface-state: 'managed')
2023-08-21T18:49:32.051348+02:00 drop NetworkManager[266999]: <info> [1692636572.0512] device (lanw0): Activation: (wifi) access point 'Zugschlus_Netgear' has security, but secrets are required.
2023-08-21T18:49:32.051575+02:00 drop NetworkManager[266999]: <info> [1692636572.0512] device (lanw0): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed')
2023-08-21T18:49:32.051952+02:00 drop NetworkManager[266999]: <info> [1692636572.0518] device (lanw0): supplicant interface state: disconnected -> interface_disabled
2023-08-21T18:49:32.052151+02:00 drop NetworkManager[266999]: <info> [1692636572.0518] device (p2p-dev-lanw0): supplicant management interface state: disconnected -> interface_disabled
2023-08-21T18:49:32.052387+02:00 drop NetworkManager[266999]: <warn> [1692636572.0520] device (lanw0): no secrets: No agents were available for this request.
2023-08-21T18:49:32.052641+02:00 drop NetworkManager[266999]: <info> [1692636572.0520] device (lanw0): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed')
2023-08-21T18:49:32.052856+02:00 drop NetworkManager[266999]: <info> [1692636572.0523] manager: NetworkManager state is now DISCONNECTED
2023-08-21T18:49:32.053097+02:00 drop NetworkManager[266999]: <warn> [1692636572.0525] device (lanw0): Activation: failed for connection 'Zugschlus_Netgear'
2023-08-21T18:49:32.053338+02:00 drop NetworkManager[266999]: <info> [1692636572.0528] device (lanw0): state change: failed -> disconnected (reason 'none', sys-iface-state: 'managed')
2023-08-21T18:49:32.096681+02:00 drop systemd-networkd[932]: lanw0: Link DOWN
2023-08-21T18:49:32.096854+02:00 drop NetworkManager[266999]: <info> [1692636572.0966] device (lanw0): set-hw-addr: set MAC address to 36:66:CB:C1:B0:3C (scanning)
2023-08-21T18:49:32.102787+02:00 drop systemd-networkd[932]: lanw0: Link UP
2023-08-21T18:49:32.106278+02:00 drop NetworkManager[266999]: <info> [1692636572.1061] policy: auto-activating connection 'Zugschlus_Netgear_5G' (b7c947c6-db17-404b-9282-b1aa499084cc)
2023-08-21T18:49:32.106910+02:00 drop NetworkManager[266999]: <info> [1692636572.1067] device (lanw0): Activation: starting connection 'Zugschlus_Netgear_5G' (b7c947c6-db17-404b-9282-b1aa499084cc)
2023-08-21T18:49:32.107132+02:00 drop NetworkManager[266999]: <info> [1692636572.1069] device (lanw0): state change: disconnected -> prepare (reason 'none', sys-iface-state: 'managed')
2023-08-21T18:49:32.108023+02:00 drop NetworkManager[266999]: <info> [1692636572.1073] manager: NetworkManager state is now CONNECTING
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?
When I then use nmtui to connect and select the SSID, it asks me for the
secret (every time again, nmtui doesnt seem to store the secret) and
connects. After this, nm applet still displays the "unconnected" icon
and "no available connections", but the system is conected and
communicates just fine.
> What kind of network btw? WLAN? Mobile?
but all experiments were done on the road, eh, rails).
Raúl Sánchez Siles
Aug 21, 2023, 2:30:04 PM8/21/23
to
Great Marc! I have had issues after kded5 silently died and what you tested ruled this out. It is enough.
I hope you find the root cause soonish.
Regards!
I hope you find the root cause soonish.
Regards!
Dietz Proepper
Aug 22, 2023, 2:10:04 AM8/22/23
to
Am Montag, 21. August 2023, 19:16:36 CEST schrieb Marc Haber:
> 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.
Ack.
> 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.
[Logfile]
>
> 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.
That makes sense.
> 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?
Marc Haber
Aug 30, 2023, 2:40:03 AM8/30/23
to
Hi,
On Mon, Aug 14, 2023 at 01:46:52PM +0200, Marc Haber wrote:
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.
>
> Is anybody else seeing this behavior and has already debugged?
The problem is still present on my system. Downgrading network-manager
> 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?
to 1.42 makes the tray icon work again. nmtui does always work.
What is the correct name of the tray icon and the network connection
widget, and in which package is it?
What else could I do?
Marc Haber
Oct 4, 2023, 11:20:03 AM10/4/23
to
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.
>
> Is anybody else seeing this behavior and has already debugged?
I still have the issue. All my notebooks are affected. Downgrading
> 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?
network-manager to 1.42.8-1 fixes the issue.
0 new messages