Bug 651543 - [abrt] telepathy-logger-0.1.5-1.fc14: raise: Process /usr/libexec/telepathy-logger was killed by signal 6 (SIGABRT)
Summary: [abrt] telepathy-logger-0.1.5-1.fc14: raise: Process /usr/libexec/telepathy-l...
Keywords:
Status: CLOSED DUPLICATE of bug 677914
Alias: None
Product: Fedora
Classification: Fedora
Component: telepathy-logger
Version: 14
Hardware: x86_64
OS: Unspecified
low
medium
Target Milestone: ---
Assignee: Brian Pepple
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:d07af471b826b0ea648eca15d9b...
: 626528 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-11-09 19:21 UTC by Matěj Cepl
Modified: 2018-04-11 16:58 UTC (History)
2 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-20 16:24:57 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (11.63 KB, text/plain)
2010-11-09 19:21 UTC, Matěj Cepl 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
FreeDesktop.org 31510 0 None None None Never

Description Matěj Cepl 2010-11-09 19:21:09 UTC 
abrt version: 1.1.13
architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/telepathy-logger
component: telepathy-logger
crash_function: raise
executable: /usr/libexec/telepathy-logger
kernel: 2.6.35.6-48.fc14.x86_64
package: telepathy-logger-0.1.5-1.fc14
rating: 4
reason: Process /usr/libexec/telepathy-logger was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1289330422
uid: 500

How to reproduce
-----
1.testing the latest empathy I have connected to my regular account, and then terminated immediately when I got connected.
2.
3.
Comment 1 Matěj Cepl 2010-11-09 19:21:12 UTC 
Created attachment 459219 [details]
File: backtrace
Comment 2 Brian Pepple 2010-11-13 17:30:22 UTC 
*** Bug 626528 has been marked as a duplicate of this bug. ***
Comment 3 abrt-bot 2012-03-20 16:24:57 UTC 
Backtrace analysis found this bug to be similar to bug #677914, closing as duplicate.

This comment is automatically generated.

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