Ubuntu
telepathy-mission-control-5 package

mission-control-5 crashed with signal 5 in g_object_newv()

Bug #930436 reported by steinhauser christian
38
This bug affects 7 people
Affects Status Importance Assigned to Milestone
telepathy-mission-control-5 (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

none

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-mission-control-5 1:5.10.1-1ubuntu5
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CrashCounter: 1
Date: Fri Feb 10 23:02:01 2012
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111129.1)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.2.0-15-generic root=UUID=4d3db0c9-a599-4f89-b937-3b75fc64791c ro quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=fr_FR:en
 LANG=fr_FR.UTF-8
Signal: 5
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_new () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: mission-control-5 crashed with signal 5 in g_object_newv()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
steinhauser christian (steinhauserchristian) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 g_cond_get_impl (cond=<optimized out>) at /build/buildd/glib2.0-2.31.16/./glib/gthread-posix.c:676
 ?? ()
 ?? ()

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 a useful symbolic stack trace). This
might be caused by some outdated packages which were installed on your system
at the time of the report:

debconf version 1.5.41ubuntu1 required, but 1.5.41ubuntu2 is available
libgcc1 version 1:4.6.2-12ubuntu1 required, but 1:4.6.2-14ubuntu1 is available
libglib2.0-0 version 2.31.16-0ubuntu1 required, but 2.31.16-0ubuntu2 is available
gcc-4.6-base version 4.6.2-12ubuntu1 required, but 4.6.2-14ubuntu1 is available
passwd version 1:4.1.4.2+svn3283-3ubuntu3 required, but 1:4.1.4.2+svn3283-3ubuntu4 is available

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
Revision history for this message
joosteto (joosteto) wrote :

Just installed 12.10, beta 2, and I'm getting this error.

Revision history for this message
joosteto (joosteto) wrote :

Just upgraded to 13.04, beta, and the first message I see after logging in is this error.

Revision history for this message
joosteto (joosteto) wrote :

Why was this bug marked as 'invalid'?
Ubuntu reported it every time I booted/logged in to 12.10; and again when I booted/logged in to 13.04 beta.
It is the reason i finnaly did

aptitude remove telepathy-mission-control-5

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

Other bug subscribers

Remote bug watches

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