#697104 gnome-screenshot broken after upgrade

Package:
gnome-screenshot
Source:
gnome-screenshot
Description:
screenshot application for GNOME
Submitter:
Daniel Pocock
Date:
2015-08-17 16:54:25 UTC
Severity:
important
#697104#5
Date:
2013-01-01 14:01:09 UTC
From:
To:
I just upgraded a desktop from squeeze to wheezy

I tried to take a screenshot of another UI issue, and found
gnome-screenshot is broken

It flashes the window, but the save dialog never appears, and I see this
error:

$ gnome-screenshot -d 2 -w

** (gnome-screenshot:4835): 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


Please note I am logged in to the Gnome classic desktop

#697104#15
Date:
2013-01-01 14:07:39 UTC
From:
To:
I discovered many reports about similar problems using a search engine

http://forums.linuxmint.com/viewtopic.php?f=47&t=103522

suggests adding --interactive, e.g.:

$ gnome-screenshot -d 2 -w --interactive


That seems to work, it still gives the error, but now I do see the save
dialog again

However,

- I now get hassled by another popup, asking me to confirm the other
command line settings

- it is not clear whether this is a deliberate change in behavior, or
just some side effect of using --interactive

#697104#20
Date:
2013-01-01 17:17:47 UTC
From:
To:
forcemerge 671831 697104
thanks

This is "expected" behaviour, i.e. an upstream decision, which we should
probably revert. See my comments at the upstream bug tracker.

See https://bugzilla.gnome.org/show_bug.cgi?id=669629

#697104#31
Date:
2013-01-01 17:23:46 UTC
From:
To:

I can confirm it was saving in ~/Pictures

As I normally use the CLI to invoke the application, I see the error
messages and came to the conclusion it was broken.  Other users like
myself would probably form the same conclusion.

Should those errors be appearing on the console?  Should another bug
be created for any of them?  The error on my console is not quite the
same as the error in 671831