Bug#907490: gnome-shell: Unrecoverable failure in required component org.gnome.Shell.desktop

Simon McVittie smcv at debian.org
Sun Sep 2 15:36:18 BST 2018


Control: tags -1 + moreinfo

On Tue, 28 Aug 2018 at 12:45:05 -0500, william l-k wrote:
> The portion of the log near the times of start attempts had sections like
> these:
> 
> Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in
> required component org.gnome.SettingsDaemon.Power.desktop
> Aug 28 10:13:07 Username dbus-daemon[603]: [system] Activating via systemd:
> service name='org.freedesktop.hostname1' unit='dbus-org.freedesktop.hostna
> Aug 28 10:13:07 Username gnome-session-binary[8534]: Unrecoverable failure in
> required component org.gnome.SettingsDaemon.XSettings.desktop
> Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App
> 'org.gnome.SettingsDaemon.Wacom.desktop' exited with code 1
> Aug 28 10:13:07 Username gnome-session-binary[8534]: WARNING: App
> 'org.gnome.SettingsDaemon.Clipboard.desktop' exited with code 1
> Aug 28 10:13:07 Username gnome-session[8534]: Unable to init server: Could not
> connect: Connection refused
> Aug 28 10:13:07 Username unknown[8630]: Cannot open display:
> Aug 28 10:13:07 Username dbus-daemon[8532]: [session uid=1000 pid=8532]
> Activating via systemd: service name='org.gtk.vfs.Daemon' unit='gvfs-daemon.se
> Aug 28 10:13:07 Username gnome-session[8534]: Unable to init server: Could not
> connect: Connection refused

This looks as though these various programs were unable to connect to an
X or Wayland display: that's a symptom, not a cause. If you go further
back in the log, are there any log messages from gdm, gnome-shell or
Xorg that might indicate why the X or Wayland display could not start?

Thanks,
    smcv



More information about the pkg-gnome-maintainers mailing list