After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 729101 - Slow hotkey response in GNOME 3.12
Slow hotkey response in GNOME 3.12
Status: RESOLVED OBSOLETE
Product: gnome-keyring
Classification: Core
Component: general
3.12.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME keyring maintainer(s)
GNOME keyring maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2014-04-28 11:52 UTC by xgdgsc
Modified: 2021-06-18 10:41 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
journalctl -f (2.76 KB, text/x-log)
2014-04-28 15:46 UTC, xgdgsc
Details

Description xgdgsc 2014-04-28 11:52:52 UTC
On archlinux, gnome 3.12.1 custom shortcuts open becomes slow. For example press short cut defined for gnome system monitor ctrl+alt+m, it appears after 10 seconds sometimes much more, which makes you think it is not functioning at all.

related post: http://superuser.com/questions/742914/slow-hotkey-response-in-gnome-3-12
Comment 1 Bastien Nocera 2014-04-28 12:28:27 UTC
And obviously you tested that gnome-system-monitor launches quickly when run some other way?
I tested this, and gnome-system-monitor appears instantaneously here.
Comment 2 xgdgsc 2014-04-28 12:30:10 UTC
Yes, when launching in the shell search, instantly.
Comment 3 Bastien Nocera 2014-04-28 14:53:16 UTC
Launch "journalctl -f" and reproduce the problem. Do you see any errors?
Comment 4 xgdgsc 2014-04-28 15:46:16 UTC
Created attachment 275358 [details]
journalctl -f

4月 28 23:43:20 gsc-arch gnome-session[6154]: (gnome-settings-daemon:6209): media-keys-plugin-WARNING **: Failed to call GetEnvironment on keyring daemon: Timeout was reached
4月 28 23:43:28 gsc-arch gnome-session[6154]: Window manager warning: last_focus_time (17549790) is greater than comparison timestamp (17549788).  This most likely represents a buggy client sending inaccurate timestamps in messages such as _NET_ACTIVE_WINDOW.  Trying to work around...

