Bug 240632

Summary: crash in qt-examples-1:4.6.2-8.fc12: Process padnavigator was killed by signal 11 (SIGSEGV)
Product: [Plasma] Oxygen Reporter: Ryan Maki <ryan.maki>
Component: styleAssignee: Hugo Pereira Da Costa <hugo.pereira.da.costa>
Status: RESOLVED UPSTREAM    
Severity: normal CC: hugo.pereira.da.costa
Priority: NOR    
Version: 4.0   
Target Milestone: ---   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Attachments: Fedora bug 580750 backtrace

Description Ryan Maki 2010-06-03 19:18:27 UTC
Created attachment 47641 [details]
 Fedora bug 580750 backtrace

Version:           4.0 (using KDE 4.4.2) 
OS:                Linux

According to the bug wranglers on the Fedora Bugzilla this issue originated in the Oxygen style. As the original reporter in Fedora I'm posting this upstream.

Fedora bug 580750

abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/lib64/qt4/examples/graphicsview/padnavigator/padnavigator
comment: Crashes every time on my system when Closed.
component: qt
executable: /usr/lib64/qt4/examples/graphicsview/padnavigator/padnavigator
kernel: 2.6.31.5-127.fc12.x86_64
package: qt-examples-1:4.6.2-8.fc12
rating: 4
reason: Process /usr/lib64/qt4/examples/graphicsview/padnavigator/padnavigator
was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

Reproducible: Always

Steps to Reproduce:
1. Open qtdemo-qt4
2. Run the Graphics View > Pad Navigator example
3. Use arrow keys to navigate left, right, up, down, hit enter to open settings
4. Click window Close button

Actual Results:  
Process /usr/lib64/qt4/examples/graphicsview/padnavigator/padnavigator
was killed by signal 11 (SIGSEGV)

Expected Results:  
padnavigator closes without errors

Widgets: Oxygen style
Fedora 12 KDE desktop, running KDM and KWin
This machine has 2 quad-core processors, 16 CPUs Hyper Threaded, which has caused a few strange problems with other software in the past.
Comment 1 Hugo Pereira Da Costa 2010-06-03 22:58:09 UTC
Hi, 
Changed severity to "crash". I think I've seen similar crash elsewhere. What's new though is that I can reproduce. (was not the case before).
Will see what I can do.
Comment 2 Hugo Pereira Da Costa 2010-06-04 00:11:15 UTC
After spending a couple of hours trying to figure out what's going on, without success, I gave a try to the same app, but linked agains Qt4.7
Miracle: no more crash.
Since 
- the backtrace explicitly mentions issues inside Qt, at QPixmap deletion (which I though might have been triggered by some stuff in oxygen, but without finding anything wrong there)
- the same crash can be seen (with Qt4.6) using the bespin style
- the crash disappears when using Qt4.7

I (strongly) suspect a bug in Qt, that have been fixed for Qt4.7 (make sense ?)

Closing as an upstream bug.