Hi, On Thu, Mar 20, 2014 at 04:00:03PM +0000, Ximin Luo wrote: > On 20/03/14 15:32, Guido Günther wrote: > > Hi, > > On Thu, Mar 20, 2014 at 12:17:16PM +0000, Ximin Luo wrote: > >> Hi, > >> > >> This is a bit weird - I am also running iceweasel 24.3.0 and it works > >> fine for me. Those warnings you pasted do not seem relevant. > > > > I do think so too. > > > >> Can you add things to that keyring via seahorse? What is your > >> $XDG_RUNTIME_DIR? Anything else unusual about how your set-up? > > > > Yes, adding via seahorse works. No speial XDG_RUNTIME_DIR here. I > > deleted the keyring and it worked for one time (one site's password is > > in the keyring now) but now it doesn't even offer to store something in > > the keyring anymore. > > > > What do you mean by "no special"? What is its value?
$ echo $XDG_RUNTIME_DIR /run/user/1000 > Is gnome-keyring-daemon running? $ ps awux | grep [g]nome-keyring-daemon who 1915 0.0 0.1 733548 5040 ? SLl 12:53 0:00 /usr/bin/gnome-keyring-daemon --daemonize --login > Any errors about "keyring" in ~/.xsession-errors or ~/.xsession-errors.old ? The files don't exist. > Do you have a different keyring running? The default login keyring. > > Adding item via seahores works. > > > >> Can you start a new profile, disable all other extensions, and see if > >> it works? What does the error console (ctrl-shift-J) say? > > > > The error console is full of CSS warnings these days but nothing that > > looks related to the keyting. I ran without extensions and with a new > > profile but it didn't change anything. > > > > Try it with a non-default keyring - something apart from "mozilla"? You can > change it with "extensions.gnome-keyring.keyringName". > > What happens if you try to "view all passwords" - anything show up in the > terminal (that you're running iceweasel from), or the error console > (ctrl-shift-J)? > > If nothing else works, you can try building the extension with print It'd be awesome if this could happen without rebuilding the extension e.g. by using GK_LOG in more places and building with DEBUG by default. One would still have to enable debugging via NSPR_LOG_MODULES. > statements added to random places in the source code, and seeing if > you get any terminal output in that case. I deleted the keyring and it seems to work now (I have some items already stored in it). The only difference I can think of is, that I unlocked the keyring once by hand and now the unlock passworf for the keyring is stored in the login keyring. I'll roll out the extension on more machines during the next weeks and will report further findings. The severity isn't justified anymore but I'd be greato to see this bug kept open for now. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-rc-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact listmas...@lists.debian.org
