Bug 1393380

Summary: DBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager
Product: [Fedora] Fedora Reporter: customercare
Component: nemoAssignee: leigh scott <leigh123linux>
Status: CLOSED NOTABUG QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 24CC: andy, fedora, leigh123linux, miketwebster
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-11-09 12:45:05 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description customercare 2016-11-09 12:37:43 UTC 
Description of problem:

(nemo:19359): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Initializing nemo-image-converter extension

The Message states correctly, that there is no servicefile for systemd which has the requested name in it. ( I assume systemd is meant )

Version-Release number of selected component (if applicable):

3.0.6 FC24 64bit

How reproducible:

start it in a bash by hand

Additional Note:

I may or may not, be a problem of this installation regarding dbus.
Comment 1 leigh scott 2016-11-09 12:45:05 UTC 
The warning is expected when running as sudo or root, running it as normal user doesn't produce it.


[leigh@main_pc ~]$ nemo
[leigh@main_pc ~]$ sudo nemo
[sudo] password for leigh: 

(nemo:6505): Gtk-WARNING **: Failed to register client: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.SessionManager was not provided by any .service files
Comment 2 Andy 2018-05-31 15:36:28 UTC 
I have the same issue on F28, and I'm not starting anything in the bash by hand.

My shutdown-dialog takes a long time (some 20 s) to open.

I have plenty of these errors when I'm running dbus-monitor when opening the shutdown-dialog.

See https://gitlab.gnome.org/GNOME/gnome-shell/issues/309