Note: bug reporters are expected to have verified the bug still exists
either in the last stable version of GIMP or on updated development code
(master branch).
Operating System:
Package: [flatpak? Installer from gimp.org? If another installer, tell us where from]
Description of the bug
Please describe your issue with details.
Add screenshot or other files if needed.
Reproduction
Is the bug reproducible? [Always / Randomly / Happened only once ]
Reproduction steps:
Open an image in GIMP
Select an area on the image
Edit/Copy
…
Expected result: Copy to clipboard
Actual result: Program crashes
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related.
Learn more.
@rowingdude: as @aklapper said, we'd need a backtrace to have more information. Also you didn't even filled in all the basic info (GIMP version, OS, how did you install GIMP, etc.).
Anyway considering the BadWindow X error and the context, it looks like it could just be a duplicate of #789 (closed).
Do you have a clipboard manager installed by any chance?
P.S.: the dbus errors are weird too, though I don't know if they are related to the crash.
Similar or same problem under Arch Linux (Archlabs) using GIMP 2.10.10 and X 1.20.4 (both from Arch Repos), steps to reproduce:
Open medium large image (PNG with 8.3 MB and roughly 3k by 3k pixels)
Select about half of it, hit Ctrl+C
Open another program that supports pasting of images (such as Firefox, Telegram)
Hit Ctrl+V, causing GIMP to crash.
Console output:
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 165435 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:25666): LibGimpBase-WARNING **: 20:25:28.450: script-fu: gimp_wire_read(): error
I'll post a backtrace if it doesn't take too long and isn't too complicated.
Lubuntu 19.04 x86_64 Intel video card laptop Asus X540SSA 4gig Ram. Same issue here, copy paste crashes the program. Some hint? The bug is not closed, so what I can do?
My bad, sorry. I was using my cellular phone, so the screen it is barely
readable.
This evening I will read the thread carefully and try to have some
useful to debug.
Closing this task as no further information / stacktrace has been provided. Please feel free to reopen this task if you can provide the information that was asked for in a previous comment and if this problem still happens.
I've seen a number of similar-looking bugs on the tracker but this appears to be the most recent, so I'm replying with the suggestion that it be reopened.
Same approximate configuration as @MaxMatti here and same error message. GIMP 2.10.14. The crash happens about 80% of the time when pasting a medium-sized image to another program, both with and without xfce4-clipman running.
There's no segfault, just an emergency exit, so my backtrace is from a breakpoint on exit(). The crashdump file mentioned in the trace is not actually produced. Does this seem to point to a problem in gdk? I'm a bit too tired to grok it.
backtrace.txt