xfce4-panel crashed with SIGSEGV in SmcRequestSaveYourself()

[Philippe Basley]

Binary package hint: xfce4-panel

l'anomalie est apparue sur l'utilisation en live cd "xubuntu 10.4 (lucid)"
en voulant quitter.
N.B.
je suis incapable de trouver le "packagename". Est-ce "lucid"?

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: Sun Aug 29 08:21:18 2010
ExecutablePath: /usr/bin/xfce4-panel
LiveMediaBuild: Xubuntu 10.04 "Lucid Lynx" - Release i386 (20100429)
ProcCmdline: xfce4-panel
ProcEnviron:
 LANG=fr_FR.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x2877f7 <SmcRequestSaveYourself+55>: movb $0x4,0x1(%eax)
 PC (0x002877f7) ok
 source "$0x4" ok
 destination "0x1(%eax)" (0x00000001) 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=0x85fc810, saveType=2,
 logout_session (session_client=0x85fcf50)
 evaluate_run_state () at panel-app.c:257
 client_event_received (win=0x85b6cc8, ev=0x86a1598)
 _gtk_marshal_BOOLEAN__BOXED_BOXED (closure=0x85fafe8,

[Charlie Kravetz (cjkgeek)]

Note to developer: is this a duplicate of bug 386850 , even though the stacktraces are different?

[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.