LinuxQuestions.org
Review your favorite Linux distribution.
Go Back   LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware
User Name
Password
Slackware This Forum is for the discussion of Slackware Linux.

Notices


Reply
  Search this Thread
Old 07-28-2018, 04:33 PM   #1
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 11,644

Rep: Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360
Gimp bug or what?


I'm trying to copy a section out of a png to paste it as a new image and gimp crashes 1 second after I press 'Ctrl_C' or Edit/Copy. It handles jpegs fine, but crashes on pngs. I grabbed this error from STDOUT
Code:
(script-fu:5056): LibGimpBase-WARNING **: 21:53:37.744: script-fu: gimp_wire_read(): error
Missing fast-path babl conversion detected, Implementing missing babl fast paths
accelerates GEGL, GIMP and other software using babl, warnings are printed on
first occurance of formats used where a conversion has to be synthesized
programmatically by babl based on format description

*WARNING* missing babl fast path(s): "R'G'B' double" to "CIE Lab double"
*WARNING* missing babl fast path(s): "R'G'B'A u8" to "A u8"
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 59922 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:5119): LibGimpBase-WARNING **: 21:54:22.247: script-fu: gimp_wire_read(): error
It's all gobbledygook to me, but it evidently doesn't like me. The video is a HD4000, and there's a recent upgrade to current (gimp-2.10). Ldd reports no libs AWOL.
 
Old 07-28-2018, 07:58 PM   #2
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 652

Rep: Reputation: 170Reputation: 170
Quote:
Originally Posted by business_kid View Post
I'm trying to copy a section out of a png to paste it as a new image and gimp crashes 1 second after I press 'Ctrl_C' or Edit/Copy. It handles jpegs fine, but crashes on pngs.
I do not see this with gimp-2.10 on current64 when loading and trying to copy a section from a png (not from a video though)

Quote:
Missing fast-path babl conversion detected, Implementing missing babl fast paths
accelerates GEGL, GIMP and other software using babl, warnings are printed on
first occurance of formats used where a conversion has to be synthesized
programmatically by babl based on format description

*WARNING* missing babl fast path(s): "R'G'B' double" to "CIE Lab double"
*WARNING* missing babl fast path(s): "R'G'B'A u8" to "A u8"
This is what I also see when starting gimp in a console-window (instead of from a menu)

No gimp-expert either, some duckduckgoing on the errors gave.....

Quote:
(script-fu:5056): LibGimpBase-WARNING **: 21:53:37.744: script-fu: gimp_wire_read(): error
might be linked to some old gimp-stuff lying about

The "error_code 3 request_code 18 minor_code 0" in the portion
Quote:
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 59922 error_code 3 request_code 18 minor_code 0)
led to the unanswered question "you installed all updates and restarted the system?"

but that started with a different serial no (20405)....

Do you get any more output when you start gimp from a console and go through your crash-sequence?

EDIT: in preferences/debugging you can change the level of reporting;

Last edited by brobr; 07-29-2018 at 02:11 AM.
 
Old 07-28-2018, 08:06 PM   #3
frankbell
LQ Guru
 
Registered: Jan 2006
Location: Virginia, USA
Distribution: Slackware, Ubuntu MATE, Mageia, and whatever VMs I happen to be playing with
Posts: 16,411
Blog Entries: 27

Rep: Reputation: 4928Reputation: 4928Reputation: 4928Reputation: 4928Reputation: 4928Reputation: 4928Reputation: 4928Reputation: 4928Reputation: 4928Reputation: 4928Reputation: 4928
I was also unable to duplicate this problem with Gimp v. 2.8.18 on Slackware 14.2.

I saved a *.jpg as a *.png, closed the file then opened the *.jpg. I copied a portion of the *.png, told Gimp I wanted to "create new," and successfully paste the bit of image from the clipboard into a new image.
 
Old 07-29-2018, 05:27 AM   #4
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 11,644

Original Poster
Rep: Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360
Thanks all for your replies
Quote:
Originally Posted by brobr
Do you get any more output when you start gimp from a console and go through your crash-sequence?
I get this when gimp starts up
Code:
(script-fu:5985): LibGimpBase-WARNING **: 10:19:27.827: script-fu: gimp_wire_read(): error
bash-4.4$ gimp
Missing fast-path babl conversion detected, Implementing missing babl fast paths
accelerates GEGL, GIMP and other software using babl, warnings are printed on
first occurance of formats used where a conversion has to be synthesized
programmatically by babl based on format description

