Bug 713424 - [abrt] hplip-3.11.5-1.fc14: ipConvert: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
Summary: [abrt] hplip-3.11.5-1.fc14: ipConvert: Process /usr/bin/python was killed by ...
Keywords:
Status: CLOSED UPSTREAM
Alias: None
Product: Fedora
Classification: Fedora
Component: hplip
Version: 14
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tim Waugh
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:be683a5208cb53e1b62e8acdcde...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-06-15 12:19 UTC by balustre
Modified: 2011-06-30 09:49 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-06-30 09:49:37 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (85.29 KB, text/plain)
2011-06-15 12:19 UTC, balustre 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Launchpad 803816 0 None None None Never

Description balustre 2011-06-15 12:19:49 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 87337 bytes
cmdline: /usr/bin/python /usr/bin/hp-scan
component: hplip
Attached file: coredump, 23670784 bytes
crash_function: ipConvert
executable: /usr/bin/python
kernel: 2.6.35.13-92.fc14.x86_64
package: hplip-3.11.5-1.fc14
rating: 4
reason: Process /usr/bin/python was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1308226685
uid: 500

How to reproduce
-----
1. Try to scan with hp-scan
2. The printer responds but nothing happens
3. hplip bug
Comment 1 balustre 2011-06-15 12:19:53 UTC 
Created attachment 504856 [details]
File: backtrace
Comment 2 Jiri Popelka 2011-06-29 11:06:44 UTC 
Have no idea why the scanning doesn't work, but the crash is result of some race condition.

Thread 1 was trying to dereference hJob variable having 0 value in ipmain.c:ipConvert().

And Thread 2 was performing 'Cancel an in-progress scanning operation' (don't know the reason) and probably had zeroed the hJob before Thread 1 accessed it.
Comment 3 Tim Waugh 2011-06-30 09:49:37 UTC 
Reported upstream.
Note You need to log in before you can comment on or make changes to this bug.