Bug 684529

Summary: [abrt] hplip-gui-3.10.9-14.fc14: setup_context: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: W8JSA <w8jsa>
Component: hplipAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: jpopelka, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:83bacc55354b0e5c18f4e202f1f2cff3b9f5abf5
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-03-21 17:35:24 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description W8JSA 2011-03-13 10:36:35 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 47807 bytes
cmdline: python /usr/bin/hp-systray --force-startup
component: hplip
Attached file: coredump, 31350784 bytes
crash_function: setup_context
executable: /usr/bin/python
kernel: 2.6.35.11-83.fc14.x86_64.debug
package: hplip-gui-3.10.9-14.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
How to reproduce: Not sure . . . 
time: 1299956431
uid: 500
Comment 1 W8JSA 2011-03-13 10:36:38 UTC 
Created attachment 483973 [details]
File: backtrace
Comment 2 Tim Waugh 2011-03-14 11:45:23 UTC 
It looks like this occurred when quitting the HPLIP systray application.  Are you able to get it to happen again?
Comment 3 abrt-bot 2012-03-21 17:35:24 UTC 
Backtrace analysis found this bug to be similar to bug #649839, closing as duplicate.

Bugs which were found to be similar to this bug: 
  hplip: bug #653574, bug #654166, bug #666923, bug #670025
  pygobject2: bug #649839

This comment is automatically generated.

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