Bug 531345

Summary:	gnome-keyring asks for password everytime a user logs into kde 4.
Product:	[Fedora] Fedora	Reporter:	Tony White <twhite>
Component:	gnome-keyring	Assignee:	Tomáš Bžatek <tbzatek>
Status:	CLOSED DUPLICATE	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	low
Version:	12	CC:	dcbw, mclasen, rdieter, tbzatek, tsmetana, walters
Target Milestone:	---
Target Release:	---
Hardware:	i686
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2010-05-03 15:22:00 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Tony White 2009-10-27 19:47:02 UTC

Description of problem:
Everytime I login into kde 4 I am presented with an input password dialogue to allow network manager to create a network connection.

Version-Release number of selected component (if applicable):


How reproducible:
Every time I login.

Steps to Reproduce:
1. Create wireless connection.
2. Logout.
3. Login to kde 4.
  
Actual results:
Please input password to unlock default keyring.
The dialogue actually makes no sense too. It's technobabble and some users may even interpret it as an ask for root password dialogue.

Expected results:
Connect wireless using network manager with no messing.
Just an option to turn the damn keyring off or that by default would suffice.

Additional info:
Requiring a password to login and then a password to unlock wireless every time you login by default; is way over the top.

Comment 1 Dan Williams 2009-11-02 17:52:30 UTC

keyring people; how should the kde session manager ensure that the keyring is unlocked on login?  Does it just magically work if the login keyring stuff is set up?

Comment 2 Tony White 2009-11-02 20:38:09 UTC

I think kwalletd is the equivalent to gnome-keyring-daemon, the two maybe conflict each other? Setting the kde pim stuff up is like some kind of voodoo known only by kde developers.

Maybe the trick would be getting gnome-network-manager to ask to store the keyring using kwalletmanager. That; I would love to see.
But would knetworkmanager instead of gnome-network-manager asking kwallet manager for the password to unlock the default keyring to connect the wireless adapter be more kde like instead?

Comment 3 Matthias Clasen 2009-11-02 20:43:22 UTC

There is work underway for a common dbus api for 'secrets'. Once that is in place, it will become a lot more realistic for applications to store their secrets in the desktops native keyring implementation.

Comment 4 Dan Williams 2009-11-02 20:50:13 UTC

nm-applet is a GNOME applet; there are KDE plasma widgets available for network config on KDE.  Ideally on KDE you'd use those, not nm-applet, and thus wouldn't run into the problem.

I think the people developing the plasma widget have been a bit slow to make sure it all works with NM and that's the reason people end up using nm-applet in KDE.

Comment 5 Tony White 2009-11-03 21:48:30 UTC

Quote : "The current version of network manager in the upcoming openSUSE 11.2 is 0.9.svn1040608-1.1.1 and is fully ported and compatible with kde4"

http://en.opensuse.org/Projects/KNetworkManager

Maybe there's a plasmoid for it but KNetworkManager is a qt4 C++ application.
Use that please. :)

Comment 6 Bug Zapper 2009-11-16 14:27:02 UTC

This bug appears to have been reported against 'rawhide' during the Fedora 12 development cycle.
Changing version to '12'.

More information and reason for this action is here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Comment 7 Rex Dieter 2010-05-03 15:22:00 UTC

Should be fixed in
* Mon Jan 04 2010 Rex Dieter <rdieter> - 2.28.2-2
- pam_gnome_keyring.so doesn't initialize properly on != gnome (#453880)
- hack out %%_libdir rpaths

*** This bug has been marked as a duplicate of bug 453880 ***