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 757070 - GIMP crashing when a clipboard manager is running
GIMP crashing when a clipboard manager is running
Status: RESOLVED OBSOLETE
Product: GIMP
Classification: Other
Component: User Interface
2.8.14
Other Linux
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
: 772693 776502 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2015-10-24 18:37 UTC by Jan Prunk
Modified: 2018-05-24 15:50 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Jan Prunk 2015-10-24 18:37:02 UTC
Hello !

I noticed GIMP crashing in LXQT on Debian stable when copying cropped image into clipboard.
The error is:

~$ gimp DSC04720.jpg
(gimp:21861): Gimp-Widgets-CRITICAL **: gimp_device_info_set_device: assertion '(info->device == NULL && GDK_IS_DEVICE (device)) || (GDK_IS_DEVICE (info->device) && device == NULL)' failed
While parsing XMP metadata:
Error: No XMP packet found
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
(Details: serial 145808 error_code 3 request_code 18 minor_code 0)
(Note to programmers: normally, X errors are reported asynchronously;
that is, you will receive the error a while after causing it.
To debug your program, run it with the --sync command line
option to change this behavior. You can then get a meaningful
backtrace from your debugger if you break on the gdk_x_error() function.)

(script-fu:21866): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error

~$ dpkg -l |grep lxqt
ii liblxqt-globalkeys-ui0 0.9.0+20150926-1~bpo8+1 amd64 daemon used to register global keyboard shortcuts (ui files)
ii liblxqt-globalkeys0 0.9.0+20150926-1~bpo8+1 amd64 daemon used to register global keyboard shortcuts (shared libs)
ii liblxqt0:amd64 0.9.0+20151024-1~bpo8+1 amd64 Shared libraries for LXQt desktop environment (libs)
ii lxqt 0.9.0-5~bpo8+1 all Metapackage for LXQt
ii lxqt-about 0.9.0+20150902-2~bpo8+1 amd64 About screen for LXQt
ii lxqt-admin 0.9.0+20150830-2~bpo8+1 amd64 Admin tools for LXQt
ii lxqt-common 0.9.1+20151003-1~bpo8+1 all Common files for LXQt
ii lxqt-config 0.9.0+20150923-1~bpo8+1 amd64 LXQt system settings center
ii lxqt-core 0.9.0-5~bpo8+1 all Metapackage for the LXQt core
ii lxqt-globalkeys 0.9.0+20150926-1~bpo8+1 amd64 daemon used to register global keyboard shortcuts (appl.)
ii lxqt-notificationd 0.9.0+20150903-1~bpo8+1 amd64 LXQt notification daemon
ii lxqt-openssh-askpass 0.9.0+20150830-1~bpo8+1 amd64 OpenSSH user/password GUI dialog for LXQt
ii lxqt-panel 0.9.0+20150925-1~bpo8+1 amd64 LXQt desktop panel
ii lxqt-policykit 0.9.0+20150830-1~bpo8+1 amd64 LXQt authentication agent for PolicyKit
ii lxqt-powermanagement 0.9.0+20150930-1~bpo8+1 amd64 power management module for LXQt
ii lxqt-qtplugin 0.9.0+20150924-1~bpo8+1 amd64 LXQt system integration plugin for Qt
ii lxqt-runner 0.9.0+20150831-1~bpo8+1 amd64 LXQt program launcher
ii lxqt-session 0.9.0+20151023-1~bpo8+1 amd64 session manager component for LXQt
ii lxqt-sudo 0.9.0+20150908-1~bpo8+1 amd64 Graphical QT frontend for plain sudo

~$ dpkg -l |grep gimp
ii  gimp                                   2.8.14-1+b1                          amd64        The GNU Image Manipulation Program
ii  gimp-data                              2.8.14-1                             all          Data files for GIMP
ii  libgimp2.0                             2.8.14-1+b1                          amd64        Libraries for the GNU Image Manipulation Program

Kind regards,
Jan
Comment 1 Michael Schumacher 2015-10-24 18:43:52 UTC
Can you provide a stack trace for this? See https://wiki.gnome.org/GettingTraces
Comment 2 Jan Prunk 2015-10-24 18:58:29 UTC
Hi Michael, 

