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 688741 - Wrong unlock dialogue when using autologin
Wrong unlock dialogue when using autologin
Status: RESOLVED DUPLICATE of bug 693145
Product: gnome-keyring
Classification: Core
Component: prompting
3.6.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2012-11-20 17:29 UTC by Bastien Nocera
Modified: 2013-03-05 08:06 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Bastien Nocera 2012-11-20 17:29:43 UTC
The keyring unlock is done using a fallback dialogue, when using autologin, instead of being done in the shell.

Stef thought this patch could help (making sure the keyring handling is done before the telepathy client, which might trigger the password dialogue, is launched):
diff --git a/js/ui/sessionMode.js b/js/ui/sessionMode.js
index 808109a..7f124fd 100644
--- a/js/ui/sessionMode.js
+++ b/js/ui/sessionMode.js
@@ -91,8 +91,8 @@ const _modes = {
         isLocked: false,
         isPrimary: true,
         unlockDialog: imports.ui.unlockDialog.UnlockDialog,
-        components: ['networkAgent', 'polkitAgent', 'telepathyClient',
-                     'keyring', 'recorder', 'autorunManager', 'automountManager'],
+        components: ['keyring', 'networkAgent', 'polkitAgent', 'telepathyClient',
+                     'recorder', 'autorunManager', 'automountManager'],
         panel: {
             left: ['activities', 'appMenu'],
             center: ['dateMenu'],
Comment 1 Stef Walter 2012-11-26 13:53:17 UTC
Bastien, did this fix the problem for you?
Comment 2 Bastien Nocera 2012-12-02 21:32:52 UTC
No, I made the change, and still see the old school unlock dialogue.
Comment 3 Stef Walter 2013-03-05 08:06:17 UTC
Marking as duplicate of bug #693145, because although it's later, there's more discussion of the issue there.

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