Bug#800617: Fails to provide secrets
Mikhail Morfikov
mmorfikov at gmail.com
Thu Oct 8 08:25:43 UTC 2015
Package: gnome-keyring
Version: 3.18.0-2
Followup-For: Bug #800617
I've just upgraded the gnome-keyring package, and I think that didn't solve my
issues. I think it's the same situation as it was before, but there's another
thing worth mentioning.
When my openbox starts I have the following processes:
$ ps aux | grep gnome
morfik 16743 0.0 0.0 122748 516 ? Sl 09:52 0:00 /usr/bin
/gnome-keyring-daemon --daemonize --login
morfik 16891 0.0 0.2 216104 5676 ? Sl 09:52 0:00 /usr/lib/at-
spi2-core/at-spi2-registryd --use-gnome-session
When I do nothing, after a minute or so, the first process disappears. I'm not
sure whether this should happen or not, so I'm just sharing my observations
with you.
Anyways, I have two apps that I often use: gajim and ssh. When I type in a
terminal "gajim" after logging into my system, everything works just fine. I
mean the above processes stay the same, and there's no lag when the app starts.
I don't have to type any passwords manually in order to log into my jabber
accounts, so the keyring works. When I close the app and reopen it again, it
also works as expected. The problem is when I want to issue ssh command -- I
get lag here and the message in the log:
Oct 08 09:53:47 morfikownia gnome-keyring-daemon[16743]: The Secret Service was
already initialized
Still, gajim (when restarted) works just fine, but issuing ssh command again
gives the lag. It looks like they're separated somehow.
The funniest thing is that when I switch the order of issuing the two commands,
so in this case the ssh command would be the fist one after login, it works
just fine, with no lag and any message in the log. But when I start gajim after
that, there's a lag and the message in the log, and of course password prompts.
So it looks like there's just only one process (the first one started after
login) that can work just fine with gnome-keyring, and the others get a lag
when started.
Another observation is that I get doubled process when the lagged application
is starting:
$ ps aux | grep gnome
morfik 16743 0.0 0.3 205072 7292 ? Sl 09:52 0:00 /usr/bin
/gnome-keyring-daemon --daemonize --login
morfik 16891 0.0 0.2 216104 5676 ? Sl 09:52 0:00 /usr/lib/at-
spi2-core/at-spi2-registryd --use-gnome-session
morfik 17825 0.0 0.2 48992 4260 ? S 09:53 0:00 /usr/bin
/gnome-keyring-daemon --start --foreground --components=secrets
morfik 17933 0.0 0.2 48992 4268 ? S 09:53 0:00 /usr/bin
/gnome-keyring-daemon --start --foreground --components=secrets
The doubled process (17933) disappears after a minute or so.
I was testing this with and without the autostart files, and it's the same in
both cases.
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (990, 'unstable'), (500, 'testing'), (130, 'experimental')
Architecture: amd64 (x86_64)
Kernel: Linux 4.2.0-1-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages gnome-keyring depends on:
ii dbus-x11 1.10.0-3
ii dconf-gsettings-backend [gsettings-backend] 0.24.0-2
ii gcr 3.16.0-1
ii libc6 2.19-22
ii libcap-ng0 0.7.7-1
ii libcap2-bin 1:2.24-12
ii libgck-1-0 3.16.0-1
ii libgcr-base-3-1 3.16.0-1
ii libgcrypt20 1.6.3-2
ii libglib2.0-0 2.46.0-2
ii p11-kit 0.23.1-3
ii pinentry-gnome3 0.9.6-2
Versions of packages gnome-keyring recommends:
ii libpam-gnome-keyring 3.18.0-2
gnome-keyring suggests no packages.
-- Configuration Files:
/etc/xdg/autostart/gnome-keyring-pkcs11.desktop [Errno 2] No such file or directory: u'/etc/xdg/autostart/gnome-keyring-pkcs11.desktop'
/etc/xdg/autostart/gnome-keyring-secrets.desktop [Errno 2] No such file or directory: u'/etc/xdg/autostart/gnome-keyring-secrets.desktop'
/etc/xdg/autostart/gnome-keyring-ssh.desktop [Errno 2] No such file or directory: u'/etc/xdg/autostart/gnome-keyring-ssh.desktop'
-- no debconf information
More information about the pkg-gnome-maintainers
mailing list