Open alexarnaud opened 6 years ago
I had mixed this up with a screensaver issue. This too should probably pop up a dialog, in this case to ask whether to cancel or try another location.
I just found that an error dialog was exactly what I got when I made a screenshot, selected a folder to save it in, moved that folder to the trash, and then tried to save. No hang, no heavy CPU use, just an error dialog asking for another location.
The Debian report says no issue with a deleted folder, so I tried removing both read and write permissions and again the error dialog came up fine.
For your 1.20.0 tests, did you only update mate-utils or all of MATE?
Le 02/03/2018 à 19:01, lukefromdc a écrit :
I just found that an error dialog was exactly what I got when I made a screenshot, selected a folder to save it in, moved that folder to the trash, and then tried to save. No hang, no heavy CPU use, just an error dialog asking for another location.
You've to save a screenshot on the location first. Make the location unreadable with chmod 000 on it and relaunch mate-screenshot.
The Debian report says no issue with a deleted folder, so I tried removing both read and write permissions and again the error dialog came up fine.
For your 1.20.0 tests, did you only update mate-utils or all of MATE?
All the Mate package.
Best regards, Alex.
OK, that confirms it. The issue appears on first opening mate-screenshot when the previously written location cannot be accessed as as default save location but does exist.
Still not fixed in Ubuntu Mate 20.04.
Advice for whoever encounters this bug: you can fix it by entering this command in a terminal:
gsettings set org.mate.screenshot last-save-directory ''
(at the end of the command, it's two simple quotes, not a double quote).
Expected behaviour
No hangs
Actual behaviour
mate-screenshot hangs when storage-folder is not accessible
Steps to reproduce the behaviour
MATE general version
Tested on 1.16 and 1.20
Package version
1.16.0-1 and 1.20.0-1
Linux Distribution
Debian Stretch and Debian Sid
Link to downstream report of your Distribution
This report is the forward of https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=891362