mission-control crashed with SIGSEGV in g_datalist_foreach()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
telepathy-mission-control (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: telepathy-
While trying to change my status from Available to Offline.
This is possibly a security concern because the topmost function call on stacktrace receives an uninitialized pointer (0xaaaaaaaa).
#0 IA__g_datalist_
func=0x1c0f50 <tp_proxy_
at /build/
list = <value optimized out>
next = <value optimized out>
ProblemType: Crash
Architecture: i386
Date: Tue Jul 14 15:19:51 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/lib/
NonfreeKernelMo
Package: telepathy-
ProcCmdline: /usr/lib/
ProcCwd: /
ProcEnviron:
SHELL=/bin/bash
LANG=fr_CA.UTF-8
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0xa344c8 <g_datalist_
PC (0x00a344c8) ok
source "(%eax)" (0xaaaaaaaa) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-
StacktraceTop:
IA__g_
tp_proxy_
tp_proxy_
tp_proxy_dispose (object=0x9e87730) at proxy.c:838
tp_connection_
Title: mission-control crashed with SIGSEGV in g_datalist_
Uname: Linux 2.6.31-3-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
visibility: | private → public |
Thank you for taking the time to report this bug and helping to make Ubuntu better. However, your crash report is either missing or challenging to deal with as a ".crash" file. Please follow these instructions to have apport report a new bug about your crash that can be dealt with by the automatic retracer.
If you are running the Ubuntu Stable Release you might need to enable apport in /etc/default/apport and restart.
If you are using Ubuntu with the Gnome desktop environment - launch nautilus and navigate to your /var/crash directory and double click on the crash report you wish to submit. apport/ apport- qt --crash- file=/var/ crash/_ my_crash_ report. crash in a terminal - where _my_crash_ report. crash is the crash you would like to report.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/
I'm closing this bug report since the process outlined above will automatically open a new bug report which can then dealt with more efficiently. Thanks in advance for your cooperation and understanding.