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

[Daniel Winzen]

I don't know when or why this happened, this error-message was in the background, so for a long time not noticed by me.

ProblemType: Crash
DistroRelease: Ubuntu 13.04
Package: telepathy-mission-control-5 1:5.14.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.8.0-7.15-generic 3.8.0
Uname: Linux 3.8.0-7-generic x86_64
ApportVersion: 2.8-0ubuntu4
Architecture: amd64
Date: Thu Feb 21 22:31:18 2013
ExecutablePath: /usr/lib/telepathy/mission-control-5
InstallationDate: Installed on 2012-04-03 (326 days ago)
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120403)
KernLog:

MarkForUpload: True
ProcAttrCurrent: /usr/lib/telepathy/mission-control-5 (enforce)
ProcCmdline: BOOT_IMAGE=/boot/vmlinuz-3.8.0-7-generic root=UUID=0A320B17320B0781 loop=/hostname/disks/root.disk ro quiet splash vt.handoff=7
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 TERM=xterm
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f997de7f320 <g_slist_find+16>: cmp %rsi,(%rax)
 PC (0x7f997de7f320) ok
 source "%rsi" ok
 destination "(%rax)" (0x00000040) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: telepathy-mission-control-5
StacktraceTop:
 g_slist_find () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libdbus-glib-1.so.2
 g_object_newv () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: mission-control-5 crashed with SIGSEGV in g_slist_find()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:

[Apport retracing service (apport)]

StacktraceTop:
 g_slist_find (list=0x40, data=data@entry=0x207a4f0) at /build/buildd/glib2.0-2.35.8/./glib/gslist.c:727
 g_object_notify_queue_add (nqueue=nqueue@entry=0x2067130, pspec=0x207a4f0, object=<optimized out>) at /build/buildd/glib2.0-2.35.8/./gobject/gobject.c:305
 object_set_property (nqueue=0x2067130, value=0x205e1f8, pspec=0x207a4f0, object=0x2064350) at /build/buildd/glib2.0-2.35.8/./gobject/gobject.c:1363
 g_object_constructor (type=<optimized out>, n_construct_properties=<optimized out>, construct_params=<optimized out>) at /build/buildd/glib2.0-2.35.8/./gobject/gobject.c:1869
 dbus_g_proxy_manager_register (manager=0x2059af0, proxy=0x2059af0) at dbus-gproxy.c:1002

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Ivan Mikushin (i-mikushin)]

I'm having this on gnome-shell reload.

[Kam Pow (kampowchicken)]

Happened to me after I logged out and logged back in. It happened multiple times already.

[HaruSiga77 (tolkien-world)]

I have gnome shell too, but I use the kernel 3.9rc4.

[Dallman Ross (spamless)]

I logged in and noticed my computer clock was two hours behind, so I went in to Date/Time and updated it. When I tried to close the Date/Time applet, the crash pop-up screen displayed itself.

[Patrik Lundquist (patrik-lundquist)]

It is obviously not fixed since the last uploaded release 1:5.14.0-0ubuntu1 is from 2013-01-10.

[BenginM (sary)]

this occur after a login attempt :, gnome-shell 3.8 enabled from gnome3 ppa :

sary@n1x:~$ lsb_release -rda; uname -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu Raring Ringtail (development branch)
Release: 13.04
Codename: raring
Linux n1x 3.8.0-17-generic #27-Ubuntu SMP Sun Apr 7 19:39:35 UTC 2013 x86_64 x86_64 x86_64 GNU/Linux
sary@n1x:~$

sary@n1x:~$ apt-cache policy gnome-shell
gnome-shell:
  Installed: 3.8.0.1-0ubuntu1+js17~raring3.1
  Candidate: 3.8.0.1-0ubuntu1+js17~raring3.1
  Version table:
 *** 3.8.0.1-0ubuntu1+js17~raring3.1 0
        500 http://ppa.launchpad.net/gnome3-team/gnome3-staging/ubuntu/ raring/main amd64 Packages
        100 /var/lib/dpkg/status
     3.8.0.1-0ubuntu1+js17~raring3 0
        500 http://ppa.launchpad.net/gnome3-team/gnome3/ubuntu/ raring/main amd64 Packages
     3.6.3.1-0ubuntu4 0
        500 http://sa.archive.ubuntu.com/ubuntu/ raring/universe amd64 Packages
sary@n1x:~$

[Michael Sparmann (theseven)]

Does not appear to be fixed in the official repositories yet, despite being in "Fix Released" state since more than 6 weeks?

[Nils Toedtmann (m-launchpad-net-mail-nils-toedtmann-net)]

It's not fixed for me either. Fully patched 13.04 with Gnome 3.8 from PPA. Seems to only happen when starting gnome shell, not in Unity.

[Jonathan (jonathan-uxbr)]

Also not fixed for me on fully patched Ubuntu 13.04 running gnome shell as packaged by the gnome team (ubuntu-gnome).

[martyfelker (martyfelker-gmail)]

Happened to me using Ubuntu 13.01 kernel 3.10. Obviously has not been fixed for some time.

[kai (kkrapu)]

Happens to me lately upon log in. I'm using gnome 3.8 from the gnome team ppa. It's been fine for weeks, but last few days I've had this crash. Didn't do any changes to the system that I can recall, might have been there was some updates after which it started happening, but I'm not sure about that.

[Jiří Podvolecký (jiripodvolecky)]

Styl in 13.10

[HamilJF (john-hamilton)]

Not fixed for me either... ran a full set of updates last night and sent off an automated error message this morning. Running 13.04 on an AMD64, Unity shell (but who knows what is going on in the background). How do we get the status to 'unfixed' ?

[Eric Morgan (gemorgan)]

This bug has been bothering me for 2 Ubuntu versions now and over a year... :( Every single time I boot and log in.

[Yann Simon (yann-simon-fr)]

Not fixed for me neither...

[RJP Computing (rpusztai)]

Not fixed for me either. It happens when rebooting or logging out and then back in as well.

[Cengizhan Yücel (cengizhan.yuecel)]

I R also affected for many months, still not fixed. :o(