On Sun, Oct 18, 2015 at 02:31:36PM +0100, Simon McVittie wrote: >On 17/10/15 13:44, David Härdeman wrote: >> Turns out that gnome-keyring-daemon isn't running and >> gnome-settings-daemon does a sync dbus call to gnome-keyring-daemon for every >> media key press (see set_launch_context_env() in >> gnome-settings-daemon-3.18.1/plugins/media-keys/gsd-media-keys-manager.c), >> a call with a 25s timeout. > >Given your description, I'm surprised those calls time out. Normally, a >D-Bus call to a service that isn't running and can't be autostarted will >complete quickly (a fraction of a second), with a NameHasNoOwner error >reply sent back by the dbus-daemon itself. > >The only calls that should time out are: > >* a call to a service that is running, but doesn't reply for some > reason, for instance because of a bug or because it was SIGSTOP'd > >* a call that triggers autostarting, but where the autostart attempt > doesn't work fast enough to get a reply within the time limit > >Please check your syslog (or systemd Journal) for any warning messages >that look relevant?
I have a line like this in /var/log/user.log for every keypress (25s later when the actual action takes place): Oct 15 00:18:46 zeus gnome-session[29673]: (gnome-settings-daemon:29750): media-keys-plugin-WARNING **: Failed to call GetEnvironment on keyring daemon: Timeout was reached And I straced gnome-settings-daemon to see that it does timeout from a poll() call before printing the above line... Looking at glib2.0-2.42.1/gio/gdbusconnection.c, line 1976, the default timeout is indeed 25 seconds. Here's a similar bug report: https://bbs.archlinux.org/viewtopic.php?id=180075 I do agree that the timeout (instead of instant failure) is weird though... -- David Härdeman
