Bug 584130 - SIGSEGV in "release_QApplication" in /usr/bin/hp-systray
Summary: SIGSEGV in "release_QApplication" in /usr/bin/hp-systray
Keywords:
Status: CLOSED DUPLICATE of bug 583286
Alias: None
Product: Fedora
Classification: Fedora
Component: hplip
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:3824635ec6ec852b95cc20eafe2...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-04-20 19:58 UTC by Piotr Kolaczek
Modified: 2010-04-23 06:48 UTC (History)
8 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-04-23 06:48:58 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (21.97 KB, text/plain)
2010-04-20 19:58 UTC, Piotr Kolaczek 		no flags Details
View All

Description Piotr Kolaczek 2010-04-20 19:58:05 UTC 
abrt 1.0.8 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: python /usr/bin/hp-systray
component: python
executable: /usr/bin/python
kernel: 2.6.32.11-99.fc12.i686.PAE
package: python-2.6.2-4.fc12
rating: 3
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)
Comment 1 Piotr Kolaczek 2010-04-20 19:58:07 UTC 
Created attachment 407913 [details]
File: backtrace
Comment 2 Sam'l Bassett 2010-04-21 04:59:35 UTC 

How to reproduce
-----
1.  Run hp-info  (from   HPLIP package)
2.  Click on CLOSE button
3.
Comment 3 Dave Malcolm 2010-04-22 20:39:27 UTC 
hank 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*" PyQt4 sip

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.
Comment 4 Jiri Popelka 2010-04-23 06:48:58 UTC 

*** This bug has been marked as a duplicate of bug 583286 ***
Note You need to log in before you can comment on or make changes to this bug.