GNOME Bugzilla – Bug 327018
The Application "bug-buddy" has quit unexpectedly while updating
Last modified: 2006-01-15 00:51:54 UTC
Distribution: Fedora Core release 4.90 (Pre-FC5) Package: bug-buddy Severity: Normal Version: GNOME2.13.4 2.12.1 Gnome-Distributor: Red Hat, Inc Synopsis: The Application "bug-buddy" has quit unexpectedly while updating Bugzilla-Product: bug-buddy Bugzilla-Component: general Bugzilla-Version: 2.12.1 BugBuddy-GnomeVersion: 2.0 (2.13.0) Description: Description of the crash: While bug-buddy was updating its list of products for the bug tracking systems it also reports an error; hence, this report to inform developers uses the old information in order to avoid the repeat of this error. Steps to reproduce the crash: 1. First, use the most cutting edge FC5 test release with development packages 2. Log into a user account 3. I obtain "Error" windows for the unexpected quitting of "gnome-volume-manager" and others 4. Click on "Inform Developers" to start the bug-buddy application 5. Click on "Update" when bug-buddy ask if you want to update the old data of your system for debugging purposes. Expected Results: In the case of bug-buddy we should get an updated list of products for the bug tracking systems; however, in order to avoid the problem I had to choose to use the old data. With regards to the originating application of the bug sequence ("gnome-volume-manager"), I am trying to report its problems via the bug-buddy, but may have to report via bugzilla directly. How often does this happen? Consistently without any updating of packages Additional Information: As indicated, the original sequence started from "gnome-volume-manager" application crashing. Debugging Information: Backtrace was generated from '/usr/bin/bug-buddy' (no debugging symbols found) Using host libthread_db library "/lib/libthread_db.so.1". (no debugging symbols found) `shared object read from target memory' has disappeared; keeping its symbols. (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread -1209067856 (LWP 2802)] [New Thread -1259635808 (LWP 2844)] (no debugging symbols found) 0x00c2e402 in __kernel_vsyscall ()
+ Trace 65208
Thread 1 (Thread -1209067856 (LWP 2802))
------- Bug created by bug-buddy at 2006-01-15 00:45 ------- Unknown version 2.12.1 in product bug-buddy. Setting version to "2.12.x".
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. *** This bug has been marked as a duplicate of 325707 ***