Bug#741975: xul-ext-gnome-keyring: Does not store passwords
Hi, > Hi Ralf, which version are you using, Icedove 38.3, the plugin has version 0.10. > and what happens to the contents of your .gnome2/keyrings between when you > log out and back in? There is no such file. I have the Gnome 3 gnome-keyring, which stores things in ~/.local/share/keyrings. What exactly do you mean by "what happens to the contents"? Those files don't look like they are readable text files... ;-) . I could try to see whether their sha1 changes. However, right now, I can't even reproduce the issue. Kind regards, Ralf
Bug#741975: xul-ext-gnome-keyring: Does not store passwords
On 30/09/15 19:33, Ralf Jung wrote: > I have the same problem: After entering the password in Icedove, they > appear in Seahores. Restarting Icedove works fine. However, when I log > out and back in, the passwords seem to be all gone and I am asked for > all of them again. > Hi Ralf, which version are you using, and what happens to the contents of your .gnome2/keyrings between when you log out and back in? X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git
Bug#741975: xul-ext-gnome-keyring: Does not store passwords
Hi, I have the same problem: After entering the password in Icedove, they appear in Seahores. Restarting Icedove works fine. However, when I log out and back in, the passwords seem to be all gone and I am asked for all of them again. This renders the plugin entirely useless. Kind regards, Ralf
Bug#741975: xul-ext-gnome-keyring: Does not store passwords
Hi, On Thu, Mar 20, 2014 at 04:00:03PM +, Ximin Luo wrote: On 20/03/14 15:32, Guido Günther wrote: Hi, On Thu, Mar 20, 2014 at 12:17:16PM +, 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-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741975: xul-ext-gnome-keyring: Does not store passwords
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. Can you add things to that keyring via seahorse? What is your $XDG_RUNTIME_DIR? Anything else unusual about how your set-up? Can you start a new profile, disable all other extensions, and see if it works? What does the error console (ctrl-shift-J) say? X On 17/03/14 20:36, Guido Günther wrote: Package: xul-ext-gnome-keyring Version: 0.6.9-6 Severity: grave Hi, while a keyring named mozilla gets created after installation of the plugin it doesn't get any passwords stored in it. In the console I'm seeing: $ iceweasel (process:12616): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed (iceweasel:12616): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised (iceweasel:12616): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised (iceweasel:12616): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised (iceweasel:12616): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised Could not check applicable rules for about:blank Could not check applicable rules for about:blank When clicking remember password nothing ends up in the keyring as seahorse shows. I'd appreciate any hints on howto debug this further. Cheers, -- Guido -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14.0-rc1+ (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xul-ext-gnome-keyring depends on: ii icedove24.3.0-2 ii iceweasel 24.3.0esr-1 ii libc6 2.18-4 ii libgcc11:4.8.2-16 ii libglib2.0-0 2.38.2-5 ii libgnome-keyring0 3.8.0-2 ii libnspr4 2:4.10.3-1 ii libstdc++6 4.8.2-16 xul-ext-gnome-keyring recommends no packages. xul-ext-gnome-keyring suggests no packages. -- no debconf information -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git signature.asc Description: OpenPGP digital signature
Bug#741975: xul-ext-gnome-keyring: Does not store passwords
Hi, On Thu, Mar 20, 2014 at 12:17:16PM +, 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. 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. Cheers, -- Guido -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
Bug#741975: xul-ext-gnome-keyring: Does not store passwords
On 20/03/14 15:32, Guido Günther wrote: Hi, On Thu, Mar 20, 2014 at 12:17:16PM +, 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? Is gnome-keyring-daemon running? Any errors about keyring in ~/.xsession-errors or ~/.xsession-errors.old ? Do you have a different keyring running? 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 statements added to random places in the source code, and seeing if you get any terminal output in that case. X -- GPG: 4096R/1318EFAC5FBBDBCE git://github.com/infinity0/pubkeys.git signature.asc Description: OpenPGP digital signature
Bug#741975: xul-ext-gnome-keyring: Does not store passwords
Package: xul-ext-gnome-keyring Version: 0.6.9-6 Severity: grave Hi, while a keyring named mozilla gets created after installation of the plugin it doesn't get any passwords stored in it. In the console I'm seeing: $ iceweasel (process:12616): GLib-CRITICAL **: g_slice_set_config: assertion 'sys_page_size == 0' failed (iceweasel:12616): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::sm-connect after class was initialised (iceweasel:12616): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::show-crash-dialog after class was initialised (iceweasel:12616): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::display after class was initialised (iceweasel:12616): GLib-GObject-WARNING **: Attempt to add property GnomeProgram::default-icon after class was initialised Could not check applicable rules for about:blank Could not check applicable rules for about:blank When clicking remember password nothing ends up in the keyring as seahorse shows. I'd appreciate any hints on howto debug this further. Cheers, -- Guido -- System Information: Debian Release: jessie/sid APT prefers testing APT policy: (990, 'testing'), (500, 'testing-updates'), (500, 'unstable'), (1, 'experimental') Architecture: amd64 (x86_64) Kernel: Linux 3.14.0-rc1+ (SMP w/4 CPU cores) Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8) Shell: /bin/sh linked to /bin/dash Versions of packages xul-ext-gnome-keyring depends on: ii icedove24.3.0-2 ii iceweasel 24.3.0esr-1 ii libc6 2.18-4 ii libgcc11:4.8.2-16 ii libglib2.0-0 2.38.2-5 ii libgnome-keyring0 3.8.0-2 ii libnspr4 2:4.10.3-1 ii libstdc++6 4.8.2-16 xul-ext-gnome-keyring recommends no packages. xul-ext-gnome-keyring suggests no packages. -- no debconf information -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of unsubscribe. Trouble? Contact listmas...@lists.debian.org
