Bug 670605 - [abrt] xsane-0.998-1.fc14: handle_error: Process /usr/bin/xsane was killed by signal 6 (SIGABRT)
Summary: [abrt] xsane-0.998-1.fc14: handle_error: Process /usr/bin/xsane was killed by...
Keywords:
Status: CLOSED DUPLICATE of bug 696183
Alias: None
Product: Fedora
Classification: Fedora
Component: xsane
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Nils Philippsen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:b136d027f6d0045a292a4eefd5c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-01-18 19:19 UTC by thunt
Modified: 2012-03-30 13:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 13:12:32 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (32.72 KB, text/plain)
2011-01-18 19:19 UTC, thunt
no flags Details

Description thunt 2011-01-18 19:19:21 UTC
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: xsane
component: xsane
crash_function: handle_error
executable: /usr/bin/xsane
kernel: 2.6.35.10-74.fc14.x86_64
package: xsane-0.998-1.fc14
rating: 4
reason: Process /usr/bin/xsane was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1295378083
uid: 500

How to reproduce
-----
1.tried to launch xsane.
2.
3.

Comment 1 thunt 2011-01-18 19:19:23 UTC
Created attachment 474133 [details]
File: backtrace

Comment 2 thunt 2011-01-27 21:15:50 UTC
Package: xsane-0.998-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.clicked on xsane
2.
3.

Comment 3 abrt-bot 2012-03-30 13:12:32 UTC
Backtrace analysis found this bug to be similar to bug #696183, closing as duplicate.

Bugs which were found to be similar to this bug: 
  gnome-panel: bug #695396
  gtk2: bug #696183
  ucview: bug #678482, bug #682947

This comment is automatically generated.

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


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