Gimp Can Not Load an Existing png File Created by my Delayed Screenshot starter
GIMP version: 2.10.8 just after being installed as a snap install
Operating System: Xbuntu 16.04.6 LTS currently running with linux kernel 4.4.0-143-generic x86_64
Package: sudo snap install gimp
followed by sudo snap connect gimp:removable-media
Description of the bug
In order to make screenshots including dropdown menus with the selection, the cursor and the like, I have created an xfce4 starter issuing the command
xfce4-screenshooter -fmd 4 -o gimp
4 seconds after the starter is activated. I was using gimp 2.8.22 before and there instead of gimp
the command was gimp-2.8
and this starter worked as expected. After installing version 2.10.8 instead, it does not work any longer because gimp can not load the png file created in /tmp
. After I had adapted the starter command as described before and when using it, after 4 seconds delay a screenshot is taken, it is stored in a png file in /tmp/Bildschirmfoto_yyyy-mm-dd_hh-nn-ss.png
where yyyy
is the year, mm
the month, dd
the day, hh
the hour, nn
the minute, ss
the second when the screenshot is taken.
Then my starter invokes Gimp. Unfortunately Gimp can not open this file. Instead there is an error message (this is on a German system, so the error message is in German):
»/tmp/Bildschirmfoto_2019-03-26_20-02-39.png« konnte nicht geöffnet werden: Datei »/tmp/Bildschirmfoto_2019-03-26_20-02-39.png« konnte nicht zum Lesen geöffnet werden: No such file or directory
I have double checked: the file exists and it is a valid screenshot: Double-clicking on it opens the screenshot in ristretto.
I also tried to open this file from Gimp itself. I even can’t navigate to /tmp
. The file selection menu does not show me the content of this directory (there are some png files in it), it just proceeds to a subdirectory containing a pdf file and offers this directory to select from!
I also tried to start gimp from a command line in order to start with that png file right away and this also proves the existence of the screenshot file to be shown by Gimp:
v@v-W:~$ ls -l /tmp/Bildschirmfoto_2019-03-26_20-02-39.png
-rw-rw-r-- 1 verwalter verwalter 85882 2019-03-26 21:33 /tmp/Bildschirmfoto_2019-03-26_20-02-39.png
v@v-W:~$ gimp -n /tmp/Bildschirmfoto_2019-03-26_20-02-39.png
ln: failed to create symbolic link '/home/verwalter/snap/gimp/130/.config/gtk-2.0/gtkfilechooser.ini': File exists
Gtk-Message: 21:35:18.112: Failed to load module "canberra-gtk-module"
Gtk-Message: 21:35:18.113: Failed to load module "canberra-gtk-module"
/snap/gimp/130/usr/bin/gimp: Gimp-Widgets-WARNUNG: parse_iso_codes: error parsing '/build/gimp/parts/gimp/install/usr/share/xml/iso-codes/iso_639.xml': No such file or directory
Gtk-Message: 21:35:19.737: Failed to load module "canberra-gtk-module"
Gtk-Message: 21:35:19.738: Failed to load module "canberra-gtk-module"
v@v-W:~$ # in this situation the error message from above
I checked that Gimp can display other png files which are not located in /tmp
.
I also copied the same file to somewhere in my home directory and to my great surprise Gimp could work with this file there!
What‘s wrong here? Do the Gtk-messages give a clue?
Reproduction
Is the bug reproducible? Always
Reproduction steps:
- create the attached png file in
/tmp
- try to open it with gimp
- meditate on the error message
…
Expected result: gimp opens the png file
Actual result: it issues an error message, see above.
Additional information
If you have a backtrace for a crash or a warning, paste it here. It is not a crash.