Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop

[Jani Uusitalo]

I've had this happen a couple of times now since upgrading to 18.04: soon (perhaps within a minute) after logging in, Gnome session ends abruptly and I'm thrown back to the login screen. IIRC, in both instances this occurred on the first login after boot, so it does not reoccur on the subsequent re-login, and not on every login (very rarely in fact), and for now I have no better steps to reproduce this other than "boot, log in".

Bug #1663839 (reported against 17.04) seems similar, as does bug #1731428 (reported against 17.10).

journalctl output during the issue:

Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
Apr 16 07:00:30 saegusa gnome-session-binary[4342]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
Apr 16 07:00:30 saegusa gnome-session-binary[4342]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Apr 16 07:00:30 saegusa gnome-session[4342]: gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Apr 16 07:00:30 saegusa gnome-session-binary[4342]: CRITICAL: We failed, but the fail whale is dead. Sorry....

ProblemType: Bug
DistroRelease: Ubuntu 18.04
Package: gnome-settings-daemon 3.28.1-0ubuntu1
ProcVersionSignature: Ubuntu 4.15.0-15.16-generic 4.15.15
Uname: Linux 4.15.0-15-generic x86_64
ApportVersion: 2.20.9-0ubuntu4
Architecture: amd64
CurrentDesktop: ubuntu:GNOME
Date: Mon Apr 16 17:07:14 2018
InstallationDate: Installed on 2016-10-13 (550 days ago)
InstallationMedia: Ubuntu-Server 16.04.1 LTS "Xenial Xerus" - Release amd64 (20160719)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=fi_FI.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-settings-daemon
UpgradeStatus: No upgrade log present (probably fresh install)

[Launchpad Janitor (janitor)]

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

[Dane Powell (danepowell)]

I'm seeing this on 18.04 as well, gnome-settings-daemon 3.28.1-0ubuntu1.

Jul 30 06:52:10 bean gnome-session[1964]: gnome-session-binary[1964]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout
Jul 30 06:52:10 bean gnome-session-binary[1964]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout
Jul 30 06:52:10 bean gnome-session-binary[1964]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop
Jul 30 06:52:10 bean gnome-session[1964]: gnome-session-binary[1964]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Jul 30 06:52:10 bean gnome-session-binary[1964]: CRITICAL: We failed, but the fail whale is dead. Sorry....

Additionally, after this happens it seems like Gnome Tweak Tools loses all of my keyboard customizations (such as switching ctrl-caps).

[richard (waneyvin)]

I have similar problem,
Unrecoverable failure in required component org.gnome.Shell.desktop
and
CRITICAL: We failed, but the fail whale is dead. Sorry....
and some Unable to get on D-Bus

My desktop is still working, some third party software like firefox is ok,
BUT gedit cannot launch, gnome-terminal cannot launch, settings cannot launch and most of gnome desktop apps are not able to launch.

I had tried to turn off Nvidia graphic card and using native intel, but those basic apps are still not able to launch.

Please help!
Ubuntu 18.04

[Rob Speer (rob-speer)]

Just had the same thing happen to me, on recently-updated Ubuntu 18.04.

