http://bugzilla.opensuse.org/show_bug.cgi?id=1108570 http://bugzilla.opensuse.org/show_bug.cgi?id=1108570#c2 Cimba Li changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |me@cimba.li --- Comment #2 from Cimba Li --- Created attachment 784688 --> http://bugzilla.opensuse.org/attachment.cgi?id=784688&action=edit Journal log of failed connection -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1108570 http://bugzilla.opensuse.org/show_bug.cgi?id=1108570#c4 Fabian Vogt changed: What |Removed |Added ---------------------------------------------------------------------------- Status|NEW |IN_PROGRESS Flags|needinfo?(adam@mizerski.pl) | --- Comment #4 from Fabian Vogt --- It seems to be a quirk in how NM sets up its DBus interface. I reported that as https://bugs.kde.org/show_bug.cgi?id=400359 and wrote a workaround patch. Please try with libKF5NetworkManagerQt6 from obs://home:Vogtinator:boo1108570/openSUSE_Factory and report back. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1108570 http://bugzilla.opensuse.org/show_bug.cgi?id=1108570#c6 --- Comment #6 from Cimba Li --- Nevermind, I finally managed to build and install your proposed patched libKF5NetworkManagerQt. It seems to fix the problem, though I have only tested it for a short while so far. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1108570 http://bugzilla.opensuse.org/show_bug.cgi?id=1108570#c8 --- Comment #8 from Fabian Vogt --- (In reply to Till Dörges from comment #7)

It appears that a standard openSUSE Leap 15.1 suffers from the same issue (and it's actually quite annoying).

Shall I open a separate bug for that?

If it's the same one, no.(In reply to Till Dörges from comment #7)

It appears that a standard openSUSE Leap 15.1 suffers from the same issue (and it's actually quite annoying).

Shall I open a separate bug for that?

FTR, I have these RPMs:

libKF5NetworkManagerQt6-5.55.0-lp151.1.1.x86_64 NetworkManager-1.10.6-lp151.8.1.x86_64 plasma-nm5-5.12.8-lp151.1.1.x86_64

And after restarting plasmashell

killall plasmashell ; sleep 3; plasmashell &

Don't use killall, use kquitapp5.

I cannot activate network connections that require a password.

Normally a PW dialog for unlocking kwallet appears, but not after a restart.

The secrets are provided by kded5, not plasmashell. So check whether kded5 is running. To restart, run kquitapp5 kded5; kded5 &

With journalctl I find this:

--- snip --- Aug 28 12:37:21 box NetworkManager[28889]: <info> [1566988641.8457] device (wlan1): state change: prepare -> config (reason 'none', sys-iface-state: 'managed') Aug 28 12:37:21 box NetworkManager[28889]: <info> [1566988641.8467] device (wlan1): Activation: (wifi) access point 'WLANSSID' has security, but secrets are required. Aug 28 12:37:21 box NetworkManager[28889]: <info> [1566988641.8467] device (wlan1): state change: config -> need-auth (reason 'none', sys-iface-state: 'managed') Aug 28 12:37:21 box NetworkManager[28889]: <warn> [1566988641.8500] device (wlan1): No agents were available for this request. Aug 28 12:37:21 box NetworkManager[28889]: <info> [1566988641.8501] device (wlan1): state change: need-auth -> failed (reason 'no-secrets', sys-iface-state: 'managed') Aug 28 12:37:21 box NetworkManager[28889]: <warn> [1566988641.8511] device (wlan1): Activation: failed for connection 'WLANSSID' --- snap ---

I had a look at https://build.opensuse.org/project/show/home:Vogtinator:boo1108570, but currently it doesn't seem to build.

The patch in there is part of Leap 15.1 already. -- You are receiving this mail because: You are on the CC list for the bug.

http://bugzilla.opensuse.org/show_bug.cgi?id=1108570 http://bugzilla.opensuse.org/show_bug.cgi?id=1108570#c10 Alexander Krupp changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |obs@akr.yagii.de --- Comment #10 from Alexander Krupp --- With 15.1 the problem occurs every time after a suspend on a laptop, which is quite annoying, especially when frequently suspending during a long meeting. Quickest solution so far has been to go to the nm-applet and open the "Configure network connections..." dialog. After the dialog opens, the connection succeeds. The dialog seems to do something to kded5, which enables credential access. As per comment #9, the "kquitapp5 kded5; kded5 &" solution works, too. Will check whether there is a systemd/user/session-hook after suspend which can be used to automate that. Suggestions and ideas are welcome, however... -- You are receiving this mail because: You are on the CC list for the bug.