-
Notifications
You must be signed in to change notification settings - Fork 432
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Copying large images from Gimp crashes it. #636
Comments
Yes, same issue, I had to uninstall CopyQ from 16.04 Ubuntu Gnome. |
Looks like Gimp bug. Strangely this doesn't happen when getting copied image data with |
I wanted to debug this so I recompiled Gimp with debug symbols and I cannot reproduce this -- this is classic :(. BTW, I'm using Arch Linux and Gimp 2.8.18. The version in from official package is affected with this bug. Edit: I can actually reproduce this sometimes with debug version. |
Fixed. It seems it's partially an issue in Gimp and in Qt. |
@Hulk it seem the bug is still exist 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 263921 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:6014): LibGimpBase-WARNING **: 18:55:37.232: script-fu: gimp_wire_read(): error
|
Ignore clipboard data if accessing it takes long time. Retrieves images last. Fixes #636 Signed-off-by: Lukas Holecek <hluk@email.cz>
@rachmadaniHaryono I tried my best to fix this but the fixes I've implemented makes the bug only happen less frequently. It's bug in Gimp (or in some libs it uses) because it definitely should not cause a crash. And it's possibly a bug in Qt because of how it retrieves X11 clipboard/selection. |
which mean even if i use similar script like on #561 it will still crash?
|
@rachmadaniHaryono It could crash even in that case since the clipboard content is retrieved before the command starts. You would need to disable storing images (in "Items" configuration tab uncheck "Images" in the list). |
I'm getting a very similar crash with Shutter (a screenshot tool written in Perl).
Also Inkscape suffers from the same issue: https://bugs.launchpad.net/inkscape/+bug/1589121 |
Probably partially problem in how Qt retrieves data but I don't see how it can crash foreign app just by requesting clipboard unless there is a bug in that app itself (or in an library it uses, XCB, X11). |
Shutter GUI is built on GTK. Not sure about Inkscape. |
Using gtk3 fixes this issue for gimp 2.99. Former versions of gimp uses gtk2. |
I have the same issue with Gimp 2.10.18 on Ubuntu 20.04.1 LTS with copyq v3.10.0 I get the same message as @dniku but noting shows up in Xorg.0.log, even when running with --sync |
Hi, |
Thanks. Upgrading GIMP to beta works.
Too bad they won't fix it for all the other non-beta users.. I imagine there are a lot of people thinking that GIMP is unstable without knowing the bug comes from an incompatibility with CopyQ... |
Instructions for installing the beta: https://www.gimp.org/downloads/devel/ |
on kubuntu 20.04 both gimp 2.10 and 2.99 still seem to fail to paste large images copied into clipboard into chrome |
System: Ubuntu 16.04.2 LTS
CopyQ version: CopyQ Clipboard Manager v2.8.2 Built with: Qt 5.5.1, LibQxt 0.7.0 (downloaded from your repo)
Gimp version: 2.8.16 (the version available in the repositories)
Ever since I've installed this new version, when I copy something large to the clipboard, Gimp just exits, and the copied image doesn't appear in CopyQ.
Running it from the terminal gets me the following errors when copying:
Interestingly, if I copy just a small part of the image, then this doesn't happen. It also didn't happen when I've tried to copy an empty image, although it does happen with very large ones (I tried 4096x4096 RGB color).
Edit: Forgot to mention it that this doesn't happen in Krita, even with large images (although it takes some time to appear in CopyQ)
The text was updated successfully, but these errors were encountered: