telepathy-logger crashed with SIGSEGV in _tpl_log_manager_add_message()

Bug #612308 reported by Kyrill
48
This bug affects 6 people
Affects Status Importance Assigned to Milestone
telepathy-logger (Ubuntu)
Expired
Medium
Unassigned

Bug Description

Binary package hint: telepathy-logger

telepathy-logger crashed with SIGSEGV in _tpl_log_manager_add_message()

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: telepathy-logger 0.1.4-1
ProcVersionSignature: Ubuntu 2.6.35-13.18-generic 2.6.35-rc6
Uname: Linux 2.6.35-13-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sun Aug 1 21:19:47 2010
ExecutablePath: /usr/lib/telepathy/telepathy-logger
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Alpha amd64 (20100630)
ProcCmdline: /usr/lib/telepathy/telepathy-logger
ProcEnviron:
 SHELL=/bin/bash
 LANG=ru_RU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f70a3524c23 <_tpl_log_manager_add_message+355>: mov 0x8(%rax),%r8
 PC (0x7f70a3524c23) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%r8" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-logger
StacktraceTop:
 _tpl_log_manager_add_message ()
 ?? () from /usr/lib/libtelepathy-logger.so.1
 ?? () from /usr/lib/libtelepathy-logger.so.1
 ?? () from /usr/lib/libtelepathy-logger.so.1
 ?? () from /usr/lib/libtelepathy-glib.so.0
Title: telepathy-logger crashed with SIGSEGV in _tpl_log_manager_add_message()
UserGroups: adm admin audio cdrom dialout dip fax fuse lpadmin netdev plugdev sambashare tape video

Revision history for this message
Kyrill (kirillshkrogalev) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 _tpl_log_manager_add_message (
 keepon_on_receiving_signal (
 on_received_signal_cb (proxy=<value optimized out>,
 got_message_pending_messages_cb (
 _tp_cli_dbus_properties_invoke_callback_get (

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in telepathy-logger (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Revision history for this message
Sebastien Bacher (seb128) wrote :

Could anybody try if that's still an issue in the current versions?

Changed in telepathy-logger (Ubuntu):
status: New → Incomplete
Revision history for this message
Launchpad Janitor (janitor) wrote :

[Expired for telepathy-logger (Ubuntu) because there has been no activity for 60 days.]

Changed in telepathy-logger (Ubuntu):
status: Incomplete → Expired
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.