lxpanel crashed with SIGSEGV in g_main_context_dispatch()

Bug #543077 reported by Ian Lawrence
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxpanel (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: lxpanel

Lucid - looks like its still a bug

ProblemType: Crash
Architecture: i386
Date: Sat Mar 20 19:28:32 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/lxpanel
Package: lxpanel 0.5.5-0ubuntu2
ProcCmdline: lxpanel --profile LXDE
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x80658bc: cmp %ebx,0xc(%edi)
 PC (0x080658bc) ok
 source "%ebx" ok
 destination "0xc(%edi)" (0x6e696d7e) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown 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()
Uname: Linux 2.6.32-16-generic i686
UserGroups: adm admin cdrom dialout lpadmin netdev plugdev sambashare

Revision history for this message
Ian Lawrence (ianlawrence) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 task_draw_label (tk=0xaf599d0) at taskbar.c:298
 flash_window_timeout (tk=0xaf599d0) at taskbar.c:935
 g_mapped_file_get_length () from /lib/libglib-2.0.so.0
 ?? () from /lib/libglib-2.0.so.0
 g_markup_parse_context_parse () from /lib/libglib-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in lxpanel (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Julien Lavergne (gilir)
visibility: private → public
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.