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 780145 - Unrecoverable failure in required component org.gnome.SettingsDaemon.Sharing.desktop
Unrecoverable failure in required component org.gnome.SettingsDaemon.Sharing....
Status: RESOLVED DUPLICATE of bug 774813
Product: gnome-settings-daemon
Classification: Core
Component: sharing
3.23.x
Other Linux
: Normal critical
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2017-03-16 13:20 UTC by thirioux
Modified: 2017-03-16 13:26 UTC
See Also:
GNOME target: ---
GNOME version: 3.23/3.24


Description thirioux 2017-03-16 13:20:35 UTC 
Hi,

Using Ubuntu 17.04, GDM, GNOME 3.23.92 RC.
CPU Skylake, Nvidia proprietary or nouveau.

I often and randomly see this error in logs :

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

followed by :

CRITICAL: We failed, but the fail whale is dead. Sorry....

in gnome-sesssin-bin component.

It causes an immediate disconnection, back to GDM login screen if I use Nvidia. If I use Nouveau, sometimes it causes the same behaviour, sometimes changes the Gnome graphical session in TTY +=1.

It's easy to know if the session will fail : if I see Nautilus icons on my desktop (turned on in tweak-tool), it will be fully ok. If not, it will disconnect shortly after, 1 or 2 minutes, say.

If I use lightdm instead of gdm, the same bug happens.
Comment 2 thirioux 2017-03-16 13:26:15 UTC 
And :
1) in a buggy session, I cannot disconnect via Gnome system menu (before the crash) ;
2) I mainly use Intel GPU (optimus) but the bug happens using Nvidia (propr. or nouveau) GPU.
Comment 3 Bastien Nocera 2017-03-16 13:26:43 UTC 
Thanks for taking the time to report this.
This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 774813 ***