Bug 595836 - [abrt] crash in telepathy-idle-0.1.6-1.fc13: Process /usr/libexec/telepathy-idle was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in telepathy-idle-0.1.6-1.fc13: Process /usr/libexec/telepathy-i...
Keywords:
Status: CLOSED DUPLICATE of bug 630080
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-idle
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:1eeb1373860ab233625c9449072...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-25 18:25 UTC by Lubos Kocman
Modified: 2010-11-09 14:52 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 14:52:05 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (8.92 KB, text/plain)
2010-05-25 18:25 UTC, Lubos Kocman
no flags Details

Description Lubos Kocman 2010-05-25 18:25:16 UTC
abrt 1.1.0 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/telepathy-idle
comment: Tried to connect to irc server over ssl when ssl is not supported on the server.
component: telepathy-idle
crash_function: iface_ssl_disconnect_impl_full
executable: /usr/libexec/telepathy-idle
global_uuid: 1eeb1373860ab233625c9449072aa72717d535e9
kernel: 2.6.33.3-85.fc13.i686.PAE
package: telepathy-idle-0.1.6-1.fc13
rating: 4
reason: Process /usr/libexec/telepathy-idle was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Try to connect to a irc server over ssl (when ssl is not supported)
2.
3.

Comment 1 Lubos Kocman 2010-05-25 18:25:23 UTC
Created attachment 416466 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 14:52:05 UTC

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

Comment 3 Karel Klíč 2010-11-09 14:52:05 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 #630080.

Sorry for the inconvenience.


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