Bug 587270

Summary: [abrt] crash in telepathy-idle-0.1.5-1.fc12: Process /usr/libexec/telepathy-idle was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: sergeobelare
Component: telepathy-idleAssignee: Brian Pepple <bdpepple>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: bdpepple
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:25ec5a36f13099f04c94bf1adbab82f28850d9fe
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2010-05-25 10:29:35 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 sergeobelare 2010-04-29 13:59:05 UTC 
abrt 1.0.9 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/telepathy-idle
comment: Tried to use the bundled Empathy IM client to access irc.freenode.net. Crashed. Tried several accounts and configurations, gave up. Installed and used Pidgin successfully.
component: telepathy-idle
executable: /usr/libexec/telepathy-idle
global_uuid: 25ec5a36f13099f04c94bf1adbab82f28850d9fe
kernel: 2.6.32.11-99.fc12.i686
package: telepathy-idle-0.1.5-1.fc12
rating: 4
reason: Process /usr/libexec/telepathy-idle was killed by signal 11 (SIGSEGV)
release: Fedora release 12 (Constantine)

How to reproduce
-----
1. Run Empathy
2. Attempt irc connection
3. Crash
Comment 1 sergeobelare 2010-04-29 13:59:07 UTC 
Created attachment 410115 [details]
File: backtrace
Comment 2 Karel Klíč 2010-05-25 10:29:35 UTC 

*** This bug has been marked as a duplicate of bug 538860 ***
Comment 3 Karel Klíč 2010-05-25 10:29:35 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 #538860.

Sorry for the inconvenience.