compiz crashed with SIGSEGV in g_data_set_internal()

[Peter Eijlander]

peter@peter-Aspire-5720:~$ unity --replace
Checking if settings need to be migrated ...no
Checking if internal files need to be migrated ...no
Backend : gconf
Integration : true
Profile : unity
Adding plugins
Skipping upgrade com.canonical.unity.unity.01.upgrade
Skipping upgrade com.canonical.unity.unity.02.upgrade
Initializing core options...done
Initializing bailer options...done
Initializing detection options...done
Initializing composite options...done
Initializing opengl options...done
Initializing decor options...done
Initializing vpswitch options...done
Initializing grid options...done
Initializing gnomecompat options...done
Initializing place options...done
Initializing move options...done
Initializing snap options...done
Initializing mousepoll options...done
Initializing animation options...done
Initializing session options...done
Initializing workarounds options...done
compiz (core) - Error: Couldn't load plugin 'unitymtgrabhandles'
Initializing resize options...done
Initializing wall options...done
compiz (expo) - Warn: failed to bind image to texture
Initializing expo options...done
Initializing fade options...done
Initializing ezoom options...done
Initializing scale options...done

Screen geometry changed:
   0x0x1280x800

Initializing unityshell options...done
Starting unity-window-decorator
WARN 2012-01-23 14:58:24 glib.libindicator <unknown>:0 Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
WARN 2012-01-23 14:58:24 glib.libindicator <unknown>:0 Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
WARN 2012-01-23 14:58:24 glib.libindicator <unknown>:0 Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
WARN 2012-01-23 14:58:24 glib.libindicator <unknown>:0 Shortcut Group does not have key 'TargetEnvironment' falling back to deprecated use of 'OnlyShowIn' and 'NotShowIn'.
WARN 2012-01-23 14:58:24 glib <unknown>:0 Failed to fetch view type at /org/ayatana/bamf/window54525958: Method "ViewType" with signature "" on interface "org.ayatana.bamf.view" doesn't exist

WARN 2012-01-23 14:58:26 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method InfoRequest proxy /com/canonical/unity/lens/music does not exist
WARN 2012-01-23 14:58:26 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method SetViewType proxy /com/canonical/unity/lens/music does not exist
WARN 2012-01-23 14:58:26 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method InfoRequest proxy /com/canonical/unity/lens/files does not exist
WARN 2012-01-23 14:58:26 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method SetViewType proxy /com/canonical/unity/lens/files does not exist
Setting Update "main_menu_key"
Setting Update "run_key"
WARN 2012-01-23 14:58:28 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method InfoRequest proxy /com/canonical/unity/lens/applications does not exist
WARN 2012-01-23 14:58:28 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method SetViewType proxy /com/canonical/unity/lens/applications does not exist
WARN 2012-01-23 14:58:28 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method InfoRequest proxy /com/canonical/unity/lens/commands does not exist
WARN 2012-01-23 14:58:28 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method SetViewType proxy /com/canonical/unity/lens/commands does not exist
WARN 2012-01-23 14:59:24 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method InfoRequest proxy /com/canonical/unity/lens/applications does not exist
WARN 2012-01-23 14:59:24 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method SetViewType proxy /com/canonical/unity/lens/applications does not exist
WARN 2012-01-23 14:59:24 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method InfoRequest proxy /com/canonical/unity/lens/commands does not exist
WARN 2012-01-23 14:59:24 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method SetViewType proxy /com/canonical/unity/lens/commands does not exist
WARN 2012-01-23 14:59:24 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method InfoRequest proxy /com/canonical/unity/lens/files does not exist
WARN 2012-01-23 14:59:24 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method SetViewType proxy /com/canonical/unity/lens/files does not exist
WARN 2012-01-23 14:59:24 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method InfoRequest proxy /com/canonical/unity/lens/music does not exist
WARN 2012-01-23 14:59:24 unity.glib.dbusproxy GLibDBusProxy.cpp:257 Cannot call method SetViewType proxy /com/canonical/unity/lens/music does not exist
WARN 2012-01-23 14:59:25 unity.iconloader IconLoader.cpp:509 Unable to load contents of file:///usr/share/icons/unity-icon-theme/places/svg/category-installed.svg: Fout bij het openen van bestand: Bestand of map bestaat niet
WARN 2012-01-23 14:59:25 unity.iconloader IconLoader.cpp:509 Unable to load contents of file:///usr/share/icons/unity-icon-theme/places/svg/category-available.svg: Fout bij het openen van bestand: Bestand of map bestaat niet

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: libnux-2.0-0 2.0.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.2.0-10.17-generic 3.2.1
Uname: Linux 3.2.0-10-generic i686
ApportVersion: 1.91-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Mon Jan 23 15:05:12 2012
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: compiz --replace
SegvAnalysis:
 Segfault happened at: 0x1e8b64 <g_datalist_id_set_data_full+356>: mov 0x0(%ebp),%ecx
 PC (0x001e8b64) ok
 source "0x0(%ebp)" (0xaaaaaaa8) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: nux
StacktraceTop:
 g_datalist_id_set_data_full () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgtk-3.so.0
 ?? () from /usr/lib/libunity-misc.so.4
 g_object_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: compiz crashed with SIGSEGV in g_datalist_id_set_data_full()
UpgradeStatus: Upgraded to precise on 2012-01-22 (0 days ago)
UserGroups: adm admin audio cdrom dialout lpadmin plugdev pulse pulse-access sambashare video

[Apport retracing service (apport)]

StacktraceTop:
 g_data_set_internal (dataset=0x0, new_destroy_func=0, new_data=0x0, key_id=53, datalist=0x94ef2a8) at /build/buildd/glib2.0-2.31.10/./glib/gdataset.c:373
 g_datalist_id_set_data_full (datalist=0x94ef2a8, key_id=53, data=0x0, destroy_func=0) at /build/buildd/glib2.0-2.31.10/./glib/gdataset.c:680
 g_object_real_dispose (object=0x94ef2a0) at /build/buildd/glib2.0-2.31.10/./gobject/gobject.c:1001
 ?? ()
 ?? ()

[Peter Eijlander (peter-eijlander)]

This happened after using the terminal and typing unity --replace. here the output I captured in the terminal that stopped at what I pasted above. After that the keyboard became unusable, I had to log off and back on again to type this comment. The text capture was done using the mouse and the pull down menu in the terminal. I was trying to find out why "Supr+D" does not show the desktop and "Super+F" does not open the file manager. It seems that some shortcut keys that worked in the past are not yet implemented in Precise - I hope they will be restored in the relese version. People get used to these shortcuts...:-)

[Omer Akram (om26er)]

thanks for the bug report. unfortunately launchpad was not able to obtain a good stacktrace of the crash that you face. If its still a issue for you and is reproduce able could you please follow the instructions on https://wiki.ubuntu.com/Unity/FilingBugs#Getting_a_stack_trace and attach unity.log to this bug report?

[Robert Roth (evfool)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug #923780, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.