compiz crashed with SIGABRT in raise()

StacktraceTop:
 raise (sig=6) at ../nptl/sysdeps/unix/sysv/linux/raise.c:64
 abort () at abort.c:92
 g_assertion_message (domain=<value optimized out>, file=<value optimized out>, line=<value optimized out>, func=0x7ff2dd324730 "g_variant_type_info_check", message=0x2ac0140 "assertion failed: (0 <= index && index < 24)") at /build/buildd/glib2.0-2.28.4/./glib/gtestutils.c:1358
 g_assertion_message_expr (domain=0x7ff2dd2da646 "GLib", file=0x7ff2dd3243b0 "/build/buildd/glib2.0-2.28.4/./glib/gvarianttypeinfo.c", line=186, func=0x7ff2dd324730 "g_variant_type_info_check", expr=<value optimized out>) at /build/buildd/glib2.0-2.28.4/./glib/gtestutils.c:1369
 g_variant_type_info_check (info=<value optimized out>, container_class=<value optimized out>) at /build/buildd/glib2.0-2.28.4/./glib/gvarianttypeinfo.c:186

A work around is:

1. When the screen freeze and you can't do anything (just move your mouse)
2. Hit CTRL+ALT+F2
3. $ pkill compiz
3. Hit CTRL+ALT+F7
4. Wait compiz reload :)

Occurs for me on login before opening any windows at all.

The suggested work around does not work here. After a few seconds it starts happening again. I've done both
compiz --replace' and 'unity --reset' and while both can 'fix' it for a few moments, the buggy behavior returns quickly. compiz and therefore unity are completely unusable atm. unity-2d works ok as a workaround.

#5 is a valid workaround if compiz is working (for the most part) and just happened to have a one-off crash that took away unity and all window decorations. Coming up with a solution to get your desktop back without restarting the computer or even GDM isn't that obvious.

Unfortunately, SIGABRT in raise() is a very general bug. We (the end users) aren't seeing why (0 <= index && index < 24). There could be multiple fronts causing index to go out of range, leaving compiz in varying states for different people.

An example I just noticed is that there isn't a line about the nvidia kernel module in the submitter's report. All bug reports I file mention the nvidia kernel module. With that very limited information, I would assume that Jamie and the bug submitter are using one of the built-in open-source 3D drivers (nv, r[nnn]g, intel) while Thiago and I are using nvidia (or fglrx). But that's going off very limited information so I very well could be wrong. Then again, I just used that as an example of what I meant by multiple fronts.

Is there anything I can do and/or provide to help with more information about this bug?

bug #741908 (a duplicate of this one) has the information on my hardware, which is intel.

I cannot reproduce this bug. I am using Unity from trunk. Is someone constantly reproducing this bug?

Jay, I am the reporter, I see this constantly and Unity is now completely unusable for me (I have to use unity-2d). All I have to do is login and start opening applications and very quickly this bug occurs. I gave a reduced reproducer for my hardware in my initial report (as previously mentioned, apport-collected hardware info is in duplicate bug #741908). I have:
nux 0.9.36-0ubuntu1
compiz 1:0.9.4git20110322-0ubuntu5
unity 3.6.8-0ubuntu3

I am not sure why the bug is now marked Incomplete....

@Jay: you can't reproduce every crashers, however please don't set them incomplete when it has been reported against latest version in Natty with all the stacktrace info beeing there.

Thanks for the fixes! Not sure when these fixes will hit natty, but I'd be happy to test patches against what is (or will be) in natty if that would be helpful. I'm also fine with waiting for them to hit the archive. Thanks again, it'll be great to have my desktop back. :)

They should land tomorrow, Jamie, look forward to hearing back from you
then!

This bug was fixed in the package nux - 0.9.38-0ubuntu1

---------------
nux (0.9.38-0ubuntu1) natty; urgency=low

  * New upstream release.
    - compiz crashed with SIGSEGV in std::_List_node_base::_M_hook()
      (LP: #711916)
    - compiz crashed with SIGSEGV in nux::View::PostProcessEvent2()
      (LP: #712498)
    - compiz crashed with SIGSEGV in sigc::internal::signal_emit0<void,
      sigc::nil>::emit() (LP: #729715)
    - compiz crashed with SIGSEGV in brw_validate_state() (LP: #730707)
    - Finish Nux detection tool support (LP: #722089)
    - compiz crashed with SIGABRT in raise() (LP: #741942)
    - compiz crashed with SIGSEGV in PanelMenuView::ProcessEvent()
      (LP: #742139)
    - compiz crashed with SIGSEGV in operator->() (LP: #741961)
    - Graphics hardware capability detection (LP: #685208)
    - compiz crashed with SIGSEGV in nux::GraphicsDisplay::GrabPointer()
      (LP: #740784)
    - compiz crashed with SIGSEGV in nux::Area::InitiateResizeLayout()
      (LP: #741977)
    - compiz crashed with SIGSEGV in nux::GraphicsDisplay::GrabKeyboard()
      (LP: #742233)
    - Missing child addition signals on nux::Layout and nux::View
      (LP: #734803)
    - compiz crashed with SIGSEGV in
      nux::GpuRenderStates::SubmitChangeStates() (LP: #735908)
    - unity_support_test crashed with SIGSEGV (LP: #743848)
  * debian/control:
    - adding libpci-dev build-dep for the new lighter unity_support_tool
 -- Didier Roche <email address hidden> Fri, 01 Apr 2011 11:15:39 +0200

FYI-- this seems to be fixed now with the latest updates. Thanks again! :)

On 05/04/11 18:42, Jamie Strandboge wrote:
> FYI-- this seems to be fixed now with the latest updates. Thanks again!
> :)

Good man, thanks for circling back :-) New updates tomorrow, test for a
regression ;-)