• network managed applet not seeing connections after suspend

    From Marc Haber@21:1/5 to All on Mon Aug 14 13:50:01 2023
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marc Haber@21:1/5 to Marc Haber on Thu Aug 17 20:40:01 2023
    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

    -- ----------------------------------------------------------------------------- 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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marc@21:1/5 to All on Fri Aug 18 12:00:01 2023
    Am 17.08.23 um 20:37 schrieb Marc Haber:
    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,

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lisandro =?ISO-8859-1?Q?Dami=E1n_Ni@21:1/5 to All on Fri Aug 18 15:37:27 2023
    Copy: mh+debian-kde@zugschlus.de (Marc Haber)

    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.

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAmTfumcACgkQq2RfQGKG p9C1BQ//RCfkQ+M/4aycEAakB0H3RSuujh0/lFVQr4Pbw9prHLUOaitkItLxvSlc B/zly2dxLnQ5VrcL/dxu4vUaIXTTIYIy9MImiHGJLbRGT8v2/fajEuOn+X0/+sD+ xvZ5EKxDRjgH2xWho+W6CK1YvwZdcMJEmdolmhfTVJf8dMZ6/lZ6FwmAhVwR1f+k TB0Sfn56//vOW/HqhcqG4+HuxzqJGvMHc92RudITysXbJMQDb3yLuAQgZaZXEpBo xn1nQAUKQI1HOfcayHiCFMlKo5+J9rGHRpiHeNk7k03cPSAv7RSGd9fg6A5gkJOK esYsb048ewGZXzTi94yyM6kKKLP10wv1uMhtUbaxgwcUbvARbEkuSGsJkN5ZM/qk OfLEnUEW7AE0P1VcUo+vKHWCU+RWkZuzJPtkI1ov8/Mdm7Wy3kO7bLP2WqqRipnU EGpaUKfxTzz6B3PSlZ1y44gY6Q0MnqU9l0ApG6P5s0gPKg3fjX3ZdnIv6rzCKE1e Gp3LjxTXLoHICR9zcPD2uBwhVgNywSH+O23tnGQ8TAh4upeDQCd2RaDLVaLEmyxb lbtera8cASgIy3lFts70Zf9b2+shq/u2Ww14ZXyI87VrNN/YDCHjGgpXtTHCATg+ ESGJrmyvE0zNM2YwXgPVScozjba2u5Z0KUc1xZHDsBca+Qe2x74=
    =9cmh
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marc Haber@21:1/5 to Marc on Sat Aug 19 07:10:01 2023
    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
    applet show "lo disabled", but nmcli networking on doesn't bring the
    contents back to the connection list.

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dietz Proepper@21:1/5 to All on Sat Aug 19 16:01:15 2023
    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).

    Regards,
    Dietz
    -----BEGIN PGP SIGNATURE-----

    iHUEABEKAB0WIQRXLjFJrGUqrtIn2lCong32mc4SfAUCZODLKwAKCRCong32mc4S fCNYAP4tQ52US7oZ1z5n7npzMAKfPoCkyGQbQCKpFChZYmfrhwD9Eed3NTEs/9Sx eRJ54DDgSE3DJ6d1JbCZpLQTXew31yk=
    =62Tt
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marc Haber@21:1/5 to Dietz Proepper on Sun Aug 20 10:50:02 2023
    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.

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dietz Proepper@21:1/5 to All on Sun Aug 20 11:58:48 2023
    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.

    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? The other thing I'd try first is to play a little with nmctl so you can narrow down who might be the culprit.

    What kind of network btw? WLAN? Mobile?

    Regards,
    Dietz
    -----BEGIN PGP SIGNATURE-----

    iHUEABEKAB0WIQRXLjFJrGUqrtIn2lCong32mc4SfAUCZOHj2AAKCRCong32mc4S fDbvAQCKmsZuUX/ImsgRpPwUZrynotTSw/aki0lQiYwdVT65PwD+LChgPPFajFqF M0jyl+gHpmJw/kLJEHEEIn3QsRkN2m4=
    =NWFF
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Alex DEKKER@21:1/5 to Dietz Proepper on Sun Aug 20 14:10:01 2023
    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 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? The other thing I'd try first is to play a little with nmctl so you can narrow down who might be the culprit.


    Or 'journalctl -f' whilst attempting...things.


    alexd

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?ISO-8859-1?Q?Ra=FAl_S=E1nchez_Sil@21:1/5 to All on Sun Aug 20 16:50:01 2023
    ------0PZNXFPDRRNJCU9XLJC8744N6BDEUQ
    Content-Type: text/plain;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    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,

    El 20 de agosto de 2023 13:39:15 CEST, Alex DEKKER <bugs@ale.cx> escribió:
    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 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? The other thing I'd try first is to >> play a little with nmctl so you can narrow down who might be the culprit.


    Or 'journalctl -f' whilst attempting...things.


    alexd



    ------0PZNXFPDRRNJCU9XLJC8744N6BDEUQ
    Content-Type: text/html;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <html><head></head><body><div dir="auto">Hi All:<br><br>Not really sure if helps, but just in case: Could you check whether kded5 process is alive when you experience the problem?<br><br>HTH,</div><br><br><div class="gmail_quote"><div dir="auto">El 20 de
    agosto de 2023 13:39:15 CEST, Alex DEKKER &lt;bugs@ale.cx&gt; escribió:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
    <pre class="k9mail"><div dir="auto">On 20/08/2023 10:58, Dietz Proepper wrote:<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">Am Sonntag, 20. August 2023, 10:
    44:19 CEST schrieb Marc Haber:<br><br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #ad7fa8; padding-left: 1ex;"><div dir="auto">The nm applet seems to<br>reconnect and shows the available connections, but
    clicking on one<br>immediately yields a toast "Connection (name) deactivated" without even<br>trying to conect. I didn't know that behavior before.<br></div></blockquote><div dir="auto">Anything interesting in /var/log/syslog? The other thing I'd try
    first is to<br>play a little with nmctl so you can narrow down who might be the culprit.<br><br></div></blockquote><div dir="auto"><br>Or 'journalctl -f' whilst attempting...things.<br><br><br>alexd<br><br><br></div></pre></blockquote></div></body></html>
    ------0PZNXFPDRRNJCU9XLJC8744N6BDEUQ--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Lisandro =?ISO-8859-1?Q?Dami=E1n_Ni@21:1/5 to All on Mon Aug 21 10:07:55 2023
    Copy: mh+debian-kde@zugschlus.de (Marc Haber)

    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.

    Logout/Login => network fine.

    Same here, but seems that I have less issues with WiFi rather than ethernet...

    -----BEGIN PGP SIGNATURE-----

    iQIzBAABCAAdFiEEEt36hKwjsrvwSzE8q2RfQGKGp9AFAmTjYasACgkQq2RfQGKG p9Cpqg/+PIYDziZth5oNIi2rbZ4LQEd5WlF6cbxPJ8AaZaWdh9VkXl0qWNF+UrNp ea+cMKeWc4Vw5l9NNAh0WlFBMnzTn4t1JAeZkFMEix8bNE2NiA16NoYTDVdSs/5H 9t+4yWt0C43AcDGKvl00ngR+O0f7VIkbwH5YxuSDv0MaxdMsUuKAx8tq+dkjli3A ssXRJ9aoi2uJHO7ZmgwC44eqXiIs5jYCQqowboat5rA0cO+t/4iNK8/L7Vc3hN6x lHD1kCoenj/BKrSI8PoQnqwBlEu9ZNaxlzW/qJpethDvNFili/SoErgfbDKDUfd+ XD3yw7OxM5ZwkihWxcjmER0wrby54+cCAwN7SfEvjxRzJkc4yz4DqCYj6mvNKrOE 797bMKDBHh2jQOvW6NsTto8d6MHxnpPZZWfjRq0ZslbEg5De+vdcSUGxUcXLRpfL SGhlMHfyttNVcDh0p6TcFpXccz2xmno2mM6CRJP7yVzuOV1+9Z2Ztp6JxacJyEFP P2YJ9LbzT00unfEKw8R07nKjswW7hqdRkNxkGcHg7GxP5aL31QL2PRsxxpSs+6le HgNNLni20OaDCLFRo4h3fomS4Tlg5/5gPLQH0dGfqL7Wm6NXiD4Sncv6+vC8F6Lk tf2wICclbt8GibijMOTzzl7B6EOWXu8boEg/FRHu2bMye1z5cH8=
    =N4Pf
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marc Haber@21:1/5 to Dietz Proepper on Mon Aug 21 19:20:02 2023
    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.

    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?

    System wakes up from suspend, first logs some blurb that was still in
    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?

    Wifi, an Intel Wireless 8260 using WPA Personal (at home WPA Enterprise,
    but all experiments were done on the road, eh, rails).

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marc Haber@21:1/5 to All on Mon Aug 21 19:20:02 2023
    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From =?ISO-8859-1?Q?Ra=FAl_S=E1nchez_Sil@21:1/5 to All on Mon Aug 21 20:30:02 2023
    ------YMDZTRFWLY783KAB2IP92WPO1SCWB1
    Content-Type: text/plain;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    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!

    El 21 de agosto de 2023 19:18:55 CEST, Marc Haber <mh+debian-kde@zugschlus.de> escribió:
    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


    ------YMDZTRFWLY783KAB2IP92WPO1SCWB1
    Content-Type: text/html;
    charset=utf-8
    Content-Transfer-Encoding: quoted-printable

    <html><head></head><body><div dir="auto">Great Marc! I have had issues after kded5 silently died and what you tested ruled this out. It is enough.<br><br>I hope you find the root cause soonish.<br><br>Regards!</div><br><br><div class="gmail_quote"><div
    dir="auto">El 21 de agosto de 2023 19:18:55 CEST, Marc Haber &lt;mh+debian-kde@zugschlus.de&gt; escribió:</div><blockquote class="gmail_quote" style="margin: 0pt 0pt 0pt 0.8ex; border-left: 1px solid rgb(204, 204, 204); padding-left: 1ex;">
    <pre class="k9mail"><div dir="auto">On Sun, Aug 20, 2023 at 04:46:09PM +0200, Raúl Sánchez Siles wrote:<br></div><blockquote class="gmail_quote" style="margin: 0pt 0pt 1ex 0.8ex; border-left: 1px solid #729fcf; padding-left: 1ex;"><div dir="auto">Not
    really sure if helps, but just in case: Could you check whether kded5 process is alive when you experience the problem?<br></div></blockquote><div dir="auto"><br>I recorded kded5's pid before suspending and verified after using nmtui<br>to get back
    connectivity that the pid isstill the same. It is.<br><br>Do you want me to do more checks with kded5?<br><br>Greetings<br>Marc<br><br></div></pre></blockquote></div></body></html>
    ------YMDZTRFWLY783KAB2IP92WPO1SCWB1--

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Dietz Proepper@21:1/5 to All on Tue Aug 22 08:04:56 2023
    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.

    [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.

    Now, where does nm applet store the secrets?

    KDEWallet iirc.
    -----BEGIN PGP SIGNATURE-----

    iHUEABEKAB0WIQRXLjFJrGUqrtIn2lCong32mc4SfAUCZORQCAAKCRCong32mc4S fKjtAP0eXWNmFcHiGOGqPMOoGbx/9XzEgoJ40RBURAT9HU6z5QD+NEWOrC5zj5v4 ZlTw66Jt/g7EezUmkAgdmtVSZxY5ObU=
    =EitU
    -----END PGP SIGNATURE-----

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marc Haber@21:1/5 to Marc Haber on Wed Aug 30 08:40:01 2023
    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.

    Is anybody else seeing this behavior and has already debugged?

    The problem is still present on my system. Downgrading network-manager
    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?

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)
  • From Marc Haber@21:1/5 to Marc Haber on Wed Oct 4 17:20:01 2023
    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 network-manager to 1.42.8-1 fixes the issue.

    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

    --- SoupGate-Win32 v1.05
    * Origin: fsxNet Usenet Gateway (21:1/5)