Comment 5 for bug 680910

Hello Bhabba,

thanks for your detailed reportings!

The first line of popper.log appears because the first thing popper does after launching is trying to open Gnome Keyring with an empty string which is the common method to automatically unlock even if you auto-login. Normally it's better not trying to unlock with an empty string but with an "NULL" which isn't possible at the moment for us python-developers, because of a bug from pythons gnomekeyring-library allready reported by me (-> https://bugzilla.gnome.org/show_bug.cgi?id=633958). If it would be possible to pass an "None" in the gnomekeyring library of python which would pass an "NULL", seahorse would behave as suspected by either trying to unlock automatically or prompt a dialog to unlock the keyring as is usual. We tried to replicate this behaviour which could never be the same as the original behaviour by the application designed to handle password-keyrings (and encryption keys), which seahorse is.

Actually we're trying to solve the problem you're describing at the moment. I have been able to reproduce this behaviour and could say, that in my reproduced case (it had something to do with checking for internet connection, too) it could be solved. So please be patient until we'll give a christmas-gift which hopefully will solve your problems.

Check out this launchpad-site around christmas :-)

If not, feel free to reopen this bug again. We've got an message-menu trial-skript i would like you to use in this case to be sure the problem isn't by a broken configuration of the message-menu.

For now, i'll set it to "Fix Commited".

Thank you for using popper and again for giving back by reporting.

Greets

Patrick