Bug 637387 - [abrt] telepathy-gabble-0.9.18-1.fc14: __strcmp_ssse3: Process /usr/libexec/telepathy-gabble was killed by signal 11 (SIGSEGV)
Summary: [abrt] telepathy-gabble-0.9.18-1.fc14: __strcmp_ssse3: Process /usr/libexec/t...
Keywords:
Status: CLOSED DUPLICATE of bug 647414
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-gabble
Version: 14
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:760a6fb369bb10398653bb5733a...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-09-25 12:22 UTC by satellitgo
Modified: 2012-03-21 17:38 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-21 17:38:01 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (65.69 KB, text/plain)
2010-09-25 12:22 UTC, satellitgo 		no flags Details
View All

Description satellitgo 2010-09-25 12:22:51 UTC 
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/telepathy-gabble
component: telepathy-gabble
crash_function: __strcmp_ssse3
executable: /usr/libexec/telepathy-gabble
kernel: 2.6.35.4-28.fc14.i686.PAE
package: telepathy-gabble-0.9.18-1.fc14
rating: 4
reason: Process /usr/libexec/telepathy-gabble was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1285417289
uid: 500

How to reproduce
-----
1.start sugar-emulator
2.
3.
Comment 1 satellitgo 2010-09-25 12:22:53 UTC 
Created attachment 449591 [details]
File: backtrace
Comment 2 Brian Pepple 2010-12-02 15:12:17 UTC 
Are you still experiencing this bug with the current version of tp-gabble (0.10.4) in F14?
Comment 3 abrt-bot 2012-03-21 17:38:01 UTC 
Backtrace analysis found this bug to be similar to bug #647414, closing as duplicate.

Bugs which were found to be similar to this bug: bug #641616, bug #647414

This comment is automatically generated.

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