compiz crashed with SIGSEGV in g_type_check_instance_is_a() from unity::launcher::BamfLauncherIcon::UpdateIconGeometries() from unity::launcher::BamfLauncherIcon::UpdateDesktopQuickList()

Bug #1096457 reported by Colan Schwartz
44
This bug affects 7 people
Affects Status Importance Assigned to Milestone
System76
Invalid
Undecided
Unassigned
Unity
Invalid
High
Unassigned
5.0
Invalid
Medium
Unassigned
6.0
Invalid
Medium
Unassigned
unity (Ubuntu)
Invalid
High
Unassigned
Nominated for Precise by Stephen M. Webb
Nominated for Quantal by Stephen M. Webb

Bug Description

These types of crashes usually happen shortly after logging in, but in this case, it happened much later. Crashing early doesn't seem to happen with debugging info turned on, as it was for this issue.

For more details on this type of crash, please see bug #750386.

WORKAROUND: For some of us, this is caused by a corrupt .config/dconf/user file in our home directories. Try removing this file, and report back. Be warned, however, that by removing this file, you will lose many of your desktop environment configuration settings. If this is a concern, rename it and keep it around in case contents of the file are salvageable.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: unity 6.12.0-0ubuntu0.2
ProcVersionSignature: Ubuntu 3.5.0-21.32-generic 3.5.7.1
Uname: Linux 3.5.0-21-generic x86_64
ApportVersion: 2.6.1-0ubuntu9
Architecture: amd64
CrashCounter: 1
Date: Sat Jan 5 16:05:46 2013
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
InstallationDate: Installed on 2010-10-11 (817 days ago)
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MarkForUpload: True
ProcCmdline: compiz --replace
ProcEnviron:
 TERM=linux
 PATH=(custom, user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_CA.UTF-8
 SHELL=/bin/zsh
SegvAnalysis:
 Segfault happened at: 0x7f5669ac469c <g_type_check_instance_is_a+60>: testb $0x4,0x16(%rdi)
 PC (0x7f5669ac469c) ok
 source "$0x4" ok
 destination "0x16(%rdi)" (0x567006f73980046) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 g_type_check_instance_is_a () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 unity::launcher::BamfLauncherIcon::UpdateIconGeometries(std::vector<nux::Point3D<float>, std::allocator<nux::Point3D<float> > >) () from /usr/lib/compiz/libunityshell.so
 unity::launcher::BamfLauncherIcon::UpdateDesktopQuickList() () from /usr/lib/compiz/libunityshell.so
 ?? ()
Title: compiz crashed with SIGSEGV in g_type_check_instance_is_a()
UpgradeStatus: Upgraded to quantal on 2012-10-27 (69 days ago)
UserGroups: adm admin cdrom dialout lp lpadmin netdev plugdev sambashare whoopsie

Revision history for this message
Colan Schwartz (colan) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceSource:
 #0 0x00007f5669ac469c in g_type_check_instance_is_a (type_instance=<optimized out>, iface_type=<optimized out>) at /build/buildd/glib2.0-2.34.1/./gobject/gtype.c:3964
   [Error: /build/buildd/glib2.0-2.34.1/./gobject/gtype.c was not found in source tree]
 #1 0x00007f565bc713d6 in unity::launcher::BamfLauncherIcon::UpdateIconGeometries(std::vector<nux::Point3D<float>, std::allocator<nux::Point3D<float> > >) () from /tmp/apport_sandbox_Bj6or7/usr/lib/compiz/libunityshell.so
 #2 0x00007f565bc72002 in unity::launcher::BamfLauncherIcon::UpdateDesktopQuickList() () from /tmp/apport_sandbox_Bj6or7/usr/lib/compiz/libunityshell.so
 #3 0x0000000000000000 in ?? ()
StacktraceTop:
 g_type_check_instance_is_a (type_instance=<optimized out>, iface_type=<optimized out>) at /build/buildd/glib2.0-2.34.1/./gobject/gtype.c:3964
 unity::launcher::BamfLauncherIcon::UpdateIconGeometries(std::vector<nux::Point3D<float>, std::allocator<nux::Point3D<float> > >) () from /tmp/apport_sandbox_Bj6or7/usr/lib/compiz/libunityshell.so
 unity::launcher::BamfLauncherIcon::UpdateDesktopQuickList() () from /tmp/apport_sandbox_Bj6or7/usr/lib/compiz/libunityshell.so
 ?? ()

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 unity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
summary: - compiz crashed with SIGSEGV in g_type_check_instance_is_a()
+ compiz crashed with SIGSEGV in g_type_check_instance_is_a() from
+ unity::launcher::BamfLauncherIcon::UpdateIconGeometries() from
+ unity::launcher::BamfLauncherIcon::UpdateDesktopQuickList()
information type: Private → Public
Changed in unity:
importance: Undecided → Medium
Revision history for this message
Andrea Azzarone (azzar1) wrote :

The stackstrace is incomplete.

Changed in unity:
status: New → Incomplete
Changed in unity (Ubuntu):
status: New → Incomplete
Revision history for this message
Colan Schwartz (colan) wrote :

I doubt I still have the data around, but what else would be required here? I followed Daniel's instructions. The problem is that when run that way, it's unlikely that it will actually crash. I've only been able to do this the one time.

Changed in unity (Ubuntu):
status: Incomplete → New
Changed in unity:
status: Incomplete → New
Changed in unity:
importance: Medium → High
Changed in unity (Ubuntu):
importance: Medium → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in unity (Ubuntu):
status: New → Confirmed
Revision history for this message
Jorge Juan (jjchico) wrote :

Comming from bug #750386.

Most times I open a session unity crashes inmediatly or after running the first application. "unity --replace" run from the console (Alt-F1) will solve it up to the next session start. When unity is run this way the crash is very unlikely. I am trying tu run unity as Daniel suggested in the old bug:

env MALLOC_CHECK_=3 G_SLICE=always-malloc unity --replace

but I think the idea is to run this right at the place unity is launched at the session start. Do you know which script/config file runs unity in the first place?

Revision history for this message
Colan Schwartz (colan) wrote :

Also reporting against System76 as I got this on my Lemur UltraThin (lemu2).

Revision history for this message
Joey Stanford (joey) wrote :

I get this as well.

This only happens when Unity with Compiz is running. It doesn't happen when I use gnome-shell, KDE, XFCE, and LXDE.

Revision history for this message
Joey Stanford (joey) wrote :

I've run unity --debug with this and I get the following additional errors:

(hand typed since I can't copy & paste it)

nux.gestures_subscription GesturesSubsription.cpp:364
Failed to set Geis subscription configuration com.canonical.oif.rotate.timeout

I get that repeated about 100 times.

Revision history for this message
Joey Stanford (joey) wrote :

The other error I seem to be getting is

unity <unknown>:0 Unable to fetch children: No such interface 'org.ayatana.bamf.view' on object path /org/ayatana/bamf/application0x2482ea0

Revision history for this message
Joey Stanford (joey) wrote :

I should also note that I was able to fix this on my system76 machine with a complete format and reinstall. The above items are appearing on my zareason box. So this is certainly not vendor dependent.

Revision history for this message
Joey Stanford (joey) wrote :

Sorry for the spam but I'm diagnosing this between desktop crashes.

Another piece from unity --debug...

Despite having an Nvidia GeForce 9400 GT (driver 304.51) I see that unity is claiming I'm unsuported and forcing me to opengl.

I then get an error of

/usr/bin/compiz (opengl) - Error: FBO is incomplete: GL::FRAMEBUFFER_UNSUPPORTED (0x8cdd)

I'm using the default (auto) kernel FB and I can run other desktops just fine. Nvidia settings doesn't seem to have a problem.

Revision history for this message
Joey Stanford (joey) wrote :

For the record I've also done a unity --distro before attempting unity --debug

Revision history for this message
Joey Stanford (joey) wrote :

I'm also seeing several lines of

Stream error: Too large

Revision history for this message
Joey Stanford (joey) wrote :

I spent some time troubleshooting with Canonical support and while I still have this problem I was able to lesson it's probability of occurrence slightly.

I've done:
* unity --distro
* unity --reset-icons
* used jocket-text to list and purge all active NVIDIA drivers
* used apt-get to purge any lingering NVIDIA items
* used .xsession-errors to resolve a number of start-up issues

Revision history for this message
Joey Stanford (joey) wrote :
Revision history for this message
Joey Stanford (joey) wrote :
Revision history for this message
Joey Stanford (joey) wrote :

fyi, I fixed this by removing .config/dconf/user

Revision history for this message
Colan Schwartz (colan) wrote :

@Joey: Thanks so much for digging into this. I'm confirming that it worked for me as well. I updated the ticket description.

description: updated
Colan Schwartz (colan)
description: updated
Revision history for this message
Jorge Juan (jjchico) wrote :

Removing .config/dconf/user also worked for me (so far).

Revision history for this message
Ian Santopietro (isantop) wrote :

Since this isn't a System76-specific issue, I'm marking this Invalid against System76.

Changed in system76:
status: New → Invalid
Stephen M. Webb (bregma)
no longer affects: unity
Changed in unity:
importance: Undecided → High
status: New → Confirmed
Revision history for this message
Will Cooke (willcooke) wrote :

Sorry folks, but as part of the bug clean up ahead of 16.04 I'm marking this as invalid because it affects an Ubuntu release which is now unsupported. If you can still recreate this bug in a supported release please do open a new bug and we can triage it for consideration in the 16.04 development cycle.

Changed in unity:
status: Confirmed → Invalid
Changed in unity (Ubuntu):
status: Confirmed → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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