Here is the dbg report:
yang@X200:~$ gdb gimp
GNU gdb (Debian 7.7.1+dfsg-5) 7.7.1
Copyright (C) 2014 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from gimp...Reading symbols from /usr/lib/debug//usr/bin/gimp-2.8...done.
done.
(gdb) set pagination 0
(gdb) run [--args]
Starting program: /usr/bin/gimp [--args]
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffecee1700 (LWP 6203)]
[New Thread 0x7fffe3fff700 (LWP 6204)]
[New Thread 0x7fffe37fe700 (LWP 6205)]

(gimp:6199): Gimp-Widgets-CRITICAL **: gimp_device_info_set_device: assertion '(info->device == NULL && GDK_IS_DEVICE (device)) || (GDK_IS_DEVICE (info->device) && device == NULL)' failed
[New Thread 0x7fffe2e41700 (LWP 6206)]
[New Thread 0x7fffe1e83700 (LWP 6217)]
[New Thread 0x7fffe1682700 (LWP 6218)]
[Thread 0x7fffe1682700 (LWP 6218) exited]
While parsing XMP metadata:
Error on line 47 char 1: End of element <exif:Flash> not expected in this context
While parsing XMP metadata:
Error on line 64 char 1: End of element <exif:Flash> not expected in this context

Metadata parasite seems to be corrupt
While parsing XMP metadata:
Error on line 47 char 1: End of element <exif:Flash> not expected in this context

** (file-jpeg:6219): WARNING **: JPEG - unable to decode XMP metadata packet
[Thread 0x7fffe1e83700 (LWP 6217) exited]
The program 'gimp' received an X Window System error.
This probably reflects a bug in the program.
The error was 'BadWindow (invalid Window parameter)'.
  (Details: serial 128685 error_code 3 request_code 18 minor_code 0)
  (Note to programmers: normally, X errors are reported asynchronously;
   that is, you will receive the error a while after causing it.
   To debug your program, run it with the --sync command line
   option to change this behavior. You can then get a meaningful
   backtrace from your debugger if you break on the gdk_x_error() function.)
[Thread 0x7fffe2e41700 (LWP 6206) exited]
[Thread 0x7fffe3fff700 (LWP 6204) exited]
[Thread 0x7fffecee1700 (LWP 6203) exited]
[Thread 0x7ffff7fb6980 (LWP 6199) exited]

(script-fu:6207): LibGimpBase-WARNING **: script-fu: gimp_wire_read(): error
[Inferior 1 (process 6199) exited with code 01]
(gdb) bt
No stack.
(gdb) quit



One of the reasons for a possible crash could be that my /tmp directory is only 335 MB small (maybe it could be related, I don't know).

Regards, 
Jan
Comment 3 Michael Natterer 2015-10-24 21:36:03 UTC
Do you have some clipboard manager running? If yes, please try if
disabling it makes the crash go away.
Comment 4 Jan Prunk 2015-10-25 10:10:52 UTC
Hi Michael, 

I had a clipboard manager called "/usr/bin/qlipper" inside LXQT. When I disabled it (I didn't realise in the first place that it was running at all) the bug disappeared and I was able to crop and paste the image inside GIMP.

Thank you for suggesting the solution !

Kind regards, 
Jan
Comment 5 Michael Natterer 2016-11-06 20:44:30 UTC
*** Bug 772693 has been marked as a duplicate of this bug. ***
Comment 6 Michael Schumacher 2017-01-01 10:42:21 UTC
*** Bug 776502 has been marked as a duplicate of this bug. ***
Comment 7 Jehan 2017-01-01 19:17:53 UTC
Setting to "NEW" as we have a few other similar reports. Other people reported the same issue with more clipboard managers ("copyq" was cited in the 2 duplicates).
Comment 8 Kunda 2018-05-12 02:03:14 UTC
(In reply to Jan Prunk from comment #0)
> I noticed GIMP crashing in LXQT on Debian stable when copying cropped image
> into clipboard.

Jan can you still reproduce this using 2.10 ?
Comment 9 GNOME Infrastructure Team 2018-05-24 15:50:31 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/gimp/issues/789.