Bug 31510

Summary: telepathy-logger-0.1.5-1.fc14: raise: Process /usr/libexec/telepathy-logger was killed by signal 6
Product: Telepathy Reporter: Brian Pepple <bpepple>
Component: loggerAssignee: Telepathy bugs list <telepathy-bugs>
Status: RESOLVED FIXED QA Contact: Telepathy bugs list <telepathy-bugs>
Severity: normal    
Priority: medium CC: pochu27
Version: unspecified   
Hardware: Other   
OS: All   
Whiteboard: r+
i915 platform: i915 features:
Attachments: Backtrace
Don't abort the logger because we got an error

Description Brian Pepple 2010-11-09 11:42:48 UTC 
Created attachment 40161 [details]
Backtrace

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.

Original Bug: https://bugzilla.redhat.com/show_bug.cgi?id=651543
Comment 1 Emilio Pozuelo Monfort 2010-12-06 07:21:49 UTC 
Created attachment 40834 [details] [review]
Don't abort the logger because we got an error

I don't know how to reproduce that (my guess is it's a rance condition), but in any case, I don't think we should abort the logger because we received an error.
Comment 2 Guillaume Desmottes 2010-12-06 07:24:35 UTC 
++
Comment 3 Emilio Pozuelo Monfort 2010-12-06 08:04:39 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.