After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 327018 - The Application "bug-buddy" has quit unexpectedly while updating
The Application "bug-buddy" has quit unexpectedly while updating
Status: RESOLVED DUPLICATE of bug 325707
Product: bug-buddy
Classification: Deprecated
Component: general
2.12.x
Other other
: High critical
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
Depends on:
Blocks:
 
 
Reported: 2006-01-15 00:45 UTC by Francis Shim
Modified: 2006-01-15 00:51 UTC
See Also:
GNOME target: ---
GNOME version: 2.13/2.14



Description Francis Shim 2006-01-15 00:45:06 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 ()

Thread 1 (Thread -1209067856 (LWP 2802))

  • #0 __kernel_vsyscall
  • #1 __waitpid_nocancel
    from /lib/libpthread.so.0
  • #2 gnome_init_with_popt_table
    from /usr/lib/libgnomeui-2.so.0
  • #3 <signal handler called>
  • #4 g_logv
    from /usr/lib/libglib-2.0.so.0
  • #5 g_log
    from /usr/lib/libglib-2.0.so.0
  • #6 g_return_if_fail_warning
    from /usr/lib/libglib-2.0.so.0
  • #7 gtk_progress_set_percentage
    from /usr/lib/libgtk-x11-2.0.so.0
  • #8 gtk_progress_bar_set_fraction
    from /usr/lib/libgtk-x11-2.0.so.0
  • #9 end_bugzilla_download
  • #10 gnome_vfs_job_get_count
    from /usr/lib/libgnomevfs-2.so.0
  • #11 g_list_remove_link
    from /usr/lib/libglib-2.0.so.0
  • #12 g_main_context_dispatch
    from /usr/lib/libglib-2.0.so.0
  • #13 g_main_context_check
    from /usr/lib/libglib-2.0.so.0
  • #14 g_main_loop_run
    from /usr/lib/libglib-2.0.so.0
  • #15 gtk_dialog_run
    from /usr/lib/libgtk-x11-2.0.so.0
  • #16 main




------- 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".

Comment 1 Olav Vitters 2006-01-15 00:51:54 UTC
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 ***