compiz crashed with SIGSEGV in g_hash_table_iter_next()

Bug #750682 reported by Patrik Lundquist
90
This bug affects 16 people
Affects Status Importance Assigned to Milestone
Unity
Fix Released
Critical
Unassigned
unity (Ubuntu)
Fix Released
Critical
Unassigned

Bug Description

Binary package hint: unity

Switching window.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.8.2-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
CheckboxSubmission: 9f39854e610f4a6ac3758faa5e9c1555
CheckboxSystem: b845c366ea09c60efa3a45c1b5b21525
CrashCounter: 1
Date: Mon Apr 4 21:50:05 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f4c0dca5d5b <g_hash_table_iter_next+107>: cmpl $0x1,0x10(%r8)
 PC (0x7f4c0dca5d5b) ok
 source "$0x1" ok
 destination "0x10(%r8)" (0x3e800000010) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 g_hash_table_iter_next () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 LauncherEntryRemoteModel::on_dbus_name_owner_changed_signal_received(_GDBusConnection*, char const*, char const*, char const*, char const*, _GVariant*, void*) () from /usr/lib/compiz/libunityshell.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 g_main_context_dispatch () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: compiz crashed with SIGSEGV in g_hash_table_iter_next()
UpgradeStatus: Upgraded to natty on 2011-03-21 (14 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Patrik Lundquist (patrik-lundquist) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_hash_table_iter_next (iter=0x7fff6201a450, key=0x7fff6201a480, value=0x7fff6201a478) at /build/buildd/glib2.0-2.28.5/./glib/ghash.c:726
 LauncherEntryRemoteModel::on_dbus_name_owner_changed_signal_received (connection=<value optimized out>, sender_name=<value optimized out>, object_path=<value optimized out>, interface_name=<value optimized out>, signal_name=<value optimized out>, parameters=<value optimized out>, user_data=0x2053100) at /build/buildd/unity-3.8.2/src/LauncherEntryRemoteModel.cpp:351
 emit_signal_instance_in_idle_cb (data=0x7f4be80a1550) at /build/buildd/glib2.0-2.28.5/./gio/gdbusconnection.c:3400
 g_main_dispatch (context=0x1218ea0) at /build/buildd/glib2.0-2.28.5/./glib/gmain.c:2440
 g_main_context_dispatch (context=0x1218ea0) at /build/buildd/glib2.0-2.28.5/./glib/gmain.c:3013

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
visibility: private → public
Alex Launi (alexlauni)
Changed in unity:
status: New → Confirmed
importance: Undecided → Medium
Changed in unity (Ubuntu):
status: New → Confirmed
Changed in unity:
importance: Medium → Critical
Changed in unity (Ubuntu):
importance: Medium → Critical
Revision history for this message
Ryan Kitty (gothickitty93) wrote :

I just experienced this with Oneiric

tags: added: oneiric
Revision history for this message
Ryan Kitty (gothickitty93) wrote :

Oneiric on a i386 system

Revision history for this message
Christopher Kyle Horton (christhehorton) wrote :

Just got this bug on Oneiric after running unity --replace.

Jason Smith (jassmith)
Changed in unity:
status: Confirmed → Fix Committed
Changed in unity (Ubuntu):
status: Confirmed → Fix Committed
Omer Akram (om26er)
Changed in unity:
status: Fix Committed → Fix Released
Changed in unity (Ubuntu):
status: Fix Committed → Fix Released
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.