I can confirm this for Lucid. A possible workaround is to create a dummy
key and delete it immediately after that, this triggers a user dialog to
unlock the keyring.
--
Python binding for gnomekeyring prevents password prompt on unlock
https://bugs.launchpad.net/bugs/432882
You received this bug
The bug is fixed, or lets say disappeared in Ubuntu 9.04 final
release/Gnome 2.26.1, it works now as it should.
--
nautilus doesn't ask for keyring password after automatic login
https://bugs.launchpad.net/bugs/335990
You received this bug notification because you are a member of Ubuntu
Desktop B
Reported as http://bugzilla.gnome.org/show_bug.cgi?id=575277
--
nautilus doesn't ask for keyring password after automatic login
https://bugs.launchpad.net/bugs/335990
You received this bug notification because you are a member of Ubuntu
Desktop Bugs, which is a bug assignee.
--
desktop-bugs mai
I narrowed it down! The ssh key-file is the problem.
I got 2 identities, that's 2 key-files called id_dsa-user1(.pub) and
id_dsa-user2(.pub). When logged in to Gnome regularly or using the
terminal, the ssh-agent (or whatever agent is doing that) knows which
key-file to choose by its content (not
The issue is reproducable in Intrepid and Jaunty with different error messages.
Steps to reproduce:
1. Enable Automatic Login (in Gnome-panel: System: Administration: Login
Window: Security-tab)
2. Reboot (note: I don't need to unlock the key storage for internet access, it
might be different wit
Public bug reported:
Binary package hint: nautilus
This is Ubuntu Intrepid 8.10, Nautilus 2.24.1.
After automatic login I can't connect to a ssh/sftp server via nautilus'
connect-to-server-gui. From gnome-panel (I bookmarked the ssh-server) it fails
silently, from nautilus it says access denied