mission-control-5 crashed with SIGSEGV in tp_strdiff()

Bug #543414 reported by Alwin Garside
98
This bug affects 20 people
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
Invalid
Undecided
Unassigned

Bug Description

Binary package hint: telepathy-mission-control-5

It just crashed.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Mar 21 11:40:43 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100224.1)
Package: telepathy-mission-control-5 5.3.2-2
ProcCmdline: /usr/lib/telepathy/mission-control-5
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=nl_NL.utf8
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x7f13407d6058: movdqa (%rsi),%xmm1
 PC (0x7f13407d6058) ok
 source "(%rsi)" (0x7275636573207370) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 ?? () from /lib/libc.so.6
 tp_strdiff () from /usr/lib/libtelepathy-glib.so.0
 tp_connection_manager_protocol_get_param ()
 ?? ()
 ?? ()
Title: mission-control-5 crashed with SIGSEGV in tp_strdiff()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Alwin Garside (yogarine) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 __strcmp_ssse3 ()
 tp_g_signal_connect_object (instance=0x0,
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? ()
 ?? ()

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-mission-control-5 (Ubuntu):
status: New → Invalid
Revision history for this message
Apport retracing service (apport) wrote : Crash report cannot be processed

Thank you for your report!

However, processing it in order to get sufficient information for the
developers failed (it does not generate an useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

libgcc1: installed version 1:4.4.3-3ubuntu3, latest version: 1:4.4.3-4ubuntu5
libdbus-1-3: installed version 1.2.16-2ubuntu3, latest version: 1.2.16-2ubuntu4
libgnome-keyring0: installed version 2.29.4git20100224-0ubuntu2, latest version: 2.30.0-0ubuntu1
gcc-4.4-base: installed version 4.4.3-3ubuntu3, latest version: 4.4.3-4ubuntu5
libc-bin: installed version 2.11.1-0ubuntu4, latest version: 2.11.1-0ubuntu5
tzdata: installed version 2010e-1, latest version: 2010g-0ubuntu1
libtelepathy-glib0: installed version 0.10.0-1, latest version: 0.10.1-1
libc6: installed version 2.11.1-0ubuntu4, latest version: 2.11.1-0ubuntu5
libstdc++6: installed version 4.4.3-3ubuntu3, latest version: 4.4.3-4ubuntu5
libglib2.0-0: installed version 2.23.5-1ubuntu3, latest version: 2.24.0-0ubuntu1

Please upgrade your system to the latest package versions. If you still
encounter the crash, please file a new report.

Thank you for your understanding, and sorry for the inconvenience!

tags: removed: need-amd64-retrace
Changed in telepathy-mission-control-5 (Ubuntu):
status: Invalid → New
Revision history for this message
alejandro gonzález (ale-g-gonzalez) wrote :

This also affect me, and I have all the updates published today (04-14) installed

tags: removed: amd64
Revision history for this message
dino99 (9d9) wrote :

This version is outdated and no more supported

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

Other bug subscribers

Remote bug watches

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