https://bugs.kde.org/show_bug.cgi?id=522934
Marco Martin <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] Status|REPORTED |CONFIRMED Ever confirmed|0 |1 --- Comment #6 from Marco Martin <[email protected]> --- This seems a bit of a difficult corner case to hit: it needs to be set as "for this user only" while at the same time not having anything stored in networkamanger and the connection set as encrypted, which the UI tries really hard to prevent (I have suspicions this might have been always been broken even before the qtkeychain imogration, is just very difficult to trigger). a convoluted series of steps i managed to reproduce the issue: * Remove the connection we wantto cause the bug form the kcm * having kwallet up and running, connect again to that connection making sure encrypted storage is selected. * disconnect, stop networkmanager, stop kded, disable kwallet and make sure neither kwallet nor ksecretsd are running (also no other secretservice providers, such as gnome-keyring) * restart networkmanager and kded * now every time connecting to that connection will always as k the password -- You are receiving this mail because: You are watching all bug changes.
