Setting package back to network-manager since the upstream bug says the
problem is how NM is sending the passphrase to gnome-keyring-manager.
They also pointed out that Seahorse does not manage the keyring and is
only a viewer for gnome-keyring-manager.
** Changed in: network-manager (Ubuntu)
** Changed in: seahorse
Status: Unknown = Invalid
--
seahorse does not show original wpa passphrase
https://bugs.launchpad.net/bugs/291260
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in ubuntu.
--
desktop-bugs
** Changed in: seahorse (Ubuntu)
Status: Confirmed = Triaged
--
seahorse does not show original wpa passphrase
https://bugs.launchpad.net/bugs/291260
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in ubuntu.
--
It's showing a hash of the passphrase. The original is preferable as an
easy way to look up the passphrase.
** Changed in: seahorse (Ubuntu)
Importance: Undecided = Medium
Status: New = Confirmed
--
seahorse does not show original wpa passphrase
https://bugs.launchpad.net/bugs/291260
Thanks for reporting this bug. The same problem is happening in network manager
see bug#239970
Since different programs are the cause of each program im not sure they should
be marked as duplicates. Though it may make sense to mark both packages under
one bug. I have reported this upstream to
I believe NM is pulling the information from Seahorse since it's the
keyring manager.
--
seahorse does not show original wpa passphrase
https://bugs.launchpad.net/bugs/291260
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is subscribed to seahorse in
I think you are right, however, it was reported under network manager
because the command 'xprop | grep WM_CLASS' reports the application as
nm-connection-editor.
Again though these discussions should be continued on the bugs at bugzilla
because that is where the developers are who are most
