Bug 625869 - [abrt] tk-1:8.5.8-2.fc13: Process /usr/bin/wish8.5 was killed by signal 11 (SIGSEGV)
Summary: [abrt] tk-1:8.5.8-2.fc13: Process /usr/bin/wish8.5 was killed by signal 11 (S...
Keywords:
Status: CLOSED DUPLICATE of bug 625747
Alias: None
Product: Fedora
Classification: Fedora
Component: tk
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Jaroslav Škarvada
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e494cb9b67b0cf535e020fb8be4...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-08-20 16:35 UTC by cesar.davalos@inegi.org.mx
Modified: 2010-08-23 09:08 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-08-23 09:08:36 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (16.74 KB, text/plain)
2010-08-20 16:35 UTC, cesar.davalos@inegi.org.mx 		no flags Details
View All

Description cesar.davalos@inegi.org.mx 2010-08-20 16:35:35 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: wish /usr/bin/amsn
comment: amsn update before it took a lot to start chat session, after the upgrade was an error starting assignment
component: tk
executable: /usr/bin/wish8.5
kernel: 2.6.33.6-147.2.4.fc13.i686.PAE
package: tk-1:8.5.8-2.fc13
rating: 3
reason: Process /usr/bin/wish8.5 was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)
time: 1282303431
uid: 500

How to reproduce
-----
1.amsn upgrade
2.restart the computer
3.run amsn and sing in
Comment 1 cesar.davalos@inegi.org.mx 2010-08-20 16:35:40 UTC 
Created an attachment (id=439986)
File: backtrace
Comment 2 cesar.davalos@inegi.org.mx 2010-08-20 17:11:18 UTC 
Package: tk-1:8.5.8-2.fc13
Architecture: i686
OS Release: Fedora release 13 (Goddard)


How to reproduce
-----
1.run empathy
2.sign in 
3.sign in ok


Comment
-----
I think there confilctos between amsn and empathy
Comment 3 Jaroslav Škarvada 2010-08-23 09:08:36 UTC 

*** This bug has been marked as a duplicate of bug 625747 ***
Note You need to log in before you can comment on or make changes to this bug.