#988351 gimp crashes when copyq is running and i copy something from gimp to clipboard

Package:
gimp
Source:
gimp
Description:
GNU Image Manipulation Program
Submitter:
"Mr. T"
Date:
2022-06-30 07:45:06 UTC
Severity:
important
#988351#5
Date:
2021-05-11 08:20:36 UTC
From:
To:
together with:

Package: copyq
Version: 3.13.0-1
Severity: normal

hi,

its a fresh debian testing install, i installed mate-desktop gimp and
copyq (cause i know it from windows and like to have a history not only
of clipboard text but also html/richtext and graphics). But when i have
copyq running (default settings) and are working with gimp, copying
stuff there, gimp just crashes completely.
Please check this out.

Thanks a lot and keep up a good work

#988351#10
Date:
2021-05-28 09:55:53 UTC
From:
To:
Hello Mr. T,
I tried to reproduce the issue inside a small VM.

I hit an issue when copying something, mostly larger areas, in gimp.

If I started gimp from a terminal I got this message [1].
Maybe you could confirm when you start gimp from a terminal
you see the same message, when the error happens.

Following the advice from the message I get this backtrace [2].

Kind regards,
Bernhard


[1]
     The program 'gimp-2.10' received an X Window System error.
     This probably reflects a bug in the program.
     The error was 'BadWindow (invalid Window parameter)'.
       (Details: serial 193066 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.)

[2]
     (gdb) bt
     #0  gdk_x_error (display=0x555555fc8c60, error=0x7fffffffdee0) at ../../../../../gdk/x11/gdkmain-x11.c:458
     #1  0x00007ffff6b7f754 in _XError (dpy=dpy@entry=0x555555fc8c60, rep=rep@entry=0x5555583efec0) at ../../src/XlibInt.c:1503
     #2  0x00007ffff6b7c217 in handle_error (dpy=0x555555fc8c60, err=0x5555583efec0, in_XReply=<optimized out>) at ../../src/xcb_io.c:207
     #3  0x00007ffff6b7c2b5 in handle_response (dpy=dpy@entry=0x555555fc8c60, response=0x5555583efec0, in_XReply=in_XReply@entry=1) at ../../src/xcb_io.c:394
     #4  0x00007ffff6b7d51d in _XReply (dpy=dpy@entry=0x555555fc8c60, rep=rep@entry=0x7fffffffe0a0, extra=extra@entry=0, discard=discard@entry=1) at ../../src/xcb_io.c:718
     #5  0x00007ffff6b78d1b in XSync (dpy=0x555555fc8c60, discard=discard@entry=0) at ../../src/Sync.c:44
     #6  0x00007ffff6b78dbb in _XSyncFunction (dpy=<optimized out>) at ../../src/Synchro.c:35
     #7  0x00007ffff6b595a3 in XChangeProperty (dpy=0x555555fc8c60, w=w@entry=37748743, property=property@entry=308, type=type@entry=523, format=format@entry=8, mode=mode@entry=0, data=0x55555b301170 "\211PNG\r\n\032\n", nelements=262144) at ../../src/ChProp.c:92
     #8  0x00007ffff7a6f560 in IA__gdk_property_change (window=0x55555930b6c0, property=<optimized out>, type=0x75, format=8, mode=mode@entry=GDK_PROP_MODE_REPLACE, data=0x55555b301170 "\211PNG\r\n\032\n", nelements=262144) at ../../../../../gdk/x11/gdkproperty-x11.c:732
     #9  0x00007ffff7c63121 in _gtk_selection_incr_event (window=<optimized out>, event=0x5555595baac0) at ../../../../gtk/gtkselection.c:2593
     #10 0x00007ffff7a65afc in gdk_event_dispatch (source=<optimized out>, callback=<optimized out>, user_data=<optimized out>) at ../../../../../gdk/x11/gdkevents-x11.c:2425
     #11 0x00007ffff7006e6b in g_main_dispatch (context=0x555555ff5f10) at ../../../glib/gmain.c:3325
     #12 g_main_context_dispatch (context=0x555555ff5f10) at ../../../glib/gmain.c:4043
     #13 0x00007ffff7007118 in g_main_context_iterate (context=0x555555ff5f10, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4119
     #14 0x00007ffff700740b in g_main_loop_run (loop=loop@entry=0x5555585e0990) at ../../../glib/gmain.c:4317
     #15 0x000055555563356e in app_run (full_prog_name=<optimized out>, filenames=<optimized out>, alternate_system_gimprc=alternate_system_gimprc@entry=0x0, alternate_gimprc=alternate_gimprc@entry=0x0, session_name=<optimized out>, batch_interpreter=0x0, batch_commands=0x0, as_new=0, no_interface=0, no_data=0, no_fonts=0, no_splash=0, be_verbose=0, use_shm=1, use_cpu_accel=1, console_messages=0, use_debug_handler=0, show_playground=0, show_debug_menu=0, stack_trace_mode=GIMP_STACK_TRACE_NEVER, pdb_compat_mode=GIMP_PDB_COMPAT_ON, backtrace_file=0x555555ee7820 "/home/benutzer/.config/GIMP/2.10/CrashLog/GIMP-crash-1622193301.txt") at app.c:439
     #16 0x0000555555632e3e in main (argc=<optimized out>, argv=<optimized out>) at main.c:636

#988351#15
Date:
2021-06-01 12:31:43 UTC
From:
To:
Dear Maintainer,
there is an upstream bug that shows a similar backtrace
and is also about clipboard interaction.
Maybe more likely to happen with larger selections.

https://gitlab.gnome.org/GNOME/gimp/-/issues/2357

Kind regards,
Bernhard

#988351#20
Date:
2021-06-01 12:37:14 UTC
From:
To:
Am 01.06.21 um 14:31 schrieb Bernhard Übelacker:

And copyq upstream has also a similar bug report here:

https://github.com/hluk/CopyQ/issues/1070

Kind regards,
Bernhard