Ubuntu
gnome-panel package

gnome-panel crashed with SIGFPE

Bug #208446 reported by yop on 2008-03-28

This bug report is a duplicate of: Bug #207693: gnome-panel crashed with SIGSEGV. Edit Remove

Affects		Status	Importance	Assigned to	Milestone
	gnome-panel (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: gnome-panel

I was removing the bottum panel and the system froze, then it restarted the panel.

ProblemType: Crash
Architecture: i386
Date: Fri Mar 28 20:42:48 2008
DistroRelease: Ubuntu 8.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 1:2.22.0-0ubuntu2
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-client-id default1
ProcEnviron:
PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
LANG=en_DK.UTF-8
SHELL=/bin/bash
Signal: 8
SourcePackage: gnome-panel
Stacktrace:
#0 0xb65ef7ef in ?? () from /usr/lib/libwnck-1.so.22
#1 0x00000000 in ?? ()
StacktraceTop:
?? () from /usr/lib/libwnck-1.so.22
?? ()
Title: gnome-panel crashed with SIGFPE
Uname: Linux 2.6.24-12-server i686
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin plugdev video

Tags:

Revision history for this message

yop (yop) wrote on 2008-03-28:

Dependencies.txt Edit (5.8 KiB, text/plain; charset="utf-8")
Disassembly.txt Edit (525 bytes, text/plain; charset="utf-8")
ProcMaps.txt Edit (27.4 KiB, text/plain; charset="utf-8")
ProcStatus.txt Edit (710 bytes, text/plain; charset="utf-8")
Registers.txt Edit (471 bytes, text/plain; charset="utf-8")
ThreadStacktrace.txt Edit (473 bytes, text/plain; charset="utf-8")

Revision history for this message

Apport retracing service (apport) wrote on 2008-03-28: Symbolic stack trace

Stacktrace.txt (retraced) Edit (77 bytes, text/plain)

StacktraceTop:?? () from /usr/lib/libwnck-1.so.22
?? ()

Revision history for this message

Apport retracing service (apport) wrote on 2008-03-28: Symbolic threaded stack trace

ThreadStacktrace.txt (retraced) Edit (1.5 KiB, text/plain)

Revision history for this message

Pedro Villavicencio (pedro) wrote on 2008-03-31:

Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.