Here are my journalctl entries from the crash (including the one from 2 seconds before in case they're relevant):

```
Oct 23 15:27:01 bad-horse code.desktop[3875]: [main 3:27:01 PM] update#setState idle
Oct 23 15:27:01 bad-horse code.desktop[3875]: bash: cannot set terminal process group (-1): Inappropriate ioctl for device
Oct 23 15:27:01 bad-horse code.desktop[3875]: bash: no job control in this shell
Oct 23 15:27:03 bad-horse gnome-session[1891]: gnome-session-binary[1891]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
Oct 23 15:27:03 bad-horse gnome-session[1891]: gnome-session-binary[1891]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 23 15:27:03 bad-horse gnome-session-binary[1891]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
Oct 23 15:27:03 bad-horse gnome-session-binary[1891]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
Oct 23 15:27:03 bad-horse gnome-session-binary[1891]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Oct 23 15:27:03 bad-horse kernel: rfkill: input handler enabled
Oct 23 15:27:03 bad-horse gnome-shell[1999]: gnome-shell: Fatal IO error 0 (Success) on X server :1.
```

[Andrey Arapov (andrey-arapov)]

Just got the same, shortly after I logged in, I opened VirtualBox (haven't started the VM yet), then Google Chrome -> went to my mails and ... just got logged out of my session!

Ubuntu 18.04; gnome-session-bin 3.28.1-0ubuntu3.

Logs:
--------------------------------------------------------------------------------
Jan 08 10:21:27 REDACTED gnome-session[4856]: gnome-session-binary[4856]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout
Jan 08 10:21:27 REDACTED gnome-session[4856]: gnome-session-binary[4856]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Keyboard.desktop
Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: WARNING: Application 'org.gnome.SettingsDaemon.Keyboard.desktop' failed to register before timeout
Jan 08 10:21:27 REDACTED gnome-session-binary[4856]: CRITICAL: We failed, but the fail whale is dead. Sorry....
Jan 08 10:21:27 REDACTED virtualbox.desktop[5400]: ICE default IO error handler doing an exit(), pid = 5400, errno = 11
Jan 08 10:21:27 REDACTED bluetoothd[2624]: Endpoint unregistered: sender=:1.107 path=/MediaEndpoint/A2DPSource
Jan 08 10:21:27 REDACTED bluetoothd[2624]: Endpoint unregistered: sender=:1.107 path=/MediaEndpoint/A2DPSink
Jan 08 10:21:27 REDACTED kernel: rfkill: input handler enabled
Jan 08 10:21:27 REDACTED gnome-shell[4958]: gnome-shell: Fatal IO error 0 (Success) on X server :1.
Jan 08 10:21:27 REDACTED polkitd(authority=local)[2802]: Unregistered Authentication Agent for unix-session:3 (system bus name :1.100, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_U
Jan 08 10:21:27 REDACTED at-spi-bus-launcher[4934]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":1"
Jan 08 10:21:27 REDACTED at-spi-bus-launcher[4934]: after 145 requests (145 known processed) with 0 events remaining.
Jan 08 10:21:27 REDACTED gsd-power[5096]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
Jan 08 10:21:27 REDACTED gsd-wacom[5117]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
Jan 08 10:21:27 REDACTED gsd-xsettings[5118]: gsd-xsettings: Fatal IO error 104 (Connection reset by peer) on X server :1.
Jan 08 10:21:27 REDACTED gsd-color[5141]: gsd-color: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
Jan 08 10:21:27 REDACTED gsd-clipboard[5137]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
Jan 08 10:21:27 REDACTED gsd-media-keys[5149]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
Jan 08 10:21:27 REDACTED gnome-terminal-[5507]: gnome-terminal-server: Fatal IO error 11 (Resource temporarily unavailable) on X server :1.
Jan 08 10:21:27 REDACTED gsd-color[4623]: failed to connect to device: Failed to connect to missing device /org/freedesktop/ColorManager/devices/xrandr_BenQ_Corporation_ZOWIE_XL_LCD_BCH00737SL0_arno_1000
Jan 08 10:21:27 REDACTED systemd[4821]: gnome-terminal-server.service: Main process exited, code=exited, status=1/FA...

[Andrei (andreic)]

Happens to me as well with the same error. Thought it might be related to the Nvidia driver, but the initial reporter clearly mentions it only started to happen after upgrading to 18.04. Have any of you guys managed to track down the issue or find a workaround?

Thanks!

[Sebastien Bacher (seb128)]

Could those having the issue add their journalctl log from the boot which showed the bug? Also comment #6 is about org.gnome.SettingsDaemon.Keyboard.desktop which is a different component (and it looks like xorg got issue and that impacted other components too)

[Jani Uusitalo (uusijani)]

Here you go. Had this occur twice in a row just now, so my original theory of the second login never failing was false.

[Sebastien Bacher (seb128)]

There is not much info in the log :/ Would it be possible to edit org.gnome.SettingsDaemon.Color.desktop to add a --debug to the Exec line and get a log with that next time you hit the issue?

[Jani Uusitalo (uusijani)]

Sure, I've now set it up thus and will post the results once I hit this again (it seems pretty unpredictable, so could be anything from days to weeks).

[Jani Uusitalo (uusijani)]

...except that --debug isn't one of gsd-color's recognized parameters, and adding it caused GDM to fail to start. I changed it to --verbose which is available.

    10.08 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color --help-all
    Usage:
      gsd-color [OPTION?] color

    Help Options:
      -h, --help Show help options
      --help-all Show all help options
      --help-gtk Show GTK+ Options

    GTK+ Options
      --class=CLASS Program class as used by the window manager
      --name=NAME Program name as used by the window manager
      --gdk-debug=FLAGS GDK debugging flags to set
      --gdk-no-debug=FLAGS GDK debugging flags to unset
      --gtk-module=MODULES Load additional GTK+ modules
      --g-fatal-warnings Make all warnings fatal
      --gtk-debug=FLAGS GTK+ debugging flags to set
      --gtk-no-debug=FLAGS GTK+ debugging flags to unset

    Application Options:
      --exit-time Exit after n seconds time
      --dummy-name Name when using the dummy daemon
      -v, --verbose Verbose
      --display=DISPLAY X display to use

There's also --gtk-debug and --gdk-debug, but I could do with a little help for what to select for those, as just giving 'all' seems a little counterproductive (for instance, "touchscreen" and "interactive" don't seem very useful here).

    10.03 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color --gtk-debug help
    Supported debug values: misc plugsocket text tree updates keybindings multihead modules geometry icontheme printing builder size-request no-css-cache baselines pixel-cache no-pixel-cache interactive touchscreen actions resize layout all help

    10.04 jani@saegusa:~$ LC_ALL=C /usr/lib/gnome-settings-daemon/gsd-color --gdk-debug help
    Supported debug values: events misc dnd xim nograbs input cursor multihead xinerama draw eventloop frames settings opengl all help
    Error parsing option --gdk-debug

(Looks like --gdk-debug reports an error with 'help', despite having just listed it as one of the options.)

[Sebastien Bacher (seb128)]

right, sorry about that, --verbose is the right option indeed

[Jani Uusitalo (uusijani)]

A new log; still nothing useful from colord AFAICT, despite the --verbose.

[Sebastien Bacher (seb128)]

Indeed, not much outside of
WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout

it could be that the issue is on the colord service side...

[Dave Mann (cwo4mann)]

I'm struggling with 18.10: Lots of bad things happen but this is worst: This happens every time more than 2 applications are open.

{code}
Unrecoverable failure in required component org.gnome.Shell.desktop
{code}

[cmcint01 (atlyetione)]

I'm seeing similar issue using nvidia card with latest NVIDIA driver update 410.
-----------------------------------------------------------------------
error log:

gnome-session-b

Unrecoverable failure in required component org.gnome.Shell.desktop

Priority: 3

---------------------------------------------------------------------
Not much else detailed except on ubuntu 18.04 with latest updates.

after last update started seeing the above errors. Also keyboard intermittently freezes. Thanks.

[Argyris Megalios (argymeg)]

This just happened to me twice as well, after the first reboot after upgrading the kernel to 4.18.0-16-generic. System had been running for a few days (with several reboots) on 4.18.0-15-generic with no issues. After logging in for the second time without rebooting everything is good so far. Attaching the journal up from boot up to the crash moment.

[leihao (litou)]

I had this issue until i uninstalled chrome remote desktop.

[elodg (generic-r)]

I too am affected by this bug. I am attaching my syslog because I have unrecoverable failures in multiple components:
org.gnome.Shell.desktop
org.gnome.SettingsDaemon.Sharing.desktop
org.gnome.SettingsDaemon.Color.desktop

[Olivier Gagnon (gagnono)]

Same, happens once a day

Here's all my "important" logs.

11:44:31 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
11:44:30 pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
11:44:16 gnome-session-b: CRITICAL: We failed, but the fail whale is dead. Sorry....
11:44:16 gnome-session-b: CRITICAL: We failed, but the fail whale is dead. Sorry....
11:44:16 gnome-session-b: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
11:42:46 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
11:42:43 pulseaudio: [pulseaudio] backend-ofono.c: Failed to register as a handsfree audio agent with ofono: org.freedesktop.DBus.Error.ServiceUnknown: The name org.ofono was not provided by any .service files
11:42:10 spice-vdagent: Cannot access vdagent virtio channel /dev/virtio-ports/com.redhat.spice.0
11:42:07 kernel: ipheth 3-3:4.2: ipheth_rcvbulk_callback: urb status: -71
11:41:57 wpa_supplicant: dbus: Failed to construct signal
11:41:57 wpa_supplicant: dbus: Failed to construct signal
11:41:57 wpa_supplicant: dbus: wpa_dbus_get_object_properties: failed to get object properties: (none) none
11:41:44 kernel: mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1554910894 SOCKET 0 APIC 6 microcode 800111c
11:41:44 kernel: mce: [Hardware Error]: PROCESSOR 2:800f11 TIME 1554910894 SOCKET 0 APIC 6 microcode 800111c
11:41:44 kernel: mce: [Hardware Error]: TSC 0 ADDR 1ffffbaf11790 MISC d012000101000000 SYND 4d000000 IPID 500b000000000
11:41:44 kernel: mce: [Hardware Error]: CPU 6: Machine Check: 0 Bank 5: bea0000000000108

[limkokhole (limkokhole)]

It happen to me just now, grep by "gnome-session-binary":

5059:Apr 18 15:20:14 xiaobai-Latitude-E6430s gnome-session[3062]: gnome-session-binary[3062]: WARNING: App 'spice-vdagent.desktop' exited with code 1
5060:Apr 18 15:20:14 xiaobai-Latitude-E6430s gnome-session-binary[3062]: WARNING: App 'spice-vdagent.desktop' exited with code 1
5087:Apr 18 15:20:16 xiaobai-Latitude-E6430s gnome-session-binary[3062]: Entering running state
5796:Apr 18 15:20:26 xiaobai-Latitude-E6430s dbus-daemon[4095]: [session uid=1000 pid=4095] Activating service name='org.gnome.ScreenSaver' requested by ':1.19' (uid=1000 pid=4098 comm="/usr/lib/gnome-session/gnome-session-binary " label="unconfined")
5803:Apr 18 15:20:26 xiaobai-Latitude-E6430s gnome-session[4098]: gnome-session-binary[4098]: WARNING: Could not parse desktop file gnome-user-share-obexpush.desktop or it references a not found TryExec binary
5804:Apr 18 15:20:26 xiaobai-Latitude-E6430s gnome-session-binary[4098]: WARNING: Could not parse desktop file gnome-user-share-obexpush.desktop or it references a not found TryExec binary
5805:Apr 18 15:20:26 xiaobai-Latitude-E6430s gnome-session[4098]: gnome-session-binary[4098]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary
5806:Apr 18 15:20:26 xiaobai-Latitude-E6430s gnome-session-binary[4098]: WARNING: Could not parse desktop file caribou-autostart.desktop or it references a not found TryExec binary
5883:Apr 18 15:20:31 xiaobai-Latitude-E6430s gnome-session[4098]: gnome-session-binary[4098]: WARNING: App 'spice-vdagent.desktop' exited with code 1
5884:Apr 18 15:20:31 xiaobai-Latitude-E6430s gnome-session-binary[4098]: WARNING: App 'spice-vdagent.desktop' exited with code 1
5950:Apr 18 15:22:02 xiaobai-Latitude-E6430s gnome-session[4098]: gnome-session-binary[4098]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' failed to register before timeout
5951:Apr 18 15:22:02 xiaobai-Latitude-E6430s gnome-session[4098]: gnome-session-binary[4098]: CRITICAL: We failed, but the fail whale is dead. Sorry....
5952:Apr 18 15:22:02 xiaobai-Latitude-E6430s gnome-session-binary[4098]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Sharing.desktop
5954:Apr 18 15:22:02 xiaobai-Latitude-E6430s gnome-session-binary[4098]: WARNING: Application 'org.gnome.SettingsDaemon.Sharing.desktop' failed to register before timeout
5992:Apr 18 15:22:02 xiaobai-Latitude-E6430s gnome-session-binary[4098]: CRITICAL: We failed, but the fail whale is dead. Sorry....
6720:Apr 18 15:22:08 xiaobai-Latitude-E6430s dbus-daemon[4095]: [session uid=1000 pid=4095] Activating service name='org.gnome.ScreenSaver' requested by ':1.97' (uid=1000 pid=5292 comm="/usr/lib/gnome-session/gnome-session-binary " label="unconfined")
6723:Apr 18 15:22:08 xiaobai-Latitude-E6430s gnome-session[5292]: gnome-session-binary[5292]: WARNING: Could not parse desktop file gnome-user-share-obexpush.desktop or it references a not found TryExec binary
6724:Apr 18 15:22:08 xiaobai-Latitude-E6430s gnome-session-binary[5292]: WARNING: Could not parse desktop file gnome-user-share-obexpush.desktop or it references a not found TryExec bin...

[rbmorse (rbmorse)]

FWIW, I did not experience this issue until I changed the hardware platform.

Old system: Intel Haswell i7-4790, nVidia 970 GTX, ASUS X97 Pro, 32GB RAM

New system: AMD Ryzen 3700x, nVidia 2080 RTX, ASUS Crosshair Hero VIII, 64 GB RAM

[Martin Karlsson (foh1981)]

As comment #19, my issue was apparently with Chrome Remote Desktop. After uninstalling it, everything seems to be back and working.

* I had no hardware changes prior to my problems
* I'm running on AMD® A10-7800 radeon r7, integrated graphics
* After installing Chrome Remote Desktop, I noticed that the profile directory of Chrome had changed. Shortly after, possibly after my first remote session, the problem with Gnome Desktop began.
* Logging in to my wife's account, and then logging out and into mine, seemed to fix the problem for the session.

[logart (logart89)]

After updating my Ubuntu, i had to uninstall chrome desktop, it wouldn't let me to open up terminal or files app. Then i re-installed chrome desktop, try it with default settings and it was working, i changed the Display to 0 (20 default) on the python file and comments. It would not let me initiate the remote access this time. It says timeout after 1200000 mili seconds something of that sort. I just think it was worth mentioning it.

[Angel D. Segarra (angel-segarra)]

Getting this on 19.04

[Tero Gusto (tero-gusto)]

Also getting an org.gnome.SettingsDaemon.Color.desktop error using Ubuntu 18.04 with Nvidia graphics card, no Chrome Desktop installed. The Desktop drops into a black screen, with this text:

dev/sda1: clean, 123456/1234567 files, 1234567/12345678 blocks

I can get back into Ubuntu by pressing Alt+F2.

From journalctl -b:
nov 12 09:01:43 USER gnome-software[3843]: json_object_has_member: assertion 'member_name != NULL' failed
nov 12 09:01:43 USER gnome-software[3843]: g_strsplit: assertion 'string != NULL' failed
nov 12 09:01:43 USER gnome-software[3843]: g_strv_length: assertion 'str_array != NULL' failed
nov 12 09:01:43 USER PackageKit[3036]: get-updates transaction /20427_ababeceb from uid 1000 finished with success after 440ms
nov 12 09:01:50 USER gnome-session[1816]: gnome-session-binary[1816]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
nov 12 09:01:50 USER gnome-session-binary[1816]: WARNING: Application 'org.gnome.SettingsDaemon.Color.desktop' failed to register before timeout
nov 12 09:01:50 USER gnome-session-binary[1816]: Unrecoverable failure in required component org.gnome.SettingsDaemon.Color.desktop
nov 12 09:01:50 USER gnome-session[1816]: gnome-session-binary[1816]: CRITICAL: We failed, but the fail whale is dead. Sorry....
nov 12 09:01:50 USER gnome-session-binary[1816]: CRITICAL: We failed, but the fail whale is dead. Sorry....
nov 12 09:01:50 USER gnome-shell[1835]: gnome-shell: Fatal IO error 0 (Success) on X server :0.
nov 12 09:01:50 USER at-spi-bus-launcher[1819]: XIO: fatal IO error 11 (Resource temporarily unavailable) on X server ":0"
nov 12 09:01:50 USER at-spi-bus-launcher[1819]: after 71 requests (71 known processed) with 0 events remaining.
nov 12 09:01:50 USER gsd-xsettings[3061]: gsd-xsettings: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
nov 12 09:01:50 USER gsd-clipboard[3067]: gsd-clipboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
nov 12 09:01:50 USER gsd-media-keys[3093]: gsd-media-keys: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
nov 12 09:01:50 USER gsd-keyboard[3082]: gsd-keyboard: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
nov 12 09:01:50 USER gsd-power[3100]: gsd-power: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
nov 12 09:01:50 USER gsd-wacom[3143]: gsd-wacom: Fatal IO error 11 (Resource temporarily unavailable) on X server :0.
nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) UnloadModule: "libinput"
nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) systemd-logind: releasing fd for 13:66
nov 12 09:01:50 USER polkitd(authority=local)[1175]: Unregistered Authentication Agent for unix-session:c2 (system bus name :1.37, object path /org/freedesktop/PolicyKit1/AuthenticationAgent, locale en_US.UTF-8) (disconnected from bus)
nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) UnloadModule: "libinput"
nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) systemd-logind: releasing fd for 13:67
nov 12 09:01:50 USER /usr/lib/gdm3/gdm-x-session[1735]: (II) UnloadModule: "libinput"
nov 12 ...

