Bug 663948

Summary: [abrt] hplip-gui-3.10.9-5.fc14: _dbus_marshal_read_uint32: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: paper512
Component: hplipAssignee: Tim Waugh <twaugh>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: jpopelka, twaugh
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:02f82162ba36f67ab582013f2d7b478eca7bfa62
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-12-17 14:38:54 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 paper512 2010-12-17 13:36:22 UTC 
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/python /usr/bin/hp-toolbox
component: hplip
crash_function: _dbus_marshal_read_uint32
executable: /usr/bin/python
kernel: 2.6.35.9-64.fc14.i686
package: hplip-gui-3.10.9-5.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1292591404
uid: 501

How to reproduce
-----
1.
2.
3.
I run HP device manager. I chose: send a fax. I chose: add a cover page. I add an address to send the fax to (with its faxnumber). I type: send the fax and the gui crashes, but it puts the document in the queue. This document stays there forever, so it is not sent out.
When I make a document in open office write and print to the fax, nothing happens. It puts the document in the queue, but it is not printed(faxed). No error messages in this case. Scanning works. Testpage print works. Printer is HP officejet pro L7780.
Comment 1 paper512 2010-12-17 13:36:25 UTC 
Created attachment 469363 [details]
File: backtrace
Comment 2 Tim Waugh 2010-12-17 14:38:54 UTC 

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