*WARNING* missing babl fast path(s): "R'G'B' double" to "CIE Lab double"
And this when I select rectangle, press Ctrl_C and it crashes out
Code:
*WARNING* missing babl fast path(s): "R'G'B'A u8" to "A u8"
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 55498 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:15841): LibGimpBase-WARNING **: 10:27:50.456: script-fu: gimp_wire_read(): error
To my eye, that's identical to the stuff in the console.
As for old gimp stuff, I did find ~/.gimp-2.8 & got rid of it, but no change. The png is a conversion by xnviewMP and it opens fine in everything else.
I tried the same conversion on another (tiny) pmg instead of the rather large one I was using, and it worked, but I got some more information
Code:
*WARNING* missing babl fast path(s): "R'G'B' double" to "CIE Lab double"
(II) AIGLX: Suspending AIGLX clients for VT switch


############################################ onTimerDirectoryChanged  1

######## checkChildren


############################################ onTimerDirectoryChanged ok



############################################ onTimerDirectoryChanged  
1 ######## checkChildren


############################################ onTimerDirectoryChanged ok

*WARNING* missing babl fast path(s): "R'G'B'A u8" to "A u8"
/usr/bin/gimp: GEGL-WARNING: (gegl-tile-handler-cache.c:866):gegl_tile_cache_destroy: runtime check failed: (g_queue_is_empty (&cache_queue))
EEEEeEeek! 1 GeglBuffers leaked
I haven't installed any updates, if there have been any. Slackware badly needs a new release, as too much has changed. To my mind, the 'Buffers Leaked' is significant, but there may not have been enough to crash things.
 
Old 07-29-2018, 10:57 AM   #5
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 652

