Bug 591446 - [abrt] crash in tk-1:8.5.7-3.fc12: raise: Process /usr/bin/wish8.5 was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in tk-1:8.5.7-3.fc12: raise: Process /usr/bin/wish8.5 was killed...
Keywords:
Status: CLOSED DUPLICATE of bug 590860
Alias: None
Product: Fedora
Classification: Fedora
Component: tk
Version: 12
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:c2d30449476a31938445ed1833e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-12 09:39 UTC by Dave Gordon
Modified: 2010-05-25 08:28 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-05-25 08:28:06 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (21.37 KB, text/plain)
2010-05-12 09:39 UTC, Dave Gordon 		no flags Details
View All

Description Dave Gordon 2010-05-12 09:39:27 UTC 
abrt 1.0.9 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: wish /usr/bin/amsn
comment: I was not present when the crash happened, so not sure how to reproduce or exactly what happened - no error messages were displayed - just the Automatic Bug Reporting Tool's crash icon was present when I returned to my computer.
component: tk
crash_function: raise
executable: /usr/bin/wish8.5
global_uuid: c2d30449476a31938445ed1833e4dc807069f28b
kernel: 2.6.32.11-99.fc12.x86_64
package: tk-1:8.5.7-3.fc12
rating: 4
reason: Process /usr/bin/wish8.5 was killed by signal 6 (SIGABRT)
release: Fedora release 12 (Constantine)
Comment 1 Dave Gordon 2010-05-12 09:39:30 UTC 
Created attachment 413374 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 08:28:06 UTC 

*** This bug has been marked as a duplicate of bug 590860 ***
Comment 3 Karel Klíč 2010-05-25 08:28:06 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #590860.

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