Description of problem:
How is it possible to change the default location for screenshots being stored to? On my system, the pictures are saved in /tmp for opening it with an external application, for instance mtPaint.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Click on the panel's button for xfce4-screenshooter plugin.
2. Choose "open with mtPaint"
3. mtPaint opens the screenshot from /tmp
Folder /tmp seems to be hard coded.
Usage of configured folder from rc file.
Default could be /var/cache/xfce4-screenshooter.
$ grep dir .config/xfce4/xfce4-screenshooter
.config/xfce4/xfce4-screenshooter seems to remain from an older version. The fedora package does not care about that file, it even works with different permanent settings if it is not available.
This seems to be very similiar to an upstream report.
The default location to store a screenshot is the last used location. Use 'Save' instead of 'Open with' and select the folder of your choice.
You still feel this is a bug we need to track?
(In reply to comment #3)
Sorry, but your statement is not true. When you save individually, the folder is kept also individually and not remembered somewhere.
I am wondering where the configuration is stored, none rc file or something like that found shortly.
And as just wrote, you have to use the option "open with" instead of "save". The application opens then the temporary file *always* from /tmp. Please take a look at the upstream bug report (already closed, but not implemented well). Upstream writes something about a cli switch -p that is not available with the Fedora package.
I discussed in #fedora with nirik and others about that a little bit, they had the opinion that there was nothing checked into git, maybe forgotten for about one year till now.
If you do not understand, I can try to explain again in another way.
So please keep this bug open. Thanks :)
Created attachment 473577 [details]
right option to select to get a file in /tmp
Not optimal, but I can change the value:
$ $ grep dir ~/.config/xfce4/xfce4-screenshooter
$ xfce4-screenshooter --fullscreen -s /tmp
(doesn't matter if you save or not)
$ grep dir ~/.config/xfce4/xfce4-screenshooter
$ xfce4-screenshooter --fullscreen -s /home/chris
$ grep dir ~/.config/xfce4/xfce4-screenshooter
I just re-checked it: The above is not necessary, just select 'Save' (your screenshot shows 'Open with'!) and save the file- Next time you select 'save' again, the same folder is opened.
For 'Open with' /tmp looks right to me. There is no reason to store a temporary file somewhere else but in /tmp. Even if you select 'Open with' the storage location is not changed: Next time 'Save' will open the previous location again.
The plugin only calls the xfce4-screenshooter binary with the last set options. It would be nice to have a preferences dialog for the plugin as well, but this is a usability question and I don't think our bugzilla is the right place for these discussions. Please nag upstream if you want this changed.
The plugin does not call the xfce4-screenshooter binary. The plugin just uses the same shared library as xfce4-screenshooter. the plugins also have a different configuration file stored at the same location as the others panel plugins config files. And the plugin has its own configuration dialog, available by right clicking the screenshooter button and clicking on 'Properties'.
Re the original issue, yes 'Open with' saves a temporary file to /tmp and does not use the directory in the preferences. This is not a bug, it was done on purpose: the screenshot is opened, you edit it and save it where you want. Adding yet another option in the UI for that sounds a bit too much. If you think this is really a major usability issue, you can file an enhancement request on bugzilla.xfce.org and I will consider it when I have more time.
And please stop hijacking old bug reports on bugzilla.xfce.org which are not 100% relevant, always open a new bug report when in doubt.
I am reopening this bug. Maybe due to my feature request.
What do you think about using a switch for ./configure to overrule the temp folder of the system (g_get_tmp_dir) that will be used?
If there is no value set, default will be to use g_get_tmp_dir which can be never empty. If there is a value but none existing folder with the specified path, a new folder will be created if possible due to user rights. In case of error, fallback to g_get_tmp_dir.
So, it will be at least possible for the builder or maintainer to decide which logic to use. I can understand that the usage of the last used "save" folder breaks with the implemented logic so far and would probably confuse users. Anyways, this should then also be possible to force the usage of the last save folder by a special value to that switch, maybe $LAST_SAVED or somehow.
$ grep dir ~/.config/xfce4/panel/*.rc
If you agree, I could provide a little patch. But of course, this should be discussed further in upstream.
(In reply to comment #8)
> The plugin does not call the xfce4-screenshooter binary. The plugin just uses
> the same shared library as xfce4-screenshooter. the plugins also have a
> different configuration file stored at the same location as the others panel
> plugins config files. And the plugin has its own configuration dialog,
> available by right clicking the screenshooter button and clicking on
But as the plugin skips the "Save as" dialog, there is no way to configure the default storage location, right?
> Re the original issue, yes 'Open with' saves a temporary file to /tmp and does
> not use the directory in the preferences. This is not a bug, it was done on
> purpose: the screenshot is opened, you edit it and save it where you want.
I fully agree.
> And please stop hijacking old bug reports on bugzilla.xfce.org which are not
> 100% relevant, always open a new bug report when in doubt.
While I agree one should not hijack old threads I think Raphael was right to speak up in this particular one. The -p switch mentioned in the bug report is not yet implemented, thus the bug is not resolved, at least not in the way that is described in the bug.
(In reply to comment #9)
> I am reopening this bug. Maybe due to my feature request.
IMHO feature requests should go into Xfce's bugzilla rather than ours.
> What do you think about using a switch for ./configure to overrule the temp
> folder of the system (g_get_tmp_dir) that will be used?
Nothing. /tmp is the only reasonable choice for temporary data.
> So, it will be at least possible for the builder or maintainer to decide which
> logic to use.
But this wouldn't solve your problem ether.
> If you agree, I could provide a little patch. But of course, this should be
> discussed further in upstream.
Yeah, upstream first. What I'd like to see is an option in the properties dialog of the plugin, but this means it's no longer consistent with the binary.
(In reply to comment #10)
Thanks for your comments.
As far as I understand the issue till now and to not overcomplicate it then, the best way would be to modify the Save/Open/Upload dialog to have the possibilites to see the current path setting, change it if needed by a button click that shows the "Save as" dialog and updates the path.
The options Open and Upload should be decoupled from the always needed save logic, so a separate only-save possibility wouldn't be needed any more. It's always possible to copy/move the picture with the file browser or choose "Save as" in an external application.
Although, I think /var/cache/xfce4-screenshooter is the better choice as a default location for screenshots, it will also make it easier to cleanup, instead of having it with other possible garbage in /tmp.
Could you please then reopen the upstream bug, also due to the non-existent -p switch? Maybe clone the bug report, it is not possible / allowed to me.
I will look for what I can do to suggest a patch to the GUI.
As far as I can see, the cronjob configured in /etc/cron.daily/tmpwatch does also clean some folders under /var/cache. So no problem to use the special folder /var/cache/xfce4-screenshooter. Why not provide a special cronjob inside the xfce4-screenshooter to enhance tmpwatch configuration.
Okay, now reported to upstream.