Rep: Reputation: 170Reputation: 170
Quote:
The png is a conversion by xnviewMP
Business-kid, I reproduced your bug. I wondered whether it has to do with starting with raw or 16-bit images as a source of the png. After downloading xnviewMP and loading a 16-bit image (which normally wouldn't display correctly in The Gimp-2.8), I exported a selection both as a png and as a jpg image and loaded these files in The Gimp. Then I tried to copy a selection from the png-image and the Gimp crashed as you described. With the jpg no such thing. I tried the same with a png coming from the same 16-bit image but then processed in FIJI, and again the Gimp crashed, so it does not seem to be linked to the program producing the png or the source of the image (in your case a video, in mine a 16-bit radioactivity scan). As mentioned above loading a 'simple' png (from a desktop-screen shot) did not cause a crash.

As the jpg works, maybe use that as a workaround. It might also point to libpng as the culprit (or the gimp not calling it correctly; wouldn't be able to tell).

I managed to get some more output, but whether this helps anyone....

Start The Gimp in one terminal, and find its pid in another:

Quote:
16003 pts/14 Ss 0:00 bash
16016 pts/13 Sl+ 0:03 gimp --sync
16037 pts/13 Sl+ 0:00 /usr/lib64/gimp/2.0/plug-ins/script-fu -gimp 10 9 -ru
and start strace and then continue with the actions in gimp. This pops up in the strace-terminal:
Quote:
bash-4.4$ strace -p 16037
strace: Process 16037 attached
select(1024, [10], NULL, NULL, NULL) = 1 (in [10])
read(10, "", 4) = 0
getpeername(2, 0x7ffc5f6a02d0, [128]) = -1 ENOTSOCK (Socket operation on non-socket)
futex(0x7f5d3e7e9598, FUTEX_WAKE_PRIVATE, 2147483647) = 0
ioctl(2, TCGETS, {B38400 opost isig -icanon -echo ...}) = 0
getpid() = 16037
openat(AT_FDCWD, "/etc/localtime", O_RDONLY|O_CLOEXEC) = 7
fstat(7, {st_mode=S_IFREG|0644, st_size=3687, ...}) = 0
fstat(7, {st_mode=S_IFREG|0644, st_size=3687, ...}) = 0
read(7, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0\10\0\0\0\0"..., 4096) = 3687
lseek(7, -2347, SEEK_CUR) = 1340
read(7, "TZif2\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0\10\0\0\0\10\0\0\0\0"..., 4096) = 2347
close(7) = 0
write(2, "\n(script-fu:16037): LibGimpBase-"..., 113) = 113
shmdt(0x7f5d34b10000) = 0
exit_group(0) = ?
+++ exited with 0 +++
Output in terminal from which gimp was run:
Quote:
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 117284 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.)
bash-4.4$
(script-fu:16037): LibGimpBase-WARNING **: 16:35:03.751: script-fu: gimp_wire_read(): error
I went ahead and filed this as a bug at The Gimp site. https://gitlab.gnome.org/GNOME/gimp/issues/1943

hth


EDIT: this is on current as of 28/7/18

Last edited by brobr; 07-29-2018 at 11:51 AM.
 
2 members found this post helpful.
Old 07-29-2018, 11:56 AM   #6
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 652

Rep: Reputation: 170Reputation: 170
Quote:
I tried the same conversion on another (tiny) pmg instead of the rather large one I was using, and it worked,
Yes, I see this as well after reducing my big png-file to a smaller one before copying; so size seems to matter (the jpg was much smaller than the png I used above)

Last edited by brobr; 07-29-2018 at 12:02 PM.
 
Old 07-30-2018, 04:07 AM   #7
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 11,644

Original Poster
Rep: Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360
Quote:
Originally Posted by brobr
I went ahead and filed this as a bug at The Gimp site. https://gitlab.gnome.org/GNOME/gimp/issues/1943
Goopd. That saves me the bother. As for linpng being involved, that's a definite maybe. I was using ve3ry high res dicom images (bitmaps over 3000 x 2000). I don't see any mention of libpng or any child process in the verbiage
The kernel of appears to be here
Code:
/usr/bin/gimp: GEGL-WARNING: (gegl-tile-handler-cache.c:866):gegl_tile_cache_destroy: runtime check failed: (g_queue_is_empty (&cache_queue))
EEEEeEeek! 1 GeglBuffers leaked
Gegl (Generic Graphics Library) is a gimp thing, basically a copy/paste buffer, it seems. Buffer leakage is always bad and very hackable, if you know how to go about it.
 
Old 07-30-2018, 04:25 AM   #8
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 652

Rep: Reputation: 170Reputation: 170
Yes, I saw that gegl-leak message too; have added it to the bug-report (it was still open in my browser :-)
 
Old 07-30-2018, 06:02 AM   #9
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 11,644

Original Poster
Rep: Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360
Interesting, this.

I'm converting hip XRays to usable formats, zooming to max, and snipping chunks of what's in focus at high zoom (It helps if you know that my left femur is only partially set, and I'm in a medical mess here).

I took a random shot of the hips and converted it into many formats - they all worked including png. But, when the image was zoomed to 'lifesize' in Xnview, That's when I had trouble. The video memory thrown about would have been considerably bigger.

I confirmed this by returning to my original image causing the issue, zooming to lifesize, pressing F11 for full screen, and then repeating. I got the buffer leak this time, but no crash

With a fair degree of probability we can say
1. The buffer leakage is related to video memory, not file size only.
2. The buffer leakage in sufficient quantity caused the crash
3. Total ram usage is a factor affecting this also. At the moment, I'm using 1 gig of 6G; Yesterday, I was online, printing a long job, watching YouTube periodically, with consoles and 4 virtual terminals going and I was also compiling ImageMagick while XnView and Gimp were going. It was certainly easier to cause offense with a buffer leakage!

(I'd like to see anyone do that lot in windows and get away with 6G)
 
Old 07-30-2018, 08:50 AM   #10
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 652

Rep: Reputation: 170Reputation: 170
Ok, I had to reboot my computer (upgraded the kernel) and have much less stuff running now and the crash does not happen, however much I try. Zooming in-out, bigger pictures etc. (I have quite a bit of ram and that is not quickly filled up). I have XnView not open.....

Then I opened XnView (shows "libpng warning: iCCP: known incorrect sRGB profile")
Still no crash when editing my 'crash-file' in the gimp

Then I opened a small file in XnView (72kb jpg)

Gimp crashes upon selecting a section of my 'crash-file'

Open gimp again, load crash-file, and Gimp crashes upon copying a section of my 'crash-file'

Close a big java-application

Open gimp again, load crash-file, and Gimp crashes upon copying a section of my 'crash-file'

Close jpg in Xnview

Open gimp again, load crash-file, and Gimp does NOT crash upon copying a section of my 'crash-file'

Open another jpg (176kb) in XnView

Gimp crashes upon copying a newly selected section of my 'crash-file'

XnView kills The Gimp by having an image file open........

Can you reproduce that???

PS Fiji (with a big image) was open all this time, so that could be a workable alternative for you...
PS2 Also open from the start: Inkscape, Firefox (~18 tabs), Vivaldi (25 tabs), IGB (a java program), Claws-mail, Scite (3 tabs) and Leafpad

Last edited by brobr; 07-30-2018 at 10:09 AM.
 
Old 07-30-2018, 10:15 AM   #11
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 11,644

Original Poster
Rep: Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360
I take your 'crash file' is a xnview converted png file of large dimensions. Your attempt to verify this memory thing reads a bit like the words of 'Lanigan's Ball'
Quote:
I stepped out, I stepped in again,
I stepped out again, I stepped in again,
I stepped out, I stepped in again,
Learning to dance for Lanigan's ball.
I have no debugging expertise on linux. My programming was a lot more low level (Assembler, VHDL, various PLCs) With the tools at my disposal, I can do no better than say that buffers are set in pseudo random places and may or may not cause a crash if they leak, dependent on whether they want to overwrite something. It's a pity you didn't scan for gegl buffer leakage, or did you?

Also, I was opening dicoms in XnView, converting them, and writing to disk (jpg or png). Then opening the jpeg/png in gimp, and cutting a section out. My work with xnview was over before I started with gimp. Jpegs worked, the one png crashed yesterday, although it worked today.

XnView and Gimp coexist quite happily here, files open or not. If you opened the same file in both, and modified that, you'd be asking for it, but things may not notice.
 
Old 07-30-2018, 11:09 AM   #12
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 652

Rep: Reputation: 170Reputation: 170
Wow, didn't know I had the talent to write a song....

At my end, the file open in The Gimp when crashing, does not need to be made with XnView,
The file that is open in XnView does not need to be the same as the file open in The Gimp - and can be very small, a jpg or a png;
As long as something is open in XnView, The Gimp crashes when copying something from a large (> 1 mB, 600 dpi) file (tif, png, jpg).

I am using this version XnViewMP-linux-x64.tgz

It does not matter whether XnView is run from /opt or from some other folder.
I use 'sh xnview.sh' to start it; using ./XnView does not work, it asks for Qt5.9:
Code:
bash-4.4$ ./XnView
./XnView: /usr/lib64/libQt5Core.so.5: version `Qt_5.9' not found (required by ./XnView)
Maybe there are some resources that need sharing but cannot; XnView is built in another environment than Slackware (current).
 
1 members found this post helpful.
Old 07-30-2018, 12:18 PM   #13
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 11,644

Original Poster
Rep: Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360
I was trying to follow your open/close/crash sequence - hence the song reference. It's a humourous song about a guy with 2 left feet in the Irish traditional form.

qt-5.9 is available in Alien Bob's builds. Installed it today.

I marked this solved because I asked "Have I bad breath or is this a gimp bug?"
You duplicated it, and reported it which is cool, because you'll have to respond on the bug if the devs come back to you :-D, e.g. 'recompile gimp-latest with this patch.'

So it is a gimp bug.
 
Old 08-01-2018, 07:52 AM   #14
business_kid
LQ Guru
 
Registered: Jan 2006
Location: Ireland
Distribution: Slackware & Android
Posts: 11,644

Original Poster
Rep: Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360Reputation: 1360
Postscript to all this.

Although it's clumsier, you can highlight a section in Xnview, then crop & export it in any format all in XnView, so I needn't have involved gimp at all :-o. Some choices pop up above the picture after you select an area. Oh well.
 
Old 09-24-2018, 07:13 AM   #15
brobr
Member
 
Registered: Oct 2003
Location: uk
Distribution: Slackware
Posts: 652

Rep: Reputation: 170Reputation: 170
Quote:
Originally Posted by business_kid View Post
..
So it is a gimp bug.
No, a userland-one
 
  


Reply


Thread Tools Search this Thread
Search this Thread:

Advanced Search

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is Off
HTML code is Off



Similar Threads
Thread Thread Starter Forum Replies Last Post
LXer: GIMP 2.10 Development Continues, GIMP 2.9.4 Lands New Features After 8 Months LXer Syndicated Linux News 0 07-13-2016 04:31 AM
LXer: GIMP Painter And GIMP Paint Studio Transform GIMP Into The Ultimate Painting Tool LXer Syndicated Linux News 0 02-08-2011 05:40 PM
LXer: Gimp Paint Studio(GPS)- A collection of brushes and accompanying tool presets for GIMP LXer Syndicated Linux News 0 02-02-2011 02:13 AM
LXer: Gimp Paint Studio [Gimp Optimized for Drawing and Painting] LXer Syndicated Linux News 0 05-04-2009 01:30 PM
Why does Ubuntu update GIMP with a pointer bug?! mamadu.bwana Ubuntu 16 01-14-2008 04:50 PM

LinuxQuestions.org > Forums > Linux Forums > Linux - Distributions > Slackware

All times are GMT -5. The time now is 06:37 AM.

Main Menu
Advertisement
My LQ
Write for LQ
LinuxQuestions.org is looking for people interested in writing Editorials, Articles, Reviews, and more. If you'd like to contribute content, let us know.
Main Menu
Syndicate
RSS1  Latest Threads
RSS1  LQ News
Twitter: @linuxquestions
Open Source Consulting | Domain Registration