Bug 734250

Summary: [abrt] xsane-0.998-4.fc14: handle_error: Process /usr/bin/xsane was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: Jason Herring <jaherring>
Component: gtk2Assignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: mclasen, nphilipp
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:6613739655d88ab6da5de571f0a43ea7e2b0fce1
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-14 08:53:44 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 Jason Herring 2011-08-29 21:35:27 UTC 
abrt version: 1.1.18
architecture: x86_64
Attached file: backtrace, 55919 bytes
cmdline: xsane
component: xsane
Attached file: coredump, 11804672 bytes
crash_function: handle_error
executable: /usr/bin/xsane
kernel: 2.6.35.14-95.fc14.x86_64
package: xsane-0.998-4.fc14
rating: 4
reason: Process /usr/bin/xsane was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1314653657
uid: 6669

How to reproduce
-----
1. start app
2. select scanner
3. crash soon after painting the main window
Comment 1 Jason Herring 2011-08-29 21:35:30 UTC 
Created attachment 520470 [details]
File: backtrace
Comment 2 Jason Herring 2011-09-01 22:37:41 UTC 
Package: xsane-0.998-4.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. removed .sane to have a clean start
2. started "Scanner Tool", and choose device dialog comes up
3. I  choose my scanner, sane begins to start, partially draws the main window then crashes


Comment
-----
Nothing special.  Does it every time.  the "Simple Scan" tool works  fine.
Comment 3 Nils Philippsen 2011-09-02 08:22:52 UTC 
X11 BadMatch error, looks like a toolkit issue:

#4  0x00000030b986a356 in gdk_x_error (display=<value optimized out>, error=<value optimized out>) at gdkmain-x11.c:466
        buf = "BadMatch (invalid parameter attributes)", '\000' <repeats 24 times>
        msg = <value optimized out>

Changing component.
Comment 4 Nils Philippsen 2011-11-14 08:53:44 UTC 

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