xfce4-panel crashed with SIGSEGV in SmcRequestSaveYourself()

Bug #474091 reported by Guille
8
This bug affects 1 person
Affects Status Importance Assigned to Milestone
xfce4-panel (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: xfce4-panel

Panel crashed in test system with Karmic CD before installation.

ProblemType: Crash
Architecture: i386
Date: Wed Nov 4 10:08:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/xfce4-panel
LiveMediaBuild: Xubuntu 9.10 "Karmic Koala" - Release i386 (20091028.3)
Package: xfce4-panel 4.6.1-3ubuntu2
ProcCmdline: xfce4-panel
ProcEnviron:
 LANG=es_ES.UTF-8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
SegvAnalysis:
 Segfault happened at: 0x1d1777 <SmcRequestSaveYourself+55>: movb $0x4,0x1(%eax)
 PC (0x001d1777) 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()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Guille (guille-querol) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:SmcRequestSaveYourself (smcConn=0x91db7e8, saveType=2,
logout_session (session_client=0x91dae70)
?? ()
?? ()
_gtk_marshal_BOOLEAN__BOXED (closure=0x91d91e0,

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in xfce4-panel (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

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. Feel free to continue to report any other bugs you may find.

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.