[nico (nicolas-pourcelot)]

Same bug ('org.gnome.SettingsDaemon.Color.desktop' failed to register) for me, but no NVIDIA card involved :

VGA compatible controller: Intel Corporation Xeon E3-1200 v2/3rd Gen Core processor Graphics Controller (rev 09)

I'm using Ubuntu 18.04.3, and it happens randomly, but only since a few weeks...

[Konstantin Hollerith (hinnelinks)]

I'm using Ubuntu 18.04 since it came out, but are effected by this bug only since two weeks.
What I noticed: I have a couple of programs setup to start automatically (via gnome-session-properties). When I log in and get kicked out because of this bug, those programs where never started at all. On a normal Login they start fine.

[Phil Ayres (ayres-phil)]

Very similar issue to the other reports. I see this every few days when I login. Typically I go to Nautilus, mount an encrypted FUSE drive, open Chrome, then randomly the session just dies. Interesting, my dual monitors are reversed so the order of them is wrong (left is on the right, and vice versa). Restarting seems fine.

OS: Ubuntu 18.04.03
Kernel: Linux 4.4.0-148-generic x86_64 Ubuntu
Processor: Intel® Core™ i7-2600 CPU @ 3.40GHz × 8
Graphics: GeForce GTX 1060 6GB/PCIe/SSE2
GNOME: 3.28.2

