Bug 668749

Summary: [abrt] simdock-1.2-10.fc14: handle_error: Process /usr/bin/simdock was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: jbox_ny
Component: simdockAssignee: Terje Røsten <terje.rosten>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 14CC: terje.rosten
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:f9bdb70a38e09db15412cf10cf1af0774a37c342
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-10-17 13:15: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:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description jbox_ny 2011-01-11 14:08:40 UTC 
abrt version: 1.1.14
architecture: x86_64
Attached file: backtrace
cmdline: simdock
component: simdock
crash_function: handle_error
executable: /usr/bin/simdock
kernel: 2.6.35.10-74.fc14.x86_64
package: simdock-1.2-10.fc14
rating: 4
reason: Process /usr/bin/simdock was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1294754538
uid: 500

How to reproduce
-----
1. It happened when I tried to start SimDock in Gnome environment
2.
3.
Comment 1 jbox_ny 2011-01-11 14:08:42 UTC 
Created attachment 472819 [details]
File: backtrace
Comment 2 jbox_ny 2011-01-19 20:18:31 UTC 
Package: simdock-1.2-10.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. It happened when I tried to start SimDock in Gnome environment
2.
3.
Comment 3 Terje Røsten 2011-10-17 13:15:44 UTC 

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