FS#43902 - Gimp segfault on libbabl and is unkillable + some KDE apps are then blocked

Attached to Project: Arch Linux
Opened by Lukas Zavodny (LukynZ) - Saturday, 21 February 2015, 05:48 GMT
Last edited by Doug Newgard (Scimmia) - Friday, 27 February 2015, 15:46 GMT
Task Type Bug Report
Category Packages: Extra
Status Closed
Assigned To No-one
Architecture All
Severity Low
Priority Normal
Reported Version
Due in Version Undecided
Due Date Undecided
Percent Complete 100%
Votes 4
Private No

Details

Description:

Gimp is running fine until I try to close it. Then nothing happens. Foce close dialog do nothing. It has D status.
Under the KDE I'm then unable to run krunner, system monitor, sometimes konsole as far as I found for now
Goint to TTY, try to log as root...after password I'm just waiting for shell command line..nothing happens

Additional info:
gimp 2.8.14-1
babl 0.1.10-2

dmesg: http://pastebin.com/MZkLkE6T

Steps to reproduce:
1. Under KDE run gimp
2. try to close gimp
This task depends upon

Closed by  Doug Newgard (Scimmia)
Friday, 27 February 2015, 15:46 GMT
Reason for closing:  Duplicate
Additional comments about closing:   FS#43921 
Comment by Jan (medhefgo) - Thursday, 26 February 2015, 15:00 GMT
The underlying kernel bug does not happen under 3.20 from testing.
Comment by Alexandre Rosenberg (arekkusu) - Thursday, 26 February 2015, 15:21 GMT
I believe this is related to  FS#43921 . At least as far as the kernel aspect goes (gimp segfault is likely a separate issue).

In particular it would be interested if process "khugepaged" end up in State D (disk sleep) some time after the gimp crash.

Jan: Anything more specific regarding what is causing the issue with 3.19 kernel ?
Comment by Jan (medhefgo) - Thursday, 26 February 2015, 16:40 GMT
Looks like it's the same kernel issue, though, khugepaded does not go into D state for me (not even after the kernel complained that gimp is stuck). I have no particular knowledge whether the kernel guys actually fixed the bug or not, I only tried the newer kernel to see if it still happens. And since it doesn't on the newer kernel, I would assume so. If you really wanna make sure, you can do a reverse bisect and/or ask on the kernel mailing list.
Comment by Jan (medhefgo) - Friday, 27 February 2015, 15:15 GMT
It seems to only happen if the nvidia binary blob is used. If nouveau is used, gimp doesn't even segfault when closing.
Comment by Alexandre Rosenberg (arekkusu) - Friday, 27 February 2015, 15:25 GMT
Jan, I've heard of git bisect. Never done it and have lot to learn when it comes to compiling / testing kernel. I did actually try to reproduce the issue in a VM but to no avail.

Now, I also run the Nvidia binary driver on my system. Maybe this is common to all the reports. (dmesg indicate "tainted" kernel)

- Nvidia driver update showed up on repo today. Installed - made no difference
- Switched to Nouveau driver - I confirm that gimp does *not* crash anymore

Loading...