Bug 700366

Summary: [abrt] telepathy-logger-0.1.7-1.fc14: _tpl_log_manager_add_message: Process /usr/libexec/telepathy-logger was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: Sailorleo <sailorleo>
Component: telepathy-loggerAssignee: Brian Pepple <bdpepple>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 14CC: bdpepple, daniell, erko1973, martin.james.davidson, nahirmoha, ulrich
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:7610f775ffd23af63642bed7f9d183c6f1ee5e5d
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-08-16 12:14:42 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
File: backtrace none

Description Sailorleo 2011-04-28 08:33:44 UTC
abrt version: 1.1.18
architecture: i686
Attached file: backtrace, 15353 bytes
cmdline: /usr/libexec/telepathy-logger
component: telepathy-logger
Attached file: coredump, 20566016 bytes
crash_function: _tpl_log_manager_add_message
executable: /usr/libexec/telepathy-logger
kernel: 2.6.35.12-88.fc14.i686.PAE
package: telepathy-logger-0.1.7-1.fc14
rating: 4
reason: Process /usr/libexec/telepathy-logger was killed by signal 11 (SIGSEGV)
release: Fedora release 14 (Laughlin)
time: 1303775452
uid: 500

How to reproduce
-----
1. Started via Empathy 2.32.0.1-2
2. Exact reproduction method uncertain: Empathy did not exit or throw error, and failure did not occur in future instances.

Comment 1 Sailorleo 2011-04-28 08:33:46 UTC
Created attachment 495451 [details]
File: backtrace

Comment 2 Sailorleo 2011-05-02 09:32:38 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Started via Empathy 2.32.2-1
2. Reproduction method uncertain: Empathy did not exit or throw error, program was backgrounded when crash occured.

Comment 3 Nahir Mohamed 2011-05-10 19:08:16 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Launching empathy
2.
3.

Comment 4 Martin James Davidson 2011-05-11 21:52:12 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Telepathy starts automatically
2. Usually, I switch it to off-line (oe invisible) mode.

Comment 5 Martin James Davidson 2011-05-11 22:31:14 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Telepathy starts automatically
2. Usually, I switch it to off-line (oe invisible) mode.

Comment 6 Ulrich Walczak 2011-05-17 23:02:33 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. while loading telepathy
2.
3.

Comment 7 Ulrich Walczak 2011-06-14 07:31:17 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. while loading telepathy
2.
3.

Comment 8 Ulrich Walczak 2011-06-19 13:23:00 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. while loading telepathy
2.
3.

Comment 9 Ulrich Walczak 2011-06-28 19:27:41 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. while loading telepathy
2.
3.

Comment 10 Ulrich Walczak 2011-07-02 16:24:40 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. while loading telepathy
2.
3.

Comment 11 Sailorleo 2011-08-17 09:37:19 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1. Unknown, sigfault occured in background.
2.
3.

Comment 12 erkan koyuncu 2011-09-04 10:06:28 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.someone send me a spam message
2.then the program gave a crash error
3.

Comment 13 Ulrich Walczak 2011-09-06 18:51:12 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.ni
2.
3.

Comment 14 erkan koyuncu 2011-09-09 09:46:26 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.i have started the empathy
2.I received the crash report
3.

Comment 15 Ulrich Walczak 2011-09-11 09:54:44 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.no idea
2.
3.

Comment 16 erkan koyuncu 2011-09-20 15:40:39 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.i have started the empathy
2.I received the crash report
3.

Comment 17 erkan koyuncu 2011-11-14 21:23:03 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: i686
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.i have started the empathy
2.I received the crash report
3.

Comment 18 Martin James Davidson 2011-11-15 08:20:17 UTC
(In reply to comment #5)
> Package: telepathy-logger-0.1.7-1.fc14
> Architecture: i686
> OS Release: Fedora release 14 (Laughlin)
> 
> 
> How to reproduce
> -----
> 1. Telepathy starts automatically
> 2. Usually, I switch it to off-line (oe invisible) mode.

I am using Fedora 15, now. (I do not use Empathy and I rarely take time to start up Pidgin.)

Comment 19 Daniel Lefebvre 2011-12-27 16:43:04 UTC
Package: telepathy-logger-0.1.7-1.fc14
Architecture: x86_64
OS Release: Fedora release 14 (Laughlin)


How to reproduce
-----
1.Crash was triggered durring boot up when program tried to launch
2.
3.

Comment 20 Fedora End Of Life 2012-08-16 12:14:45 UTC
This message is a notice that Fedora 14 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 14. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained.  At this time, all open bugs with a Fedora 'version'
of '14' have been closed as WONTFIX.

(Please note: Our normal process is to give advanced warning of this 
occurring, but we forgot to do that. A thousand apologies.)

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, feel free to reopen 
this bug and simply change the 'version' to a later Fedora version.

Bug Reporter: Thank you for reporting this issue and we are sorry that 
we were unable to fix it before Fedora 14 reached end of life. If you 
would still like to see this bug fixed and are able to reproduce it 
against a later version of Fedora, you are encouraged to click on 
"Clone This Bug" (top right of this page) and open it against that 
version of Fedora.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events.  Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

The process we are following is described here: 
http://fedoraproject.org/wiki/BugZappers/HouseKeeping