Popper

Gnome keyring problem

Asked by pelm

Thanks for a great mail-notification program. To the problem: When i log in to gnome, popper ask to unlock the keyring. Why? I don't use auto-logon, i'm logging in from gdm as usual. Then when logged in the keyring is unlocked for the programs that use the keyring. But popper seems to ignore that, why? I must have the gnome keyring on. But i don't wish to have the little annoying popup every login. Is that a known bug, or if someone could give an explanation?

Regards

Question information

Language:
English Edit question
Status:
Solved
For:
Popper Edit question
Assignee:
No assignee Edit question
Solved by:
pelm
Solved:
Last query:
Last reply:
Revision history for this message
Ralf Hersel (ralf.hersel) said : 		#1

As far as I know this is standard Keyring behaviour.

Read this chapter of the Popper Help:

There must be a password for each user account. Characters are shown as

dots. Passwords are managed by Gnome-Keyring. When you key it in for the

first time or modify an existing password, all changes will be stored to

Keyring. Popper retrieves your passwords when checking for new emails.

Therefore the Keyring has to be unlocked at every start of a user-session

unless the password has been set to BLANK. If want to know more about

keyring you should take a look at the programm "Seahorse" or its

documentation. Seahorse can be found in Ubuntu menu:

system->preferences->passwords and encryption.

Revision history for this message
pelm (pelle-ekh) said : 		#2

Yes that's correct, but as this: http://live.gnome.org/GnomeKeyring/Pam states, when i have "libpam-gnome-keyring" installed, which i have, the keyring is automatically unlocked in every login, the login keyring is indeed unlocked when i log in because no other program which use the passwords in the default.keyring (ie evolution etc) complain, but Popper will unlock it again, why? It's not a consistent behaviour, i think. Other than that the program is great.

Revision history for this message
Pa_trick17 (trick17) said : 		#3

Hello pelm,

> the login keyring is indeed unlocked when i log in because no other program which use the passwords in the default.keyring (ie evolution etc) complain, but Popper will unlock it again, why?
Popper isn't unlocking an unlocked keyring. But it's possible that your standard-keyring, which is used by Popper to store and get the passwords, isn't the 'login'-keyring. Please check by typing

python -c "import gnomekeyring; print gnomekeyring.get_default_keyring_sync()"

to your shell.

Greets

Pa_trick17

Revision history for this message
pelm (pelle-ekh) said : 		#4

Thanks alot! Changing the standard keyring to be the same as the login keyring did the trick! Thanks!

/pelm

Revision history for this message
Hyperion1984 (jonathan-genest) said : 		#5

Hello,

I think I have the same problem, but I don't know how to change my default keyring. In seahorse, I only see a login keyring.

Thanks,

Jon

Revision history for this message
Срђан Хрњак (srdjan-hrnjak) said : 		#6

Hi

I have this problem too, but I don't know what to do exactly. After

python -c "import gnomekeyring; print gnomekeyring.get_default_keyring_sync()"

i get

None

This is great app, but I have to disable it for now, I don't want to enter password every time I boot up.

Thanks

Revision history for this message
Pa_trick17 (trick17) said : 		#7

Hi Hyperion1984 and Srdjan,

open seahorse (f.e. by typing "seahorse" in a terminal) -> right-click on the keyring you want as default -> click "Set as default" -> Done

Regards,

Pa_trick17