seems relevant
Comment 5 Bastien Nocera 2014-04-28 15:50:39 UTC
(In reply to comment #4)
> 4月 28 23:43:20 gsc-arch gnome-session[6154]: (gnome-settings-daemon:6209):
> media-keys-plugin-WARNING **: Failed to call GetEnvironment on keyring daemon:
> Timeout was reached

That would be why then. Is gnome-keyring-daemon running?
Comment 6 xgdgsc 2014-04-28 15:57:07 UTC
Yes, there are two gnome-keyring-daemon processes.
Comment 7 Bastien Nocera 2014-04-28 15:59:01 UTC
(In reply to comment #6)
> Yes, there are two gnome-keyring-daemon processes.

That's not normal. I'll reassign this to gnome-keyring, as even if gnome-keyring-daemon is autostarted, it should still answer the query we send to it.
Comment 8 Letik 2015-10-26 12:16:05 UTC
Hi ! I still have this problem, but I see no workaround / fix about that ?
@xgdgsc, do you still have this problem ? Thanks !
Comment 9 André Klapper 2015-10-26 14:29:15 UTC
If you "still" have this problem, please provide version information.
Comment 10 Alexey 2015-12-04 07:48:03 UTC
Hi! I also have issue. My gnome shell version: GNOME Shell 3.14.4
As for example pressing "Super+L" for lock screen may work after minutes, also Shift+PrintSceen take a sometime to complete
Comment 11 Letik 2015-12-04 13:26:59 UTC
Sorry, I didn't see your previous mesage André. Here is the version is use :

local/libgnome-keyring 3.12.0-2
    GNOME keyring client library
local/gnome-shell 3.18.3-1 (gnome)
    The next generation GNOME Shell
local/gnome-session 3.18.1.2-1 (gnome)
    The GNOME Session Handler
Comment 12 Letik 2016-02-29 15:18:52 UTC
Hi, the bug still appears for me. But I realized that it only appears when I have gnome-screensaver launched.
Comment 13 Letik 2016-02-29 15:24:19 UTC
Here is the version installed on my system

local/gnome-keyring 1:3.18.3-1 (gnome)
    GNOME Password Management daemon
local/gnome-shell 3.18.3-3 (gnome)
    The next generation GNOME Shell
local/gnome-screensaver 3.6.1-13
    Legacy GNOME screensaver
local/gnome-session 3.18.1.2-1 (gnome)
    The GNOME Session Handler

Ask me if you need anything or if I can help in any way.
Thanks !
Comment 14 WD 2016-08-11 09:37:20 UTC
I have struggled with this bug for 2 years now on my laptop and I give up. I now have gnome 3.18.5 (fresh Ubuntu-Gnome 16.04.1) and it worse than ever. The bug is now encountered immediately after boot; in earlier versions it only occurred after some time. I have tried the suggestions in this thread and every single solution I found via Google. Could it be hardware related? Any other ideas?
Comment 15 WD 2016-08-11 09:38:54 UTC
I have struggled with this bug for 2 years now on my laptop and I give up. I now have gnome 3.18.5 (fresh Ubuntu-Gnome 16.04.1) and it worse than ever. The bug is now encountered immediately after boot; in earlier versions it only occurred after some time. I have tried the suggestions in this thread and every single solution I found via Google. Could it be hardware related? Any other ideas?
Comment 16 Andreas Kern 2017-05-12 07:43:55 UTC
running 'gnome-keyring-daemon' in a terminal after logging in solves the behavior for me.

to see the Timeout message i run 'journalctl -f' and there I see:

gnome-session[3614]: (gnome-software:3837): GsPlugin-WARNING **: could not lookup cached macaroon: Error calling StartServiceByName for org.freedesktop.secrets: Timeout was reached

this line appears twice for every time I run a terminal via my keyboard shortcut. They disappear after running `gnome-keyring-daemon` (without any params).
Comment 17 Antonios Hadjigeorgalis 2017-05-19 16:16:41 UTC
Andreas Kern's workaround has worked for me on Ubuntu 16.04
Comment 18 gwarah 2017-07-10 13:58:41 UTC
(In reply to xgdgsc from comment #0)
> On archlinux, gnome 3.12.1 custom shortcuts open becomes slow. For example
> press short cut defined for gnome system monitor ctrl+alt+m, it appears
> after 10 seconds sometimes much more, which makes you think it is not
> functioning at all.
> 
> related post:
> http://superuser.com/questions/742914/slow-hotkey-response-in-gnome-3-12

I'm on ubuntu 16.04 (up to dated) and until now this bugs is not solved. This solution suggested by @xgdgsc has been the only workaround I've been found.

I'm sharing this script using the command suggested in this post:

------------

#!/bin/bash

#
# Requisites user with sudo rights
#
echo "workaround to bug gnome_keyring_bug729101"
if [ $(pgrep gnome-keyring --list-full | wc -l) -gt 1 ]; then
    echo "killing all gnome-keyring processes"
    sudo killall gnome-keyring-daemon
    echo "please check if there's only one gnome-keyring process"
    echo "command: pgrep gnome-keyring --list-full"
else
    echo "It's ok!"    
fi

exit 0
------------
Comment 19 Antonios Hadjigeorgalis 2017-07-15 21:18:49 UTC
Several of us have resolved this on Ubuntu 16.04 by purging dbus-user-session.
Starting at response #67, this bug report contains additional context.
https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825

For me, dbus-user-session was installed as a dependency of flatpak and that is when my issue began.
Comment 20 frederik.feichtmeier 2017-07-16 17:29:53 UTC
(In reply to Antonios Hadjigeorgalis from comment #19)
> Several of us have resolved this on Ubuntu 16.04 by purging
> dbus-user-session.
> Starting at response #67, this bug report contains additional context.
> https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825
> 
> For me, dbus-user-session was installed as a dependency of flatpak and that
> is when my issue began.

Thank you! This fixed it for me! I also need to disable SSH Key Agent in the startup applications which also got enabled after installing flatpak.
Comment 21 Andreas Kern 2017-07-17 09:08:29 UTC
`apt remove dbus-user-session` fixed it for me

i had flatpack installed too, don't care much about it.
Comment 22 gwarah 2017-07-26 15:10:51 UTC
(In reply to Antonios Hadjigeorgalis from comment #19)
> Several of us have resolved this on Ubuntu 16.04 by purging
> dbus-user-session.
> Starting at response #67, this bug report contains additional context.
> https://bugs.launchpad.net/ubuntu/+source/gnome-keyring/+bug/1689825
> 
> For me, dbus-user-session was installed as a dependency of flatpak and that
> is when my issue began.

`sudo apt remove dbus-user-session` fixed it for me too.
Comment 23 Ramón Casero 2019-08-23 12:00:40 UTC
This also happens in Ubuntu disco dingo (19.04). A solution is running `gnome-keyring-daemon` on a terminal.

A related solution, to avoid having to type this every time, seems to be launching from Ubuntu "Startup Applications Preferences", and editing "SSH Key Agent" from

```
/usr/bin/gnome-keyring-daemon --start --components=ssh

```

to

```
/usr/bin/gnome-keyring-daemon
```

Uninstalling `dbus-user-session` or doing `sudo apt-get install --reinstall ca-certificates` doesn't do anything.
Comment 24 André Klapper 2021-06-18 10:41:08 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-keyring/-/issues/

Thank you for your understanding and your help.