Description of problem: The window asking for your general keyring password is now broken, you can't type your password and so you can't unlock your keyring. Version-Release number of selected component (if applicable): gnome-keyring-2.20-4.fc8 gnome-keyring-pam-2.20-4.fc8 gnome-keyring-manager-2.20.0-1.fc8 How reproducible: static Steps to Reproduce: 1. run gnome-keyring-manager (or any app using the gnome-keyring) 2. a window asking to unlock your keyring appears 3. you can't type anything this windows is not fully drawn and desktop is frozen 4. have to kill that window Actual results: apps using the gnome-keyring are enable to access your keyring because it's not possible to unlock it. Expected results: should be able to unlock the keyring Additional info: sorry I don't know how to be more helpfull.
Can you upgrade to 2.20-4.f8 and test. We fixed a bunch of problems. Also, if your ~/.gnome2/keyrings/default file is 0 bytes, do: echo -n default > ~/.gnome2/keyrings/default
where can i find gnome-keyring-manager-2.20-4.f8? can't find it in koji All my other gnome-keyring-* are already in 2.20-4 you mean ~/.gnome2/keyrings/default or ~/.gnome2/keyrings/default.keyring? I only have default.keyring and it's not empty
Alex meant gnome-keyring-2.20-4.f8 And ~/.gnome2/keyrings/default (without extension) default.keyring is the actual keyring, default is a text file containing the name of the default keyring.
gnome-keyring-2.20-4 was already installed and now after upgrade: [madko@Alcyone ~]$ rpm -qa|grep keyring gnome-keyring-2.20-5.fc8 gnome-keyring-manager-2.20.0-1.fc8 gnome-keyring-pam-2.20-5.fc8 [madko@Alcyone ~]$ ls .gnome2/keyrings/ default default.keyring [madko@Alcyone ~]$ cat .gnome2/keyrings/default default[madko@Alcyone ~]$ The only change I can notice is the fact that the uncompletely drawn window frozing my desktop and asking for keyring pass appears a second time when I kill it.
Which version of glibc are you using ? The was a bug fix in glibc recently that solved some hang issues with the the gnome-keyring dialog. Can you try again with the latest glibc, please ?
This is a dup of bug 321761, which is a glibc gettext locking bug. *** This bug has been marked as a duplicate of 321761 ***
i'm using the glibc-2.6.90-17, i will try with glibc-2.6.90-18 asap
thanks, works great with glibc-2.6.90-18