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 780357 - Use gnome-screenshot setting auto-save-directory
Use gnome-screenshot setting auto-save-directory
Status: RESOLVED OBSOLETE
Product: gnome-settings-daemon
Classification: Core
Component: media-keys
unspecified
Other Linux
: Normal enhancement
: ---
Assigned To: gnome-settings-daemon-maint
gnome-settings-daemon-maint
Depends on:
Blocks:
 
 
Reported: 2017-03-21 16:05 UTC by Antonio Ospite
Modified: 2019-03-20 11:40 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Antonio Ospite 2017-03-21 16:05:53 UTC
I would be handy to use the auto-save-directory setting from gnome-screenshot (if set) when taking screenshots with the PrintScreen.

I tried to set it:
$ gsettings set org.gnome.gnome-screenshot auto-save-directory 'file:///tmp'
$ gsettings get org.gnome.gnome-screenshot auto-save-directory
'file:///tmp'

But hitting the PrintScreen still saves to $XDG_PICTURES_DIR.

I guess this is because using that dir is hardcoded in gnome-flashback/libscreenshot/gf-screenshot.c::get_filename()

Thanks,
   Antonio
Comment 1 Antonio Ospite 2017-03-21 21:53:45 UTC
I see that the PrintScreen triggered screenshot is initiated by gnome-settings-daemon: https://git.gnome.org/browse/gnome-settings-daemon/tree/plugins/media-keys/gsd-screenshot-utils.c#n164

GSD also hardcodes other parameters like include_pointer and include_border ignoring the ones from org.gnome.gnome-screenshot.

In fact it's not possible at all to include the pointer when capturing with PrintScreen.

Maybe this is a GSD bug instead of a gnome-flashback one.

Does it sound reasonable for GSD to re-use the settings from org.gnome.gnome-screenshot?
Comment 2 Antonio Ospite 2017-05-03 09:05:14 UTC
Reassigning to gnome-settings-daemon.
Comment 3 Antonio Ospite 2017-05-05 10:57:20 UTC
If the idea of reusing org.gnome.gnome-screenshot settings in gnome-settings-daemon makes sense I could provide a patch myself.

Let me know.

Thanks,
   Antonio
Comment 4 benjaoming 2018-05-09 12:30:57 UTC
I think that makes sense, Antonio!

It would be a nice compromise since the discussion on how to handle screenshots & PrintScreen has stalled since 2012. A lot of what people are missing from gnome-screenshot could be yielded back by having better configurability.

Also, distros could configure this behavior themselves (there are even arguments that silently saving PrintScreen key strokes is a security issues).
Comment 5 Antonio Ospite 2018-05-11 07:13:20 UTC
The doubt if it's worth spending time on it. :)

I noticed the strange behavior the one time I used PrintScreen, but then I haven't used PrintScreen in more than one year and forgot about it.

If G-S-D maintainers too think that reusing org.gnome.gnome-screenshot settings make sense I can take another look.

Ciao,
   Antonio
Comment 6 GNOME Infrastructure Team 2019-03-20 11:40:52 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-settings-daemon/issues/323.