unity-2d-launcher crashed with SIGABRT in raise()

[Lukas Koranda]

Binary package hint: unity-2d

unity-2d is crashing very often e.g. after login or when I am rolling over panel with cursor

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity-2d-launcher 3.6.2-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.38-7.36-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Mon Mar 21 14:49:36 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/unity-2d-launcher
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110317)
ProcCmdline: unity-2d-launcher
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
Signal: 6
SourcePackage: unity-2d
StacktraceTop:
 raise () from /lib/x86_64-linux-gnu/libc.so.6
 abort () from /lib/x86_64-linux-gnu/libc.so.6
 g_assertion_message () from /lib/libglib-2.0.so.0
 g_assertion_message_expr () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgio-2.0.so.0
Title: unity-2d-launcher crashed with SIGABRT in raise()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare tape video
XsessionErrors: (nautilus:2941): GConf-CRITICAL **: gconf_value_free: assertion `value != NULL' failed

[Kate Stewart (kate.stewart)]

Can someone confirm this bug is still present?

[Tobin Davis (gruemaster)]

I am unable to reproduce this on either armel or my x86_64 netbook since 3.8.4 release. I have been doing extensive testing daily, and have not had this issue since Beta 2 release.

marking as invalid.

[cespinal (cespinal17)]

As for today, I keep experiencing random crashes in both Unity 3d and 3d. It gets to a point where using the computer is practically impossible.

[Olivier Tilloy (osomon)]

@cespinal: did you mean "Unity 2d and 3d"?

Also, when those crashes happen, could you take the time to report them through apport, the automatic crash reporting tool that should be popping up? That would be extremely useful. Thanks!

[David Barth (dbarth)]

It doesn't sound like an active bug, nor is there a reproducible way to demonstrate the issue. Marking as invalid