[apport] gnome-panel crashed with SIGSEGV

Bug #91018 reported by headhunter
2
Affects Status Importance Assigned to Milestone
gnome-panel (Ubuntu)
Invalid
Medium
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-panel

blala

ProblemType: Crash
Architecture: i386
CrashCounter: 1
Date: Sat Mar 10 02:28:00 2007
DistroRelease: Ubuntu 7.04
ExecutablePath: /usr/bin/gnome-panel
Package: gnome-panel 2.17.92-0ubuntu4
PackageArchitecture: i386
ProcCmdline: gnome-panel --sm-client-id default1
ProcCwd: /home/thord
ProcEnviron:
 LANGUAGE=sv_SE:sv:en_GB:en
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: gnome-panel
Stacktrace:
 #0 0xb74c7984 in ?? () from /lib/tls/i686/cmov/libc.so.6
 #1 0x00000000 in ?? ()
StacktraceTop:
 ?? () from /lib/tls/i686/cmov/libc.so.6
 ?? ()
ThreadStacktrace:
 .
 Thread 1 (process 5297):
 #0 0xb74c7984 in ?? () from /lib/tls/i686/cmov/libc.so.6
 #1 0x00000000 in ?? ()
Uname: Linux laptop 2.6.20-9-generic #2 SMP Mon Feb 26 03:01:44 UTC 2007 i686 GNU/Linux
UserGroups: adm admin audio cdrom dialout dip floppy lpadmin netdev plugdev powerdev scanner video

Revision history for this message
headhunter (thord2) wrote :
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thanks for your bug report. The crash looks like a memory corruption. Could you try to get a valgrind log for it? (you can follow the instructions from https://wiki.ubuntu.com/Valgrind for that)

Changed in gnome-panel:
assignee: nobody → desktop-bugs
importance: Undecided → Medium
status: Unconfirmed → Needs Info
Revision history for this message
Sebastien Bacher (seb128) wrote :

As described in the previous comments, your report lacks the information we need to investigate the problem further. We'll close this report for now - please reopen it if you can give us the missing information.

Changed in gnome-panel:
status: Needs Info → Rejected
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.