After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 791134 - Weird Behavior of NetworkManager and KWallet after Login in Plasma
Weird Behavior of NetworkManager and KWallet after Login in Plasma
Status: RESOLVED FIXED
Product: NetworkManager
Classification: Platform
Component: general
1.10.x
Other Linux
: Normal minor
: ---
Assigned To: NetworkManager maintainer(s)
NetworkManager maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-12-02 13:56 UTC by Nicolás Adamo
Modified: 2017-12-18 14:00 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nicolás Adamo 2017-12-02 13:56:02 UTC
Dear Sirs,

Sorry for coming up with a problem that has nothing to do with GNOME, and might not be related to NetworkManager, but to KWallet. To be honest, I couldn't track back the source of the problem.

I'm writting here basically seeking for help to understand the journalctl logs showed in this thread I've posted last night in ArchLinux Newbie Corner forums:
https://bbs.archlinux.org/viewtopic.php?id=232311

I agree this is not the best way to seek for a solution, so if you consider this bug doesn't proceed and needs to be cancelled/deleted to keep the development natural course, please do so.

Below some additional information about the versions and dates of update:
[2017-11-17 15:10] [ALPM] upgraded networkmanager (1.8.5dev+22+g5f2855fad-1 -> 1.10.0-1)
[2017-11-17 15:10] [ALPM] upgraded networkmanager-qt (5.39.0-1 -> 5.40.0-1)


Regards,

Nicolás Adamo
Comment 1 Nicolás Adamo 2017-12-02 15:56:37 UTC
I missed the line regarding kwallet update...

[2017-11-17 15:10] [ALPM] upgraded networkmanager (1.8.5dev+22+g5f2855fad-1 -> 1.10.0-1)
[2017-11-17 15:10] [ALPM] upgraded networkmanager-qt (5.39.0-1 -> 5.40.0-1)

[2017-11-17 15:09] [ALPM] upgraded kwallet (5.39.0-1 -> 5.40.0-1)
Comment 2 Thomas Haller 2017-12-04 10:14:14 UTC
probably fixed by https://cgit.freedesktop.org/NetworkManager/NetworkManager/commit/?id=e2c8ef45ac9fba8d4f5722ab10831bf42085a110

As workaround, try wither disabling WPS fixes the issue:

  nmcli connection modify "$CON" wifi-sec.wps-method disabled
Comment 3 Dmitry 2017-12-16 16:16:57 UTC
Got the same problem with "No agents were available for this request" error in journalctl logs and NetworkManager refusing to auto-connect to my WiFi after booting the system.
The problem appeared after upgrading networkmanager (1.10.0-1 -> 1.10.2-1).
Thanks for the workaround it worked for me but in what version the bugfix will be released?
Comment 4 Nicolás Adamo 2017-12-17 19:52:48 UTC
Marked as solved since the workaround is known and the bugfix is likely to be incorporated in the next (or at least some future) release.
Comment 5 Thomas Haller 2017-12-18 14:00:29 UTC
(In reply to Dmitry from comment #3)
> Got the same problem with "No agents were available for this request" error
> in journalctl logs and NetworkManager refusing to auto-connect to my WiFi
> after booting the system.
> The problem appeared after upgrading networkmanager (1.10.0-1 -> 1.10.2-1).
> Thanks for the workaround it worked for me but in what version the bugfix
> will be released?

1.10.2.

there is not enough information to verify whether you "got the same problem", or just something that looks similar.
Please open a new bug and provide level=TRACE logs. This bug is considered to be fixed on master and nm-1-10 branch (1.10.2 release or newer). Even if your issue happens to have the same cause, we still new new information and that warrants a new bug. Thanks