lxpanel crashed with SIGSEGV in g_main_context_dispatch()

Bug #908110 reported by Jerry
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
lxpanel (Ubuntu)
New
Undecided
Unassigned

Bug Description

seems to be happening or something like it for over a year,
reporting anyway, in case it's not a duplicate...

not sure what I was doing at the time that caused
some panel activity. maybe a bad keypress?

happy holidays, and a bug for any geeks out there
looking for something to do ;-/

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: lxpanel 0.5.8-1ubuntu3
ProcVersionSignature: Ubuntu 3.2.0-6.12-generic 3.2.0-rc6
Uname: Linux 3.2.0-6-generic i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
Config_System_LXDE:
 [Command]
 FileManager=pcmanfm %s
 Terminal=x-terminal-emulator
 Logout=lxde-logout
Date: Fri Dec 23 07:41:43 2011
ExecutablePath: /usr/bin/lxpanel
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: lxpanel --profile LXDE
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8063d33: mov 0x4(%eax),%eax
 PC (0x08063d33) ok
 source "0x4(%eax)" (0x000002a8) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: lxpanel
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
 g_main_context_dispatch () from /lib/i386-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/i386-linux-gnu/libglib-2.0.so.0
Title: lxpanel crashed with SIGSEGV in g_main_context_dispatch()
UpgradeStatus: Upgraded to precise on 2011-11-25 (27 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Jerry (jerrywone) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #853276, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
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.