mission-control crashed with SIGSEGV in g_datalist_foreach()

Bug #399446 reported by Arnaud Faucher
270
This bug affects 4 people
Affects Status Importance Assigned to Milestone
telepathy-mission-control (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: telepathy-mission-control

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_foreach (datalist=0xaaaaaaaa,
     func=0x1c0f50 <tp_proxy_lose_interface>, user_data=0x9e87730)
     at /build/buildd/glib2.0-2.21.3/glib/gdataset.c:496
         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/telepathy/mission-control
NonfreeKernelModules: ndas_core nvidia
Package: telepathy-mission-control 4.67-3ubuntu1
ProcCmdline: /usr/lib/telepathy/mission-control
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 LANG=fr_CA.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-3.18-generic
SegvAnalysis:
 Segfault happened at: 0xa344c8 <g_datalist_foreach+40>: mov (%eax),%eax
 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-mission-control
StacktraceTop:
 IA__g_datalist_foreach (datalist=0xaaaaaaaa,
 tp_proxy_lose_interfaces (self=0x9e87730) at proxy.c:394
 tp_proxy_emit_invalidated (p=0x9e87730) at proxy.c:413
 tp_proxy_dispose (object=0x9e87730) at proxy.c:838
 tp_connection_dispose (object=0x9e87730) at connection.c:659
Title: mission-control crashed with SIGSEGV in g_datalist_foreach()
Uname: Linux 2.6.31-3-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Arnaud Faucher (arnaud-faucher) wrote :
visibility: private → public
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

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.
If you are using Kubuntu or Xubuntu you can file the crash using /usr/share/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.

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.

Changed in telepathy-mission-control (Ubuntu):
status: New → Invalid
Revision history for this message
Jamie Strandboge (jdstrand) wrote :

Marking Confirmed as others are seeing this issue and it was mistakenly invalidated.

Changed in telepathy-mission-control (Ubuntu):
status: Invalid → Confirmed
Revision history for this message
dino99 (9d9) wrote :

This version has died long ago; no more supported

Changed in telepathy-mission-control (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public Security information  
Everyone can see this security related information.

Other bug subscribers

Remote bug watches

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