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:~$
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to telepathy-mission-control-5 in Ubuntu.
https://bugs.launchpad.net/bugs/1132555
Title:
mission-control-5 crashed with SIGSEGV in g_slist_find()
Status in “telepathy-mission-control-5” package in Ubuntu:
Fix Released
Bug description:
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:
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/telepathy-mission-control-5/+bug/1132555/+subscriptions
--
Mailing list: https://launchpad.net/~desktop-packages
Post to : desktop-packages@lists.launchpad.net
Unsubscribe : https://launchpad.net/~desktop-packages
More help : https://help.launchpad.net/ListHelp
