several g-s-d services are timing out when booting a live session

Bug #1750846 reported by Jean-Baptiste Lallement on 2018-02-21
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
gnome-settings-daemon (Ubuntu)
High
Iain Lane
Bionic
High
Iain Lane

Bug Description

The following g-s-d services are timing out when booting a live session:

gsd-media-keys
gsd-color
gsd-wacom
gsd-power

One impact at least is that the shortcut to launch a terminal doesn't work

From the journal:
[ 82.368253] ubuntu gsd-media-keys[1865]: Failed to grab accelerators: Timeout was reached (24)
[ 108.828263] ubuntu gsd-color[1863]: failed to get screens: Timeout was reached
[ 108.836334] ubuntu gsd-wacom[1836]: Failed to construct RR screen: Timeout was reached
[ 108.837764] ubuntu gsd-power[1823]: Could not create GnomeRRScreen: Timeout was reached

[ 245.337228] ubuntu gsd-media-keys[1865]: Could not find accelerator for accel id 175
^_ this last line is displayed when Ctrl+Alt+T is pressed to open a terminal

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.26.2-0ubuntu2
ProcVersionSignature: Ubuntu 4.13.0-32.35-generic 4.13.13
Uname: Linux 4.13.0-32-generic x86_64
ApportVersion: 2.20.8-0ubuntu10
Architecture: amd64
CasperVersion: 1.388
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 21 15:20:00 2018
LiveMediaBuild: Ubuntu 18.04 LTS "Bionic Beaver" - Alpha amd64 (20180221)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=C.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

Jean-Baptiste Lallement (jibel) wrote :
tags: added: rls-bb-incoming
Jean-Baptiste Lallement (jibel) wrote :

Full journal

Will Cooke (willcooke) on 2018-03-06
Changed in gnome-settings-daemon (Ubuntu Bionic):
importance: Undecided → High
Changed in gnome-settings-daemon (Ubuntu Bionic):
assignee: nobody → Iain Lane (laney)
tags: removed: rls-bb-incoming
Péter Prőhle (prohlep) wrote :

Is it possible, that my issue https://bugs.launchpad.net/bugs/1755106 has some connection with this issue, see the journalctl | grep -i key | grep -i failed > journalctl_key_failed.txt attachment there:

https://bugs.launchpad.net/ubuntu/+source/gnome-settings-daemon/+bug/1755106/+attachment/5082123/+files/journalctl_key_failed.txt

Iain Lane (laney) wrote :

I can reproduce this, trying to figure it out now.

Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in gnome-settings-daemon (Ubuntu):
status: New → Confirmed
Iain Lane (laney) wrote :

I injected a dbus.service.wants/ unit to run busctl --user monitor, here is its output for the record.

Not analysed yet, hoping it's going to contain something interesting when read in conjunction with...

Iain Lane (laney) wrote :

journal from the same boot

Iain Lane (laney) wrote :

journal:

Mar 26 14:58:58 ubuntu gsd-xsettings[1846]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist

I can't find where that gets on the bus though, which is annoying because it eventually does get there

Jeremy Bicha (jbicha) wrote :

Laney, see also LP: #1752083 then.

Iain Lane (laney) wrote :

I'm sure there are many reports of the symptoms caused by this bug, but I'm going to track the work here.

Iain Lane (laney) wrote :

Tried to turn off rate limiting in systemd, here's my attempt, looks better from a first glance

Iain Lane (laney) wrote :

journalctl | grep -v busctl

Iain Lane (laney) wrote :

Mar 26 16:33:58 ubuntu gsd-xsettings[1729]: Failed to get current display configuration state: GDBus.Error:org.freedesktop.DBus.Error.NameHasNoOwner: Name "org.gnome.Mutter.DisplayConfig" does not exist

...

Mar 26 16:34:00 ubuntu busctl[1419]: Sender=:1.13 Destination=org.freedesktop.DBus Path=/org/freedesktop/DBus Interface=org.freedesktop.DBus Member=RequestName
Mar 26 16:34:00 ubuntu busctl[1419]: UniqueName=:1.13
Mar 26 16:34:00 ubuntu busctl[1419]: MESSAGE "su" {
Mar 26 16:34:00 ubuntu busctl[1419]: STRING "org.gnome.Mutter.DisplayConfig";
Mar 26 16:34:00 ubuntu busctl[1419]: UINT32 1;
Mar 26 16:34:00 ubuntu busctl[1419]: };

Iain Lane (laney) wrote :

Mar 26 16:33:49 ubuntu busctl[1419]: Sender=:1.13 Destination=org.freedesktop.DBus Path=/org/freedesktop/DBus Interface=org.freedesktop.DBus Member=RequestName
Mar 26 16:33:49 ubuntu busctl[1419]: UniqueName=:1.13
Mar 26 16:33:49 ubuntu busctl[1419]: MESSAGE "su" {
Mar 26 16:33:49 ubuntu busctl[1419]: STRING "org.gnome.Shell";
Mar 26 16:33:49 ubuntu busctl[1419]: UINT32 1;

Mar 26 16:34:00 ubuntu busctl[1419]: Sender=:1.45 Destination=:1.13 Path=/org/gnome/Shell Interface=org.gnome.Shell Member=GrabAccelerators

this call times out

Mar 26 16:34:24 ubuntu gsd-media-keys[1768]: Failed to grab accelerators: Timeout was reached (24)

but whyyyyy

Iain Lane (laney) wrote :

I'll dupe this to the other slowness bug, it's probably the same thing.

What I found out before ali1234 came up with his analysis is that gsd-xsettings is taking a really long time to start up. If you get in while it's grinding, you can see that it's setting up its fontconfig monitor at the time. So it's probably the same thing.

Other things in the session startup rely on gsd-xsettings being ready, and they time out when it isn't.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers