Bug 26606 - Gimp 2.10.10 is unstable and crashing using clipboard
Summary: Gimp 2.10.10 is unstable and crashing using clipboard
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 8
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: QA Team
QA Contact:
URL: https://www.gimp.org/news/2019/06/12/...
Whiteboard:
Keywords:
Depends on: 29538
Blocks:
  Show dependency treegraph
 
Reported: 2020-05-10 22:26 CEST by Edward d'Auvergne
Modified: 2021-10-12 15:21 CEST (History)
9 users (show)

See Also:
Source RPM: plasma-workspace-5.20.4-5.mga8.src.rpm
CVE:
Status comment:


Attachments

Description Edward d'Auvergne 2020-05-10 22:26:38 CEST
Description of problem:

Gimp in Mageia 7 is unusable, with segfaults with messages such as:

"""
$ gimp
Gtk-Message: 22:04:52.724: Failed to load module "canberra-gtk-module"
Gtk-Message: 22:05:04.606: Failed to load module "canberra-gtk-module"
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 311775 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:17203): LibGimpBase-WARNING **: 22:08:22.158: script-fu: gimp_wire_read(): error
"""

This is a well known issue with the 2.10.10 version being insanely buggy.  See the release notes for 2.10.12 (https://www.gimp.org/news/2019/06/12/gimp-2-10-12-released/), where they say:

"""
Among most pesky bugs fixed:

    crashes for various reasons, with more crashes to fix yet;
"""

The fix is simple, move to a non-fubar version of GEGL gimp.


Version-Release number of selected component (if applicable):

2.10.10


How reproducible:

100% with the steps below, at least for me.


Steps to Reproduce:
1. Open an image, e.g. https://upload.wikimedia.org/wikipedia/commons/thumb/1/1d/GIMP_2.10.jpg/800px-GIMP_2.10.jpg
2. Click on the "select by colour tool" (Shift+O).
3. Click somewhere on the image.
4. Type 'Ctrl+X' to cut the selection.
Thierry Vignaud 2020-05-11 15:09:23 CEST

Source RPM: (none) => gimp, gegl
CC: (none) => eatdirt, shlomif, thierry.vignaud

Thierry Vignaud 2020-05-11 15:09:42 CEST

URL: (none) => https://www.gimp.org/news/2019/06/12/gimp-2-10-12-released/

Comment 1 Lewis Smith 2020-05-11 20:22:38 CEST
> Steps to Reproduce:
> 1. Open an image, e.g. https://upload.wikimedia.org/wikipedia/commons/thumb
> /1/1d/GIMP_2.10.jpg/800px-GIMP_2.10.jpg
> 2. Click on the "select by colour tool" (Shift+O).
> 3. Click somewhere on the image.
> 4. Type 'Ctrl+X' to cut the selection.
As is often the case, this worked for me: gimp-2.10.10-1.6.mga7
I am not belittling the complaint.

Cauldron seems to have rapidly moved 2.10.10-12-14-16-18! Can we not advance at least a bit for Mageia 7?
Having to assign this to all packagers as different people do Gimp; Thierry has already CC'd several. Not much bugsquad can do to help.

Assignee: bugsquad => pkg-bugs
CC: (none) => smelror

Comment 2 Nicolas Lécureuil 2020-05-17 15:24:53 CEST
if there is so many crashes i think this can be a good option to update it.

Can you test 2.10.12 when it will be available in the repos ?

Status: NEW => ASSIGNED
CC: (none) => mageia

Comment 3 Chris Denice 2020-05-22 18:31:12 CEST
Sorry, I am not confirming this. I've been using it for a few things and it works fine.

First thing to try, erase old config directories (or rename it if you have things inside to save)
$HOME/.config/GIMP

If this works, we don't update. At best, someone backports.

Resolution: (none) => WORKSFORME
Status: ASSIGNED => RESOLVED

Comment 4 Edward d'Auvergne 2020-06-07 12:04:54 CEST
Sorry for the long delay, due to Covid-19 I haven't had a chance to sit at my computer and test this.  I have moved $HOME/.config/GIMP out of .config/ and I still see these crashes:

"""
$ gimp /home/edward/Download/800px-GIMP_2.10.jpg
Gtk-Message: 11:58:46.657: Failed to load module "canberra-gtk-module"
Gtk-Message: 11:58:50.547: Failed to load module "canberra-gtk-module"
using gegl copy
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 21876 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:13545): LibGimpBase-WARNING **: 11:58:56.462: script-fu: gimp_wire_read(): error
"""


I don't know if this is any use, but here it the gdb backtrace on gdk_x_error() and subsequent crash:

"""
$ gdb gimp
GNU gdb (GDB) 8.2-8.mga7 (Mageia release 7)
Copyright (C) 2018 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-mageia-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 .gnu_debugdata for /usr/bin/gimp-2.10...(no debugging symbols found)...done.
(no debugging symbols found)...done.
Missing separate debuginfos, use: debuginfo-install gimp-2.10.10-1.1.mga7.x86_64
(gdb) break gdk_x_error
Function "gdk_x_error" not defined.
Make breakpoint pending on future shared library load? (y or [n]) y
Breakpoint 1 (gdk_x_error) pending.
(gdb) run --sync /home/edward/Download/800px-GIMP_2.10.jpg
Starting program: /usr/bin/gimp --sync /home/edward/Download/800px-GIMP_2.10.jpg
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/usr/lib64/libthread_db.so.1".
[New Thread 0x7ffff3bad700 (LWP 14220)]
[New Thread 0x7ffff33ac700 (LWP 14221)]
[New Thread 0x7ffff2bab700 (LWP 14222)]
[New Thread 0x7ffff23aa700 (LWP 14223)]
[New Thread 0x7ffff1ba9700 (LWP 14224)]
[New Thread 0x7ffff13a8700 (LWP 14225)]
[New Thread 0x7ffff0ba7700 (LWP 14226)]
Gtk-Message: 12:02:40.277: Failed to load module "canberra-gtk-module"
[New Thread 0x7fffd3230700 (LWP 14236)]
[New Thread 0x7fffd2a2f700 (LWP 14237)]
[New Thread 0x7fffc9a0b700 (LWP 14241)]
[New Thread 0x7fffc920a700 (LWP 14242)]
[New Thread 0x7fffbf61a700 (LWP 14246)]
[Thread 0x7fffbf61a700 (LWP 14246) exited]
[Detaching after vfork from child process 14256]
[Detaching after vfork from child process 14257]
[Detaching after vfork from child process 14259]
[Detaching after vfork from child process 14261]
[Detaching after vfork from child process 14264]
[New Thread 0x7fffbf61a700 (LWP 14270)]
Gtk-Message: 12:02:48.305: Failed to load module "canberra-gtk-module"
[Thread 0x7fffc920a700 (LWP 14242) exited]
[New Thread 0x7fffc920a700 (LWP 14280)]
using gegl copy

Thread 1 "gimp" hit Breakpoint 1, 0x00007ffff7aaa8d0 in gdk_x_error () from /usr/lib64/libgdk-x11-2.0.so.0
(gdb) bt
#0  0x00007ffff7aaa8d0 in gdk_x_error () at /usr/lib64/libgdk-x11-2.0.so.0
#1  0x00007ffff6c41c6a in _XError (dpy=dpy@entry=0xd81130, rep=rep@entry=0x3f1f710) at XlibInt.c:1444
#2  0x00007ffff6c3ec47 in handle_error (dpy=0xd81130, err=0x3f1f710, in_XReply=<optimized out>) at xcb_io.c:199
#3  0x00007ffff6c3ecdd in handle_response (dpy=0xd81130, response=0x3f1f710, in_XReply=<optimized out>) at xcb_io.c:324
#4  0x00007ffff6c3fb90 in _XReply (dpy=dpy@entry=0xd81130, rep=rep@entry=0x7fffffffc8b0, extra=extra@entry=0, discard=discard@entry=1) at xcb_io.c:634
#5  0x00007ffff6c3b6cd in XSync (dpy=0xd81130, discard=discard@entry=0) at Sync.c:44
#6  0x00007ffff6c3b75b in _XSyncFunction (dpy=<optimized out>) at Synchro.c:35
#7  0x00007ffff6c1d5cb in XChangeProperty (dpy=0xd81130, w=123731981, property=<optimized out>, type=<optimized out>, format=<optimized out>, mode=<optimized out>, data=0x4edac10 "BM\232\212\021", nelements=262144) at ChProp.c:92
#8  0x00007ffff7aacd52 in gdk_property_change () at /usr/lib64/libgdk-x11-2.0.so.0
#9  0x00007ffff7c8f638 in _gtk_selection_incr_event () at /usr/lib64/libgtk-x11-2.0.so.0
#10 0x00007ffff7c2ae6c in gtk_main_do_event () at /usr/lib64/libgtk-x11-2.0.so.0
#11 0x00007ffff7aa372c in gdk_event_dispatch () at /usr/lib64/libgdk-x11-2.0.so.0
#12 0x00007ffff70bb665 in g_main_context_dispatch () at /usr/lib64/libglib-2.0.so.0
#13 0x00007ffff70bb9e8 in g_main_context_iterate.isra () at /usr/lib64/libglib-2.0.so.0
#14 0x00007ffff70bbcd2 in g_main_loop_run () at /usr/lib64/libglib-2.0.so.0
#15 0x0000000000499012 in app_run ()
#16 0x0000000000498976 in main ()
(gdb) c
Continuing.
[Thread 0x7fffbf61a700 (LWP 14270) 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 45817 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 0x7fffc920a700 (LWP 14280) exited]
[Thread 0x7fffc9a0b700 (LWP 14241) exited]
[Thread 0x7fffd2a2f700 (LWP 14237) exited]
[Thread 0x7fffd3230700 (LWP 14236) exited]
[Thread 0x7ffff0ba7700 (LWP 14226) exited]
[Thread 0x7ffff13a8700 (LWP 14225) exited]
[Thread 0x7ffff1ba9700 (LWP 14224) exited]
[Thread 0x7ffff23aa700 (LWP 14223) exited]
[Thread 0x7ffff33ac700 (LWP 14221) exited]
[Thread 0x7ffff3bad700 (LWP 14220) exited]
[Thread 0x7ffff606a680 (LWP 14212) exited]

(script-fu:14261): LibGimpBase-WARNING **: 12:04:07.066: script-fu: gimp_wire_read(): error
[Inferior 1 (process 14212) exited with code 01]
(gdb)
"""
Comment 5 Edward d'Auvergne 2020-06-07 15:49:27 CEST
If a newer version is packaged and put into one of the testing repositories, I can check if that fixes the problem for me.  Cheers.
Comment 6 Chris Denice 2020-06-08 21:16:18 CEST
Ok, thanks for the test!

The problem is that no one is able to reproduce this bug, even with the file you provided. So something should be different between your installation and the one others have and we should first try to understand what is this.

Which arch? x86_64?

You don't have backport enable? All updates made on mga7?

What version number is returned by:
rpm -qi lib64gtk+-x11-2.0_0
(2.24.32 5.mga7)?

rpm -qi gimp
(2.10.1 1.6.mga7)?
Comment 7 Chris Denice 2020-06-08 21:18:56 CEST
And which graphic drivers?

What reports ldd /usr/bin/gimp

?
Comment 8 Edward d'Auvergne 2021-05-17 10:44:58 CEST
Sorry for the long delay - COVID-19 issues blocked me from completely looking at this.  Gimp is still on version 2.10.10 and I just had the crash again.  This is a complete blocker for me.  The details of my system are:

Arch:  x86_64

OS:  mga7

Updates:  All

$ rpm -qi lib64gtk+-x11-2.0_0:  [snip] Version: 2.24.32; Release: mga7; Architecture: x86_64 [snip]

$ rpm -qi gimp:  [snip] Epoch: 1; Version: 2.10.10; Release: 1.6.mga7; Architecture: x86_64 [snip]

$ ldd /usr/bin/gimp
        linux-vdso.so.1 (0x00007ffff9d99000)
        libgimpwidgets-2.0.so.0 => /usr/lib64/libgimpwidgets-2.0.so.0 (0x00007f9611f0a000)
        libgtk-x11-2.0.so.0 => /usr/lib64/libgtk-x11-2.0.so.0 (0x00007f9611ad0000)
        libgdk-x11-2.0.so.0 => /usr/lib64/libgdk-x11-2.0.so.0 (0x00007f9611a1a000)
        libgimpconfig-2.0.so.0 => /usr/lib64/libgimpconfig-2.0.so.0 (0x00007f9611a03000)
        libgimpmath-2.0.so.0 => /usr/lib64/libgimpmath-2.0.so.0 (0x00007f96119fc000)
        libgimpthumb-2.0.so.0 => /usr/lib64/libgimpthumb-2.0.so.0 (0x00007f96119ee000)
        libgimpcolor-2.0.so.0 => /usr/lib64/libgimpcolor-2.0.so.0 (0x00007f96119d6000)
        libgimpmodule-2.0.so.0 => /usr/lib64/libgimpmodule-2.0.so.0 (0x00007f96119cf000)
        libgimpbase-2.0.so.0 => /usr/lib64/libgimpbase-2.0.so.0 (0x00007f961199f000)
        libgdk_pixbuf-2.0.so.0 => /usr/lib64/libgdk_pixbuf-2.0.so.0 (0x00007f9611979000)
        libpangocairo-1.0.so.0 => /usr/lib64/libpangocairo-1.0.so.0 (0x00007f9611969000)
        libpangoft2-1.0.so.0 => /usr/lib64/libpangoft2-1.0.so.0 (0x00007f961194f000)
        libpango-1.0.so.0 => /usr/lib64/libpango-1.0.so.0 (0x00007f9611906000)
        libfontconfig.so.1 => /usr/lib64/libfontconfig.so.1 (0x00007f96118c1000)
        libfreetype.so.6 => /usr/lib64/libfreetype.so.6 (0x00007f9611818000)
        libharfbuzz.so.0 => /usr/lib64/libharfbuzz.so.0 (0x00007f9611715000)
        libcairo.so.2 => /usr/lib64/libcairo.so.2 (0x00007f96115e4000)
        libgegl-0.4.so.0 => /usr/lib64/libgegl-0.4.so.0 (0x00007f961151f000)
        libgegl-npd-0.4.so.0 => /usr/lib64/libgegl-npd-0.4.so.0 (0x00007f9611516000)
        libbabl-0.1.so.0 => /usr/lib64/libbabl-0.1.so.0 (0x00007f9611433000)
        liblcms2.so.2 => /usr/lib64/liblcms2.so.2 (0x00007f96113d8000)
        libgexiv2.so.2 => /usr/lib64/libgexiv2.so.2 (0x00007f96113b3000)
        libgio-2.0.so.0 => /usr/lib64/libgio-2.0.so.0 (0x00007f96111ee000)
        libz.so.1 => /usr/lib64/libz.so.1 (0x00007f96111cf000)
        libmypaint-1.3.so.0 => /usr/lib64/libmypaint-1.3.so.0 (0x00007f96111bb000)
        libgobject-2.0.so.0 => /usr/lib64/libgobject-2.0.so.0 (0x00007f9611160000)
        libglib-2.0.so.0 => /usr/lib64/libglib-2.0.so.0 (0x00007f9611041000)
        libm.so.6 => /usr/lib64/libm.so.6 (0x00007f9610eff000)
        libdl.so.2 => /usr/lib64/libdl.so.2 (0x00007f9610efa000)
        libpthread.so.0 => /usr/lib64/libpthread.so.0 (0x00007f9610ed7000)
        libc.so.6 => /usr/lib64/libc.so.6 (0x00007f9610d0d000)
        libX11.so.6 => /usr/lib64/libX11.so.6 (0x00007f9610bcf000)
        libXfixes.so.3 => /usr/lib64/libXfixes.so.3 (0x00007f9610bc7000)
        libatk-1.0.so.0 => /usr/lib64/libatk-1.0.so.0 (0x00007f9610b9e000)
        libgmodule-2.0.so.0 => /usr/lib64/libgmodule-2.0.so.0 (0x00007f9610b98000)
        libXrender.so.1 => /usr/lib64/libXrender.so.1 (0x00007f9610b89000)
        libXinerama.so.1 => /usr/lib64/libXinerama.so.1 (0x00007f9610b84000)
        libXi.so.6 => /usr/lib64/libXi.so.6 (0x00007f9610b71000)
        libXrandr.so.2 => /usr/lib64/libXrandr.so.2 (0x00007f9610b64000)
        libXcursor.so.1 => /usr/lib64/libXcursor.so.1 (0x00007f9610b58000)
        libXcomposite.so.1 => /usr/lib64/libXcomposite.so.1 (0x00007f9610b53000)
        libXdamage.so.1 => /usr/lib64/libXdamage.so.1 (0x00007f9610b4c000)
        libXext.so.6 => /usr/lib64/libXext.so.6 (0x00007f9610b38000)
        libfribidi.so.0 => /usr/lib64/libfribidi.so.0 (0x00007f9610b1a000)
        libthai.so.0 => /usr/lib64/libthai.so.0 (0x00007f9610b0f000)
        libxml2.so.2 => /usr/lib64/libxml2.so.2 (0x00007f96109a9000)
        libuuid.so.1 => /usr/lib64/libuuid.so.1 (0x00007f961099e000)
        libbz2.so.1 => /usr/lib64/libbz2.so.1 (0x00007f961098b000)
        libpng16.so.16 => /usr/lib64/libpng16.so.16 (0x00007f9610932000)
        libgraphite2.so.3 => /usr/lib64/libgraphite2.so.3 (0x00007f961090d000)
        libpixman-1.so.0 => /usr/lib64/libpixman-1.so.0 (0x00007f9610867000)
        libEGL.so.1 => /usr/lib64/libEGL.so.1 (0x00007f9610827000)
        libxcb-shm.so.0 => /usr/lib64/libxcb-shm.so.0 (0x00007f9610820000)
        libxcb.so.1 => /usr/lib64/libxcb.so.1 (0x00007f96107f8000)
        libxcb-render.so.0 => /usr/lib64/libxcb-render.so.0 (0x00007f96107e8000)
        libGL.so.1 => /usr/lib64/libGL.so.1 (0x00007f9610778000)
        librt.so.1 => /usr/lib64/librt.so.1 (0x00007f961076d000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f9611fa3000)
        libexiv2.so.27 => /usr/lib64/libexiv2.so.27 (0x00007f96104ab000)
        libstdc++.so.6 => /usr/lib64/libstdc++.so.6 (0x00007f9610325000)
        libgcc_s.so.1 => /usr/lib64/libgcc_s.so.1 (0x00007f961030b000)
        libmount.so.1 => /usr/lib64/libmount.so.1 (0x00007f96102b2000)
        libresolv.so.2 => /usr/lib64/libresolv.so.2 (0x00007f9610297000)
        libjson-c.so.4 => /usr/lib64/libjson-c.so.4 (0x00007f9610285000)
        libffi.so.6 => /usr/lib64/libffi.so.6 (0x00007f9610279000)
        libpcre.so.1 => /usr/lib64/libpcre.so.1 (0x00007f9610207000)
        libdatrie.so.1 => /usr/lib64/libdatrie.so.1 (0x00007f96101fd000)
        liblzma.so.5 => /usr/lib64/liblzma.so.5 (0x00007f96101c9000)
        libgbm.so.1 => /usr/lib64/libgbm.so.1 (0x00007f96101b7000)
        libglapi.so.0 => /usr/lib64/libglapi.so.0 (0x00007f961017c000)
        libexpat.so.1 => /usr/lib64/libexpat.so.1 (0x00007f9610140000)
        libX11-xcb.so.1 => /usr/lib64/libX11-xcb.so.1 (0x00007f961013b000)
        libxcb-dri2.so.0 => /usr/lib64/libxcb-dri2.so.0 (0x00007f9610135000)
        libxcb-xfixes.so.0 => /usr/lib64/libxcb-xfixes.so.0 (0x00007f961012c000)
        libdrm.so.2 => /usr/lib64/libdrm.so.2 (0x00007f9610118000)
        libwayland-client.so.0 => /usr/lib64/libwayland-client.so.0 (0x00007f9610105000)
        libwayland-server.so.0 => /usr/lib64/libwayland-server.so.0 (0x00007f96100f0000)
        libxcb-dri3.so.0 => /usr/lib64/libxcb-dri3.so.0 (0x00007f96100ea000)
        libxcb-present.so.0 => /usr/lib64/libxcb-present.so.0 (0x00007f96100e5000)
        libxcb-sync.so.1 => /usr/lib64/libxcb-sync.so.1 (0x00007f96100dc000)
        libxshmfence.so.1 => /usr/lib64/libxshmfence.so.1 (0x00007f96100d7000)
        libXau.so.6 => /usr/lib64/libXau.so.6 (0x00007f96100d0000)
        libXdmcp.so.6 => /usr/lib64/libXdmcp.so.6 (0x00007f96100c8000)
        libxcb-glx.so.0 => /usr/lib64/libxcb-glx.so.0 (0x00007f96100ad000)
        libXxf86vm.so.1 => /usr/lib64/libXxf86vm.so.1 (0x00007f96100a6000)
        libblkid.so.1 => /usr/lib64/libblkid.so.1 (0x00007f9610057000)
        libbsd.so.0 => /usr/lib64/libbsd.so.0 (0x00007f961003c000)
Comment 9 Edward d'Auvergne 2021-05-17 10:48:33 CEST
And the graphics drivers:

$ lspci | grep VGA
02:00.0 VGA compatible controller: Advanced Micro Devices, Inc. [AMD/ATI] Caicos [Radeon HD 6450/7450/8450 / R5 230 OEM]

$ grep LoadModule /var/log/Xorg.0.log
[    33.810] (II) LoadModule: "v4l"
[    33.810] (II) LoadModule: "glx"
[    33.812] (II) LoadModule: "ati"
[    33.812] (II) LoadModule: "radeon"
[    33.814] (II) LoadModule: "fb"
[    33.815] (II) LoadModule: "dri2"
[    33.987] (II) LoadModule: "glamoregl"
[    34.090] (II) LoadModule: "ramdac"
[    34.233] (II) LoadModule: "libinput"
Comment 10 Chris Denice 2021-05-17 10:51:02 CEST
All right, I'll have a look if an update still makes sense on mga7, it is going to be soon EOL.

In the meanwhile, you should consider upgrading to mga8, which has gimp-2.10.24, hopefully that will fix your issues!
Comment 11 Edward d'Auvergne 2021-05-17 10:56:22 CEST
With some more searching, I found this related report:

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

I now think the issue identified at the end might be the real cause - the problem is with the plasma clipboard:

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

Only the cut or copy operations in the GIMP cause a crash - the delete operation does not.

As a test, I started a vnc server and logged in to LXDE.  The copy and cut operations do not crash the Gimp with this window manager.
Comment 12 Edward d'Auvergne 2021-05-17 11:06:52 CEST
Due to a deadline and school holidays, I will need to delay upgrading to mga8 for about 3-4 weeks.  Cheers!
Comment 13 Chris Denice 2021-05-17 11:12:02 CEST
Thanks for looking at it! Please open a bug report for plasma is you see the issue again under mga8.

PS: I am reopening and reassigning this bug to plasma-workspace, someone could edit the SRPMS more accurately, I don't use that gas factory :)

Source RPM: gimp, gegl => plasma-workspace-5.20.4-5.mga8.src.rpm
Summary: Gimp 2.10.10 is unstable and constantly crashing. => Gimp 2.10.10 is unstable and constantly crashing only under plasma
Resolution: WORKSFORME => (none)
Status: RESOLVED => REOPENED

Comment 14 Aurelien Oudelet 2021-07-06 13:16:26 CEST
Mageia 7 is EOL since July 1st 2021.
There will not have any further bugfix for this release.

You are encouraged to upgrade to Mageia 8 as soon as possible.

@reporter, if this bug still apply with Mageia 8, please let us know it.

@packager, if you work on the Mageia 7 version of your package, please check the Mageia 8 package if issue is also present. In this case, please fix the Mageia 8 version instead.

This bug report will be closed OLD if there is no further notice within 1st September 2021.
Comment 15 papoteur 2021-09-02 12:09:39 CEST
Hello,
I encountered this bug with Mageia 8.
I try to copy-paste image from Gimp to Libreoffice. When I paste in Libreoffice, Gimp crashes if the current document in Gimp has not been saved.
gimp
Warning: Unknown input_id: -1 for input: surfacemap_x
Warning: Unknown input_id: -1 for input: surfacemap_x
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 947780 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:869189): LibGimpBase-WARNING **: 11:56:54.109: script-fu: gimp_wire_read(): error

CC: (none) => yves.brungard_mageia
Version: 7 => 8

papoteur 2021-09-02 12:10:32 CEST

Summary: Gimp 2.10.10 is unstable and constantly crashing only under plasma => Gimp 2.10.10 is unstable and crashing using clipboard

Comment 16 papoteur 2021-09-02 12:12:07 CEST
I should add that I use LXQt.
rpm -q gimp
gimp-2.10.24-1.mga8
Comment 17 papoteur 2021-09-02 12:23:43 CEST
Gimp bug report says:
Edit on 2021-08-13 by @schumaml

The Qt bug (QTBUG-56595) causing this has been fixed - see #789 (comment 1246287). Once updated Qt versions (or backports) spread across distros, the crashes with GTK 2.x applications will disappear, and with GTK 3.x applications copy&paste should start to work in previously affected environments.

And the Qt bug report is: https://bugreports.qt.io/browse/QTBUG-56595
Can the resolution be ported on our Qt?
Comment 18 Nicolas Lécureuil 2021-10-07 10:36:43 CEST
new qtbase pushed, please test ( pushed mga8/9 )
Comment 19 Jose Manuel López 2021-10-07 11:10:40 CEST
This bug is still happening, with Mageia 8 plasma x64 updated.

When an image is copied and pasted to writer, Gimp crashes and close.

Greetings!

CC: (none) => joselpddj

Comment 20 Nicolas Lécureuil 2021-10-07 14:27:10 CEST
please test with new package in updates testing.

papoteur tested and this fixes the issue for him

Assignee: pkg-bugs => qa-bugs

Comment 21 Morgan Leijström 2021-10-07 16:01:26 CEST
Please state more clearly packages user should test.

I guess the packages are (for 64 bit):

- lib64qt5-database-plugin-ibase-5.15.2-4.3.mga8.x86_64
- lib64qt5-database-plugin-mysql-5.15.2-4.3.mga8.x86_64
- lib64qt5-database-plugin-sqlite-5.15.2-4.3.mga8.x86_64
- qtbase5-common-5.15.2-4.3.mga8.x86_64

?

CC: (none) => fri

Comment 22 Nicolas Lécureuil 2021-10-07 16:07:02 CEST
Hi,

the packages from this packages are ( i removed debuginfo, debugsource, devel packages):

qtbase5-examples-5.15.2-4.3.mga8
lib64qt5gui5-5.15.2-4.3.mga8
lib64qt5widgets5-5.15.2-4.3.mga8
lib64qt5core5-5.15.2-4.3.mga8
lib64qt5network5-5.15.2-4.3.mga8
lib64qt5xcbqpa5-5.15.2-4.3.mga8
qtbase5-common-5.15.2-4.3.mga8
lib64qt5eglfsdeviceintegration5-5.15.2-4.3.mga8
lib64qt5dbus5-5.15.2-4.3.mga8
lib64qt5opengl5-5.15.2-4.3.mga8
lib64qt5test5-5.15.2-4.3.mga8
lib64qt5printsupport5-5.15.2-4.3.mga8
lib64qt5xml5-5.15.2-4.3.mga8
lib64qt5eglfskmssupport5-5.15.2-4.3.mga8
lib64qt5sql5-5.15.2-4.3.mga8
lib64qt5-database-plugin-pgsql-5.15.2-4.3.mga8
lib64qt5-database-plugin-odbc-5.15.2-4.3.mga8
lib64qt5-database-plugin-ibase-5.15.2-4.3.mga8
lib64qt5-database-plugin-mysql-5.15.2-4.3.mga8
lib64qt5-database-plugin-sqlite-5.15.2-4.3.mga8
lib64qt5concurrent5-5.15.2-4.3.mga8
lib64qt5-database-plugin-tds-5.15.2-4.3.mga8
Comment 23 Jose Manuel López 2021-10-07 17:32:41 CEST
Ok, I have tried the new packages from testing repositories. Now, I can copy a image from Gimp to Writer correctly. Gimp Gimp won't crash or close.

I think that this is fixed, and we can close this bug.

Thanks and greetings!
Comment 24 Morgan Leijström 2021-10-08 08:11:25 CEST
@ Nicolas, please open a bug on the qt5 update, and set to QA.
So it can be QA tested and validated.
Comment 25 Nicolas Lécureuil 2021-10-08 09:13:31 CEST
i need to open a new bugreport or do i add the advisory here ?
Comment 26 Morgan Leijström 2021-10-08 10:40:19 CEST
This bug was opened for Gimp.

It is more elegant to open a fresh new for qtbase, to do the QA for qtbase in.

And set this Gimp bug to depend on qtbase, and close it when qtbase is closed,
OR close this as invalid with a note the bug is in qtbase.
Comment 27 Nicolas Lécureuil 2021-10-08 11:59:04 CEST
ok no pb for me :-)
Nicolas Lécureuil 2021-10-08 14:15:55 CEST

Depends on: (none) => 29538

Comment 28 Dave Hodgins 2021-10-12 15:21:41 CEST
Closing as the fix in bug 29538 has been pushed to updates.

Status: REOPENED => RESOLVED
Resolution: (none) => FIXED
CC: (none) => davidwhodgins


Note You need to log in before you can comment on or make changes to this bug.