Comment 8 for bug 641335

On Mon, Sep 20, 2010 at 10:18:39AM -0000, Neil J. Patel wrote:
> @mdz Please do try with very latest unity, mutter and appmenu, as the
> fixes didrocks mentioned did touch precisely the code where your seeing
> the crash.

Which version of unity do you mean? I have confirmed the bug with
0.2.40-0ubuntu1 as Didier requested.

> Otherwise, if your running on an intel machine, starting unity from VT1
> like this would give us a chance of a backtrace:
> export DISPLAY=:0
> export UBUNTU_MENUPROXY=libappmenu.so
> gdb --args mutter --replace --mutter-plugins=libunity-mutter
> (gdb) r <enter>
>
> Then, switch to VT7 and, when it crashes, the screen should freeze and
> you can switch back to VT1 and hopefully get a trace. It's a pain to
> copy gdb traces off a VT, though, so having a camera handy is useful :)

I have a core dump, so I do have a backtrace. It just isn't very useful:

 #2 0x02d12e42 in abort () from /lib/libc.so.6
 #3 0x080920cc in meta_bug ()
 #4 0x0807a57f in ?? ()
 #5 0x010162c9 in _XError () from /usr/lib/libX11.so.6
 #6 0x0101d0de in _XReply () from /usr/lib/libX11.so.6
 #7 0x00ffa316 in XGetWindowProperty () from /usr/lib/libX11.so.6
 #8 0x098e05e4 in egg_xid_get_functions () from /usr/lib/indicators/3/libappmenu.so
[...]

i.e. it's dying because of the X error which you can see in the log.

I tried retracing the core file, but apport-retrace tells me that every one
of the -dbgsym packages are unavailable or incompatible for some reason.

--
 - mdz