compiz crashed with SIGSEGV in g_object_newv() from g_object_new() from g_volume_monitor_get() from unity::launcher::DeviceLauncherSection::DeviceLauncherSection() from unity::launcher::Controller::Impl::Impl()

Bug #984099 reported by GregLee
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Unity
Fix Released
High
Unassigned
unity (Ubuntu)
Fix Released
High
Unassigned

Bug Description

I was trying to log in to Unity 3D. I've crashed this way a number of times before -- it's repeatable. I've reported it several times. I've applied all updates to 12.04 as of 12 hours ago. Now, I'm logged in to KDE, since all Unity and all Gnome shells keep crashing.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.10.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Tue Apr 17 05:48:15 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.2)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: nux
StacktraceTop:
 ?? () from /usr/lib/gio/modules/libgioremote-volume-monitor.so
 g_object_newv () 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
 g_volume_monitor_get () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 unity::launcher::DeviceLauncherSection::DeviceLauncherSection() () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV 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
GregLee (greglee) wrote :
visibility: private → public
summary: - compiz crashed with SIGSEGV in g_object_newv()
+ compiz crashed with SIGSEGV in g_object_newv() from g_object_new() from
+ g_volume_monitor_get() from
+ unity::launcher::DeviceLauncherSection::DeviceLauncherSection() from
+ unity::launcher::Controller::Impl::Impl()
affects: nux (Ubuntu) → unity (Ubuntu)
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()

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):
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:

fontconfig version 2.8.0-3ubuntu8 required, but 2.8.0-3ubuntu9 is available
fontconfig-config version 2.8.0-3ubuntu8 required, but 2.8.0-3ubuntu9 is available
libpango1.0-0 version 1.30.0-0ubuntu1 required, but 1.30.0-0ubuntu2 is available
libfontconfig1 version 2.8.0-3ubuntu8 required, but 2.8.0-3ubuntu9 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
Andrea Azzarone (azzar1)
Changed in unity:
status: New → Incomplete
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

The stack trace is readable in comment #1.

Changed in unity:
status: Incomplete → New
Changed in unity (Ubuntu):
status: Invalid → New
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
Changed in unity (Ubuntu):
status: Confirmed → New
Changed in unity:
importance: Undecided → High
Changed in unity (Ubuntu):
importance: Undecided → High
Changed in unity:
status: New → In Progress
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
milestone: none → 5.12.0
Changed in unity (Ubuntu):
status: New → In Progress
assignee: nobody → Marco Trevisan (Treviño) (3v1n0)
Changed in unity:
status: In Progress → Confirmed
Changed in unity (Ubuntu):
assignee: Marco Trevisan (Treviño) (3v1n0) → nobody
Changed in unity:
assignee: Marco Trevisan (Treviño) (3v1n0) → nobody
Changed in unity (Ubuntu):
status: In Progress → Confirmed
Changed in unity (Ubuntu):
status: Confirmed → Triaged
Changed in unity:
milestone: 5.12.0 → 5.14.0
Changed in unity:
milestone: 5.14.0 → 5.16.0
Changed in unity:
milestone: 5.16.0 → 5.18.0
Changed in unity:
milestone: 5.18.0 → 7.0.0
Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.0.0 → 7.0.1
Changed in unity:
milestone: 7.0.1 → 7.3.1
Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.3.1 → 7.3.2
Stephen M. Webb (bregma)
Changed in unity:
milestone: 7.3.2 → 7.3.3
Revision history for this message
Christopher Townsend (townsend) wrote :

This is a rather old bug and the crash has not been reported in a very log time. It seems this has been fixed some releases ago and as such, marking Fix Released.

If it does still occur, then we can either reopen this bug or open a new one.

no longer affects: unity/5.0
no longer affects: unity/6.0
Changed in unity:
status: Confirmed → Fix Released
milestone: 7.3.3 → none
Changed in unity (Ubuntu):
status: Triaged → Fix Released
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.