Comment 2 for bug 709754

I got this crasher in close sequence today; I couldn't stop it, so I had to debug it a bit. :-)

I tried running indicator-applet within valgrind, but apart of a conditional jump on startup in the gtk / zlib init, I would just get the backtrace at the time where it segfaults, even after installing indicator-applet, libdbusmenu-glib3 and libglib2.0-0 ddebs.

I tried running indicator-applet within gdb, and saw the same backtrace is actually in update_layout_cb(), where data is optimized out (it's a static function) but if I print *client, I see that it's corrupt.

I added a breakpoint where the debug is registered, but all the private callback data was correct at this point, so it seems corruption is happening later on.

My system has the gnome-power-manager icon updating erratically, so I tried killing gnome-power-manager; now that I've done that, it doesn't crash anymore.