![]() If you are running a KDE desktop, it seems youĬould use krita instead of XnViewMP, or klipper instead of CopyQ. Same results should be experienced with the clipboard managers referenced. I used XnViewMP to cause the crashing instead of a clipboard manager as it's just easier to open/close and manipulate. Gimp profile as a new user, but I can still get it to fail and the lag is still there. I have found that it does crash less often with a bare ![]() It was mentioned before that this might be a configuration problem. Do note that the error when gimp is closing happens whether gthumb is open or not.Ĭlipboard: sending image data as 'image/x-xcf' clipboard: sending image data as 'image/png' (gimp-2.10:9520 ): GLib-CRITICAL **: 09:37:07.076: Source ID 23198 was not found when attempting to remove it EXIT: app_exit_after_callback gimp-2.10: GEGL-WARNING: (gegl-tile-handler-cache.c:977 ):gegl_tile_cache_destroy: runtime check failed: (g_queue_is_empty (&cache_queue )) EEEEeEeek! 4 GeglBuffers leaked Here I open the image from gthumb and show that you can copy and paste just fine without lag or crash. Once gimp finishes it's crash, XnViewMP resumes to load and open. You will notice in the gimp console that it is writing to the clipboard right before it crashes. Now when I try to launch XnViewMP, you can see it hang for a bit and then gimp will crash. I again copy the base layer and paste it as a new layer twice, and you will notice this time the operation is almost instant, and of course without a crash. In this video I open the image directly into gimp without XnViewMP being open. You will notice as soon as the copy is made that the cursor goes into busy mode until the crash about 10 seconds later. Next, (using shortcuts) I copy the base layer and paste as a new layer. In this video I open an image from XnviewMP into gimp. I made a few videos showing the problem in action. ) (script-fu:14629 ): LibGimpBase-WARNING **: 19:09:58.461: script-fu: gimp_wire_read (): error Additional information You can then get a meaningful backtrace from your debugger if you break on the gdk_x_error () function. To debug your program, run it with the -sync command line option to change this behavior. (Details: serial 314790 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. The error was 'BadWindow (invalid Window parameter)'.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |