telepathy-salut crashed with SIGSEGV in free()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-salut |
Invalid
|
Medium
|
|||
telepathy-salut (Ubuntu) |
Invalid
|
Medium
|
Unassigned |
Bug Description
Binary package hint: telepathy-salut
Reboot PC and open apport with crash
ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: telepathy-salut 0.3.11-1
ProcVersionSign
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Tue Apr 6 22:23:32 2010
ExecutablePath: /usr/lib/
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
ProcCmdline: /usr/lib/
ProcEnviron:
SHELL=/bin/bash
LANG=es_CL.utf8
SegvAnalysis:
Segfault happened at: 0x6f689a: mov 0x4(%esi),%eax
PC (0x006f689a) ok
source "0x4(%esi)" (0x00000005) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-salut
StacktraceTop:
?? () from /lib/tls/
?? () from /lib/tls/
free () from /lib/tls/
dbus_free () from /lib/libdbus-1.so.3
?? () from /lib/libdbus-1.so.3
Title: telepathy-salut crashed with SIGSEGV in free()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
visibility: | private → public |
Changed in telepathy-salut: | |
importance: | Unknown → Medium |
status: | Unknown → Invalid |
Changed in telepathy-salut (Ubuntu): | |
assignee: | nobody → Wuilmer Bolívar (elwuilmer) |
Changed in telepathy-salut (Ubuntu): | |
assignee: | Wuilmer Bolívar (elwuilmer) → nobody |
Changed in telepathy-salut: | |
importance: | Medium → Unknown |
Changed in telepathy-salut: | |
importance: | Unknown → Medium |
This backtrace isn't useful without debug symbols, and Launchpad won't let me access the bug. As I understand it, Launchpad will automatically produce a more informative backtrace after a while? Please provide that when it appears.