Bug 598298 - [abrt] crash in tkgate-2.0-9.beta10.fc13: Tk_MakeWindowExist: Process /usr/bin/tkgate was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in tkgate-2.0-9.beta10.fc13: Tk_MakeWindowExist: Process /usr/bi...
Status: CLOSED DUPLICATE of bug 576849
Alias: None
Product: Fedora
Classification: Fedora
Component: tkgate
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Thibault North
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:a2a9e8ae251be2ebebe27963a1a...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-01 03:12 UTC by robert fairb
Modified: 2010-08-03 08:40 UTC (History)
3 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-08-03 08:40:39 UTC


Attachments (Terms of Use)
File: backtrace (15.85 KB, text/plain)
2010-06-01 03:12 UTC, robert fairb
no flags Details

Description robert fairb 2010-06-01 03:12:33 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: tkgate
component: tkgate
crash_function: Tk_MakeWindowExist
executable: /usr/bin/tkgate
global_uuid: a2a9e8ae251be2ebebe27963a1aa446f3cbf1bdb
kernel: 2.6.33.4-95.fc13.i686.PAE
package: tkgate-2.0-9.beta10.fc13
rating: 4
reason: Process /usr/bin/tkgate was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.i just tryed to open tkgate
2.
3.

Comment 1 robert fairb 2010-06-01 03:12:34 UTC
Created attachment 418440 [details]
File: backtrace

Comment 2 roamvalley 2010-06-03 01:08:42 UTC
Package: tkgate-2.0-9.beta10.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.after login gnome
2.open Digital Circuit Simulator
3.crashed

Comment 3 roamvalley 2010-06-13 04:12:41 UTC
Package: tkgate-2.0-9.beta10.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1. Open Digital Circuit Simulator
2. It's crashed

Comment 4 Thibault North 2010-08-03 08:40:39 UTC

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


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