xfce4-panel crashed with SIGSEGV in SmcRequestSaveYourself()

[Kenneth J. Weber]

Binary package hint: xfce4-panel

Using rercently-burned Xubuntu 10.04 LiveCD in old HP desktop (about 10 years old, already) with 256M RAM and an Intel Celeron 667MHz processor, this occurred while I was trying to shut down using the upper right-hand exit button. Apport offered to report this bug, so I took it up on it. This is the result.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: xfce4-panel 4.6.3-1ubuntu2
ProcVersionSignature: Ubuntu 2.6.32-21.32-generic 2.6.32.11+drm33.2
Uname: Linux 2.6.32-21-generic i686
Architecture: i386
Date: Mon May 24 09:56:13 2010
ExecutablePath: /usr/bin/xfce4-panel
LiveMediaBuild: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: xfce4-panel
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0xa127f7 <SmcRequestSaveYourself+55>: movb $0x4,0x1(%eax)
 PC (0x00a127f7) ok
 source "$0x4" ok
 destination "0x1(%eax)" (0x00000012) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: xfce4-panel
StacktraceTop:
 SmcRequestSaveYourself () from /usr/lib/libSM.so.6
 logout_session () from /usr/lib/libxfcegui4.so.4
 ?? ()
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
Title: xfce4-panel crashed with SIGSEGV in SmcRequestSaveYourself()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 SmcRequestSaveYourself (smcConn=0x98f4398, saveType=2,
 logout_session (session_client=0x98f39c8)
 evaluate_run_state () at panel-app.c:257
 client_event_received (win=0x98bd8c8, ev=0x99d8cc0)
 _gtk_marshal_BOOLEAN__BOXED (closure=0x98f0be8,

[Charlie Kravetz (cjkgeek)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 386850, so it 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.