lxpanel crashed with SIGSEGV in g_main_context_dispatch()

[Jānis Kangarooo]

Binary package hint: lxpanel

nothing crashed at least i didnt see anything and this camne up

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: lxpanel 0.5.5-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-22.36-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-22-generic i686
NonfreeKernelModules: nvidia
Architecture: i386
Date: Tue Jun 29 20:09:16 2010
ExecutablePath: /usr/bin/lxpanel
InstallationMedia: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: lxpanel --profile Lubuntu
ProcCwd: /home/kng
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x80658eb: mov 0x4(%eax),%eax
 PC (0x080658eb) ok
 source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: lxpanel
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /lib/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
Title: lxpanel crashed with SIGSEGV in g_main_context_dispatch()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 task_draw_label (tk=0x858e398) at taskbar.c:310
 flash_window_timeout (tk=0x858e398) at taskbar.c:935
 g_timeout_dispatch (source=0x8640b50, callback=0,
 IA__g_main_context_dispatch (context=0x847ea48)
 g_main_context_iterate (context=0x847ea48,

[Charlie Kravetz (cjkgeek)]

 Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

[Julien Lavergne (gilir)]

Reported upstream : https://sourceforge.net/tracker/?func=detail&aid=3030538&group_id=180858&atid=894869

[Chris Guiver (guiverc)]

Thank you for reporting this bug to Ubuntu.

Ubuntu 10.04 (lucid) reached end-of-life on May 9, 2013.

See this document for currently supported Ubuntu releases:
https://wiki.ubuntu.com/Releases

We appreciate that this bug may be old and you might not be interested in discussing it any more. But if you are then please upgrade to the latest Ubuntu version and re-test. If you then find the bug is still present in the newer Ubuntu version, please add a comment here telling us which new version it is in.