I also have the Chrome Remote Desktop installed. I'll try removing it.

Relevant syslog attached for reference.

[Phil Ayres (ayres-phil)]

Following up on my previous comment, after removing Chrome Remote Desktop three weeks ago I have not had any crashes on login. That old program (which Chrome didn't register as being installed, but was running in the background) seems to be the source of the issue for me.

[Thinking Torus (thinking-torus)]

Fix:
If you search your journalctl output and find an event like this:
Jul 07 20:45:20 ubuntu dbus-daemon[1064]: [system] Activating via systemd: service name='org.freedesktop.ColorManager' unit='colord.service' requested by ':1.168' (uid=1000 pid=23634 comm="/usr/lib/gnome-settings-daemon/gsd-color " label="unconfined")

and the timestamp coincides with the second (successful) login (look for "GNOME Shell started" if you are using Gnome), and the first (failed) login doesn't have a matching event like the above, then the following might help:

# copy /lib/systemd/system/graphical.target to /etc/systemd/system/

# edit /etc/systemd/system/graphical.target, so that when you diff it against the original, you get something like this:
$ diff /lib/systemd/system/graphical.target /etc/systemd/system/graphical.target
14c14
< Wants=display-manager.service
---
> Wants=display-manager.service colord.service
16c16
< After=multi-user.target rescue.service rescue.target display-manager.service
---
> After=multi-user.target rescue.service rescue.target display-manager.service colord.service

# next time you reboot the issue should be gone.

Explanation:
gsd-color is invoked by org.gnome.SettingsDaemon.Color.desktop.
The event above is logged presumably when gsd-color requests the dbus service provided by colord.service.
One can reasonably guess a failed login happens when gsd-color makes the request but colord hasn't yet started, so it fails and when gnome shell gets tired waiting, it kills itself.
So we add colord as a dependency to be run prior to graphical.target.

[Thinking Torus (thinking-torus)]

Commenting on my own comment #32 above:
Somehow launchpad decided to break the lines following "display-manager.". The line breaks should not be there in the diff output.

[Tero Gusto (tero-gusto)]

This seems to have been fixed in Ubuntu 20.04.1 ...