Comment 4 for bug 90383

Not sure if this helps or not... but there are errors.

crazyeccentric@CrazyEccentric:~$ valgrind gnome-panel
==29963== Memcheck, a memory error detector.
==29963== Copyright (C) 2002-2006, and GNU GPL'd, by Julian Seward et al.
==29963== Using LibVEX rev 1658, a library for dynamic binary translation.
==29963== Copyright (C) 2004-2006, and GNU GPL'd, by OpenWorks LLP.
==29963== Using valgrind-3.2.1-Debian, a dynamic binary instrumentation
framework.
==29963== Copyright (C) 2000-2006, and GNU GPL'd, by Julian Seward et al.
==29963== For more details, rerun with: -v
==29963==
==29963== Syscall param writev(vector[...]) points to uninitialised byte(s)
==29963== at 0x4A85BED: do_writev (writev.c:46)
==29963== by 0x4F2D302: (within /usr/lib/libxcb.so.1.0.0)
==29963== by 0x4F2D89A: (within /usr/lib/libxcb.so.1.0.0)
==29963== by 0x4F2D9CC: (within /usr/lib/libxcb.so.1.0.0)
==29963== by 0x4F2DB1E: xcb_flush (in /usr/lib/libxcb.so.1.0.0)
==29963== by 0x48E8DDD: _XSend (in /usr/lib/libX11.so.6.2.0)
==29963== by 0x48D692A: XQueryExtension (in /usr/lib/libX11.so.6.2.0)
==29963== by 0x48CB6BA: XInitExtension (in /usr/lib/libX11.so.6.2.0)
==29963== by 0x4B60DFF: XFixesFindDisplay (in
/usr/lib/libXfixes.so.3.1.0)
==29963== by 0x4B6109C: XFixesQueryExtension (in
/usr/lib/libXfixes.so.3.1.0)
==29963== by 0x45F2374: gdk_display_open (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==29963== by 0x45CFCBE: gdk_display_open_default_libgtk_only (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==29963== Address 0x515681C is 4,684 bytes inside a block of size 8,556
alloc'd
==29963== at 0x402095F: calloc (vg_replace_malloc.c:279)
==29963== by 0x4F2D510: xcb_connect_to_fd (in /usr/lib/libxcb.so.1.0.0)
==29963== by 0x4F2FBF8: xcb_connect (in /usr/lib/libxcb.so.1.0.0)
==29963== by 0x48E7E9F: _XConnectXCB (in /usr/lib/libX11.so.6.2.0)
==29963== by 0x48D0A28: XOpenDisplay (in /usr/lib/libX11.so.6.2.0)
==29963== by 0x45F21C1: gdk_display_open (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==29963== by 0x45CFCBE: gdk_display_open_default_libgtk_only (in
/usr/lib/libgdk-x11-2.0.so.0.1000.9)
==29963== by 0x43A07A4: (within /usr/lib/libgtk-x11-2.0.so.0.1000.9)
==29963== by 0x4847F73: g_option_context_parse (in
/usr/lib/libglib-2.0.so.0.1200.11)
==29963== by 0x415FE88: gnome_program_parse_args (in
/usr/lib/libgnome-2.so.0.1786.6)
==29963== by 0x41611DC: (within /usr/lib/libgnome-2.so.0.1786.6)
==29963== by 0x4161510: gnome_program_init (in
/usr/lib/libgnome-2.so.0.1786.6)
==29963==
==29963== ERROR SUMMARY: 9 errors from 1 contexts (suppressed: 185 from 2)
==29963== malloc/free: in use at exit: 1,850,598 bytes in 20,108 blocks.
==29963== malloc/free: 131,318 allocs, 111,210 frees, 23,572,473 bytes
allocated.
==29963== For counts of detected errors, rerun with: -v
==29963== searching for pointers to 20,108 not-freed blocks.
==29963== checked 2,484,632 bytes.
==29963==
==29963== LEAK SUMMARY:
==29963== definitely lost: 38,454 bytes in 1,367 blocks.
==29963== possibly lost: 98,200 bytes in 138 blocks.
==29963== still reachable: 1,713,944 bytes in 18,603 blocks.
==29963== suppressed: 0 bytes in 0 blocks.
==29963== Use --leak-check=full to see details of leaked memory.
crazyeccentric@CrazyEccentric:~$

Sebastien Bacher wrote:
> Thanks for your bug report. The crash looks like a memory corruption.
> Could you try to get a valgrind log for it? (you can follow the
> instructions from https://wiki.ubuntu.com/Valgrind for that)
>
> ** Changed in: gnome-panel (Ubuntu)
> Importance: Undecided => Medium
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>
>