GNOME Bugzilla – Bug 170275
Documnets in floppy drive opened in unknown application
Last modified: 2005-03-14 08:07:43 UTC
Distribution: Debian testing/unstable Package: bug-buddy Severity: normal Version: GNOME2.8.1 2.8.1 Gnome-Distributor: Ubuntu Synopsis: Documnets in floppy drive opened in unknown application Bugzilla-Product: bug-buddy Bugzilla-Component: docs Bugzilla-Version: 2.8.1 BugBuddy-GnomeVersion: 2.0 (2.8.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/bin/gnome-panel' (no debugging symbols found)...Using host libthread_db library "/lib/tls/i686/cmov/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)...(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)...[Thread debugging using libthread_db enabled] [New Thread 1087387584 (LWP 3685)] (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)...0xffffe410 in __kernel_vsyscall ()
+ Trace 56834
Thread 1 (Thread 1087387584 (LWP 3685))
------- Bug moved to this database by unknown@bugzilla.gnome.org 2005-03-14 01:53 ------- Unknown version 2.8.1 in product bug-buddy. Setting version to "2.8.x". Unknown platform unknown. Setting to default platform "Other". Unknown milestone "unknown" in product "bug-buddy". Setting to default milestone for this product, '---' The original reporter of this bug does not have an account here. Reassigning to the person who moved it here, unknown@bugzilla.gnome.org. Previous reporter was emulovhe@geology.uct.ac.za. Setting to default status "UNCONFIRMED". Setting qa contact to the default for this product. This bug either had no qa contact or an invalid one.
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. Matches the stack trace in bug 169328, which has been marked as a duplicate of 157723. *** This bug has been marked as a duplicate of 157723 ***
*** Bug 170281 has been marked as a duplicate of this bug. ***