Bug 664090 - [abrt] gscan2pdf-0.9.31-1.fc14: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
Summary: [abrt] gscan2pdf-0.9.31-1.fc14: Process /usr/bin/perl was killed by signal 11...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Fedora
Classification: Fedora
Component: perl-forks
Version: 14
Hardware: i686
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Bernard Johnson
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:27b4fe5f173e31807af9ec883bf...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-12-18 01:50 UTC by Paul Suppo
Modified: 2012-08-16 21:47 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-08-16 21:47:48 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (7.69 KB, text/plain)
2010-12-18 01:50 UTC, Paul Suppo
no flags Details

Description Paul Suppo 2010-12-18 01:50:31 UTC
abrt version: 1.1.14
architecture: i686
Attached file: backtrace
cmdline: /usr/bin/perl /usr/bin/gscan2pdf
component: gscan2pdf
executable: /usr/bin/perl
kernel: 2.6.35.9-64.fc14.i686.PAE
package: gscan2pdf-0.9.31-1.fc14
rating: 3
reason: Process /usr/bin/perl was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1292636944
uid: 500

How to reproduce
-----
1.Started Gscan. Immediate crash
2.
3.

Comment 1 Paul Suppo 2010-12-18 01:50:33 UTC
Created attachment 469480 [details]
File: backtrace

Comment 2 Bernard Johnson 2010-12-19 07:39:58 UTC
Try:

$ mv ~/.gscan2pdf ~/.gscan2pdf.bak

and then run it again.

Comment 3 Paul Suppo 2010-12-19 18:49:57 UTC
I was able to fix this concern by installing the additional HP All in 1 scanner drivers.  Although the system driver notifications stated that the all in 1 installed successfully, it was only the printer drivers and the scanner was not installed.

After a little searching on the net I did find the HP all in 1 scanner driver and gscan2pdf worked fine.

As an enhancement to gscan2pdf I would recommend notification or some other error catch rather than a total bailout.

Comment 4 Paul Suppo 2010-12-22 02:54:06 UTC
Package: gscan2pdf-0.9.31-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Correction of previous 'fixed' .. I still have the same issue.
2.to reproduce click on icon in menu. Immediate crash.
3.

Comment 5 Paul Suppo 2010-12-22 02:58:18 UTC
After this second attempt I issued the rename as you suggested. I have no .gscan2pdf in my home or sub directories.

Comment 6 Bernard Johnson 2011-08-19 21:35:20 UTC
possibly a crash in perl-forks based on the stack trace

Comment 7 Fedora End Of Life 2012-08-16 21:47:50 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping


Note You need to log in before you can comment on or make changes to this bug.