compiz crashed with SIGSEGV in g_data_set_internal()

Bug #924198 reported by Alan Pope 🍺🐧🐱 🦄
34
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Nux
Won't Fix
Undecided
Unassigned
Unity
Won't Fix
Undecided
Unassigned
nux (Ubuntu)
Won't Fix
Critical
Unassigned
Nominated for Precise by Alberto Salvia Novella
unity (Ubuntu)
Won't Fix
Critical
Unassigned
Nominated for Precise by Alberto Salvia Novella

Bug Description

Plugged HDMI cable into machine already running precise. Opened display settings and ticked 'mirror'. Compiz crashed.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-12.20-generic 3.2.2
Uname: Linux 3.2.0-12-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Tue Jan 31 09:10:59 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120102)
ProcCmdline: compiz
SegvAnalysis:
 Segfault happened at: 0x7f4eb1938b55 <g_datalist_id_set_data_full+341>: mov 0x0(%r13),%esi
 PC (0x7f4eb1938b55) ok
 source "0x0(%r13)" (0xaaaaaaaaaaaaaaa8) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 g_datalist_id_set_data_full () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 unity::PanelTray::~PanelTray() () from /usr/lib/compiz/libunityshell.so
 unity::PanelTray::~PanelTray() () from /usr/lib/compiz/libunityshell.so
Title: compiz crashed with SIGSEGV in g_datalist_id_set_data_full()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Alan Pope 🍺🐧🐱 🦄 (popey) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_data_set_internal (dataset=0x0, new_destroy_func=0, new_data=0x0, key_id=53, datalist=0xa91a30) at /build/buildd/glib2.0-2.31.12/./glib/gdataset.c:373
 g_datalist_id_set_data_full (datalist=0xa91a30, key_id=53, data=0x0, destroy_func=0) at /build/buildd/glib2.0-2.31.12/./glib/gdataset.c:680
 g_object_real_dispose (object=0xa91a20) at /build/buildd/glib2.0-2.31.12/./gobject/gobject.c:1001
 g_object_unref (_object=0xa91a20) at /build/buildd/glib2.0-2.31.12/./gobject/gobject.c:2971
 unity::ui::KeyboardUtil::GetAbsoluteKeyBounds (this=<optimized out>, key=0x2, row=0x8, section=0x2, geo=<optimized out>) at /build/buildd/unity-5.0.0/plugins/unityshell/src/KeyboardUtil.cpp:117

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 nux (Ubuntu):
importance: Undecided → Medium
summary: - compiz crashed with SIGSEGV in g_datalist_id_set_data_full()
+ compiz crashed with SIGSEGV in g_data_set_internal()
tags: removed: need-amd64-retrace
Changed in nux (Ubuntu):
importance: Medium → Critical
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in nux (Ubuntu):
status: New → Confirmed
visibility: private → public
Revision history for this message
Omer Akram (om26er) wrote :

This bug was reported on a development snapshot of Unity but lacks elements for it to be actionable:
- there seems to be no reports of further occurences of the issue
- the bug cannot be reproduced reliably
- the information provided is not sufficient to track down the issue to a particular programming error.
Could you please check if this issue is present in the current version, and if it is reopen the bug to a NEW status.

Revision history for this message
Omer Akram (om26er) wrote :

sorry wrong comment for the bug.

Omer Akram (om26er)
Changed in unity:
status: New → Confirmed
Changed in nux:
status: New → Confirmed
Changed in unity (Ubuntu):
status: New → Confirmed
Changed in unity (Ubuntu):
importance: Undecided → Critical
Changed in nux (Ubuntu):
status: Confirmed → Triaged
Changed in unity (Ubuntu):
status: Confirmed → Triaged
Changed in nux:
status: Confirmed → Opinion
Revision history for this message
Will Cooke (willcooke) wrote :

As part of the big bug clear up for 16.04 LTS I am marking this bug as Wont Fix.
These types of crasher are better handled by errors.ubutnu.com which can collate similar crash reports to help us identify persitent bugs rather than one-off crashes.
Sorry we are not able to help with this specific issue. If you are still experiencing this crash, please re-open the bug and add the tag "desktop-bugscrub-reopened". See https://wiki.ubuntu.com/BigDesktopBugScrub for more information.

Changed in unity (Ubuntu):
status: Triaged → Won't Fix
tags: added: desktop-bugscrub-autoclosed
Changed in nux:
status: Opinion → Won't Fix
Changed in nux (Ubuntu):
status: Triaged → Won't Fix
Changed in unity:
status: Confirmed → Won't Fix
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.