[apport] gnome-panel crashed with SIGSEGV in ??()

I got a similar trace from vmware, and its gtk2.4 libs.. could that be part of the problem?

got hit the same, suddenly. Stacktrace matches this one. After downloading libc6 debugging symbols, and running apport-retrace I get the following:

Stacktrace:
 Using host libthread_db library "/lib/libthread_db.so.1".
 Core was generated by `gnome-panel --sm-config-prefix /gnome-panel-FiPRVZ/ --sm-client-id 117f00000100'.
 Program terminated with signal 11, Segmentation fault.
 #0 0x00002aff2c449d15 in _int_malloc () from /lib/libc.so.6
 #0 0x00002aff2c449d15 in _int_malloc () from /lib/libc.so.6
 #1 0x00002aff2c44b99d in malloc () from /lib/libc.so.6
 #2 0x00002aff2a16ed25 in _gdk_xsettings_setting_copy () from /usr/lib/libgdk-x11-2.0.so.0
 #3 0x00002aff2a16e72f in _gdk_xsettings_client_get_setting () from /usr/lib/libgdk-x11-2.0.so.0
 #4 0x00002aff2a1531e7 in gdk_screen_get_setting () from /usr/lib/libgdk-x11-2.0.so.0
 #5 0x00002aff29d108c2 in ?? () from /usr/lib/libgtk-x11-2.0.so.0
 #6 0x00002aff2b5846c2 in IA__g_object_get_valist (object=0x6cf280,
     first_property_name=<value optimized out>, var_args=0x7fff827edfe0) at gobject.c:659
        value = {g_type = 64, data = {{v_int = 0, v_uint = 0, v_long = 0, v_ulong = 0, v_int64 = 0,
       v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}, {v_int = 0, v_uint = 0, v_long = 0,
       v_ulong = 0, v_int64 = 0, v_uint64 = 0, v_float = 0, v_double = 0, v_pointer = 0x0}}}
        pspec = (GParamSpec *) 0x2aff2c7269f0
        error = <value optimized out>
        name = $1 = -99
 .
Full report is available if needed.

Could you get a backtrace with libgtk2.0-0-dbg installed?

hggdh, thank you for the detailled backtrace. I've forwarded that upstream: http://bugzilla.gnome.org/show_bug.cgi?id=402478

What do you do to get the bug? Could you try to get a valgrind log for it: https://wiki.ubuntu.com/Valgrind

I do not remember what was it I was doing -- I *think*, at this point in time, I was firing off the Gnome Control Center, but there were a lot of things going on. Also, when the gnome panel bellied up it took some time for apport to bring up the notice, and I was still going on hard... I remember I saw the screen flash, but it only registered a bit later... so the actual sequence of actions has been lost in the limbo.

Sorry.

I also have been unable to reproduce it. And, yes, I thought about Valgrind, since this is seems like a memory allocation issue. I will try to run the panel under it for a while, on the off-chance I hit the issue again.

ah well. It did not take long for me to get fed up with the response times with Valgrind running.

I could not reproduce it, but the Valgrind log does report on unitialised buffers and lost memory. On the chance this might help, I will attach it here.

That looks like a memory corruption, could you get valgrind log (https://wiki.ubuntu.com/Valgrind) for that problem?

the log attached above was the single log valgrind created. I ran it against gnome-panel only.

Here you have another valgrind log for gnome-panel. Lots of lost memory.

No problem pointed by that log that looks like a crasher or a corruption

I am sorry. There is not much I can do, then. I do not have a sequence to reproduce the issue, and I cannot keep on running gnome-panel under valgrind -- response times suck, and there are issues on gnome-panel and any opened windows themselves (open windows are without windows control --right-clicking on the window title bar does not work), and they cover the panel itself, making it unaccessible.

no problem, that's understable, closing the bug for now until somebody can provide useful informations about it