Bug 584458

Summary: SIGSEGV in "release_QApplication" in /usr/bin/hp-systray
Product: [Fedora] Fedora Reporter: tiagoalmeida <hugocosta22>
Component: hplipAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: dmalcolm, ivazqueznet, james.antill, jonathansteffan, jpopelka, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard: abrt_hash:479a0922afea01cc7d2e7e6c27322b60df121205
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-04-23 06:34:36 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description tiagoalmeida 2010-04-21 15:50:11 UTC 
abrt 1.0.8 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: python /usr/bin/hp-systray
comment: just started the system
component: python
executable: /usr/bin/python
kernel: 2.6.32.11-99.fc12.x86_64
package: python-2.6.2-4.fc12
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 tiagoalmeida 2010-04-21 15:50:14 UTC 
Created attachment 408117 [details]
File: backtrace
Comment 2 Dave Malcolm 2010-04-22 20:54:23 UTC 
Thank you for reporting this bug.

How reproducible is this problem?  If you run the program from a terminal, is an error message printed?

What is the output of running the following command?
  rpm -qa hplip-gui "qt*" sip PyQt4

Looking at the backtrace, it looks like the problem occurred in the program's single thread in release_QApplication

Reassigning component from "python" to "hplip";  hopefully the hplip maintainer will be able to figure this out further or reassign as necessary.

(The backtrace looks very similar to that in bug 584353; perhaps they are the same underlying issue?)
Comment 3 Jiri Popelka 2010-04-23 06:34:36 UTC 

*** This bug has been marked as a duplicate of bug 583286 ***