I tested Xubuntu 10.04 RC (20100419) in LiveCD mode (no installation or thelike).
When attempting to shut down xfce4-panel crashed with SIGSEGV in _IceTransWrite().
Whoever will be the triager I ask that person to set this bug report to *high* and not medium since this directly affects the release of Xubuntu and thus needs to be worked on. I relized that one or two similar bugs exist for that package. So I ask to take my request into consideration, please.
Binary package hint: xfce4-panel
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: Thu Apr 22 03:52:41 2010
ExecutablePath: /usr/bin/xfce4-panel
LiveMediaBuild: Xubuntu 10.04 "Lucid Lynx" - Release Candidate i386 (20100419)
ProcCmdline: xfce4-panel
ProcEnviron:
LANG=de_DE.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x7a695c <_IceTransWrite+12>: mov (%eax),%edx
PC (0x007a695c) ok
source "(%eax)" (0x00000019) not located in a known VMA region (needed readable region)!
destination "%edx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: xfce4-panel
StacktraceTop:
_IceTransWrite () from /usr/lib/libICE.so.6
_IceWrite () from /usr/lib/libICE.so.6
IceFlush () from /usr/lib/libICE.so.6
SmcRequestSaveYourself () from /usr/lib/libSM.so.6
logout_session () from /usr/lib/libxfcegui4.so.4
Title: xfce4-panel crashed with SIGSEGV in _IceTransWrite()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
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 480094, 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.
The developers of Xfce thought this had already been fixed, as noted in the Master bug 480094. This report has an invalid stacktrace, but is being used to verify the fix is not complete.