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 678880 - fails to run with GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown
fails to run with GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown
Status: RESOLVED DUPLICATE of bug 677023
Product: gnome-screenshot
Classification: Core
Component: general
3.4.x
Other Linux
: Normal minor
: ---
Assigned To: gnome-screenshot-maint
gnome-screenshot-maint
Depends on:
Blocks:
 
 
Reported: 2012-06-26 13:57 UTC by Sam Morris
Modified: 2012-06-26 14:46 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Sam Morris 2012-06-26 13:57:57 UTC 
$ gnome-screenshot

** (gnome-screenshot:290953): WARNING **: Unable to use GNOME Shell's builtin screenshot interface, resorting to fallback X11. Error: GDBus.Error:org.freedesktop.DBus.Error.ServiceUnknown: The name org.gnome.Shell was not provided by any .service files

I have gnome-shell installed, through I'm using fallback mode. There's no org.gnome.Shell.service file in /usr/share/dbus-1/services, though there do exist org.gnome.Shell.CalendarServer.service and org.gnome.Shell.HotplugSniffer.service.
Comment 1 Sam Morris 2012-06-26 14:25:45 UTC 
I just noticed that gnome-screenshot now dumps things in ~/Pictures by default, so it was working, but the lack of any feedback indicating that this was the case, combined with the error message, mislead me.

I suggest retitling the bug to "Spurious ServiceUnknown error message" or something like that. You could also change gnome-screenshot to print the saved screenshot filename to stdout so that people running it from the command line at least can find out that a screenshot was taken.
Comment 2 André Klapper 2012-06-26 14:38:35 UTC 
Boils down to the same problem as bug 669629.

*** This bug has been marked as a duplicate of bug 669629 ***
Comment 3 Sam Morris 2012-06-26 14:39:44 UTC 
No, I'm not calling for the interactive mode to become the default. Just for the misleading error message to go away.
Comment 4 Cosimo Cecchi 2012-06-26 14:46:27 UTC 
Thanks for taking the time to report this bug.
This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade.

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