GNOME Bugzilla – Bug 311234
if I select program from list and hit enter mini_commander crashed
Last modified: 2006-02-13 19:02:42 UTC
Distribution: Gentoo Base System version 1.6.12 Package: gnome-applets Severity: normal Version: GNOME2.10.0 unspecified Gnome-Distributor: Gentoo Synopsis: if I select program from list and hit enter mini_commander crashed Bugzilla-Product: gnome-applets Bugzilla-Component: mini-commander Bugzilla-Version: unspecified BugBuddy-GnomeVersion: 2.0 (2.10.0) Description: Description of the crash: Steps to reproduce the crash: 1. 2. 3. Expected Results: How often does this happen? Additional Information: Debugging Information: Backtrace was generated from '/usr/libexec/mini_commander_applet' (no debugging symbols found)...Using host libthread_db library "/lib/libthread_db.so.1". (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)...[Thread debugging using libthread_db enabled] [New Thread 16384 (LWP 9142)] 0x40795ebe in waitpid () from /lib/libpthread.so.0
+ Trace 61936
Thread 1 (Thread 16384 (LWP 9142))
------- Bug moved to this database by unknown@gnome.bugs 2005-07-22 09:12 UTC ------- The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@gnome.bugs. Previous reporter was rat@metal.punkt.pl.
Thanks for the bug report. Unfortunately, that stack trace is not very useful in determining the cause of the crash. Can you get us one with debugging symbols? Please see [WWW]http://live.gnome.org/GettingTraces for more information on how to do so.
*** This bug has been marked as a duplicate of 311068 ***
*** Bug 323849 has been marked as a duplicate of this bug. ***