GNOME Bugzilla – Bug 121409
gnome-panel hard crashes
Last modified: 2004-12-22 21:47:04 UTC
Package: acme Severity: blocker Version: 2.2.2.2 Synopsis: gnome-panel hard crashes Bugzilla-Product: acme Bugzilla-Component: general BugBuddy-GnomeVersion: 2.0 (2.2.2) Description: Description of Problem: Gnome-panel hard crashes Steps to reproduce the problem: 1. 2. 3. Use the most recent Debian installation from unstable. Actual Results: Expected Results: How often does this happen? Everytime the time. Additional Information: Debugging Information: Backtrace was generated from '/usr/bin/gnome-panel' (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...[New Thread 16384 (LWP 4731)] (no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... (no debugging symbols found)...(no debugging symbols found)... 0x408ba3d1 in waitpid () from /lib/libpthread.so.0
+ Trace 39951
Thread 1 (Thread 16384 (LWP 4731))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2003-09-03 19:44 ------- The original reporter (billh@gnuppy.monkey.org) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, hadess@hadess.net.
for this to be marginally useful, i need a file or something. cc'ing hadess
You need to ask the reporter of the bug, he only selected the wrong module when filing the bug. -ENOTMYFAULT :)
*** This bug has been marked as a duplicate of 122093 ***