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 325069 - Critical warning to fix really soon now ;-)
Critical warning to fix really soon now ;-)
Status: RESOLVED DUPLICATE of bug 325707
Product: bug-buddy
Classification: Deprecated
Component: general
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Bug-buddy Maintainers
Bug-buddy Maintainers
Depends on:
Blocks:
 
 
Reported: 2005-12-27 16:26 UTC by Vincent Untz
Modified: 2006-01-05 17:15 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
Ugly hack, that happens to work around this problem (1.00 KB, patch)
2005-12-28 20:26 UTC, Elijah Newren 		rejected Details | Review

Description Vincent Untz 2005-12-27 16:26:28 UTC 
Gtk-CRITICAL **: gtk_progress_set_percentage: assertion `percentage >= 0 && perc entage <= 1.0' failed
aborting...

Program received signal SIGABRT, Aborted.

+ Trace 64830

Thread NaN (LWP 1451)

  • #0 __kernel_vsyscall
  • #1 raise
    from /lib/tls/i686/cmov/libc.so.6
  • #2 abort
    from /lib/tls/i686/cmov/libc.so.6
  • #3 IA__g_logv
    at gmessages.c line 497
  • #4 IA__g_log
    at gmessages.c line 517
  • #5 IA__g_return_if_fail_warning
    at gmessages.c line 532
  • #6 IA__gtk_progress_set_percentage
    at gtkprogress.c line 586
  • #7 IA__gtk_progress_bar_set_fraction
    at gtkprogressbar.c line 1011
  • #8 async_update
    at bugzilla.c line 284
  • #9 dispatch_sync_job_callback
    at gnome-vfs-job.c line 282 






Comment 1


Elijah Newren





          2005-12-28 20:26:07 UTC
        



Created attachment 56478 [details] [review]
Ugly hack, that happens to work around this problem

Just thought I'd post the patch for informational purposes (and maybe provide a workaround for people that are using development builds but want a working bug-buddy despite the fatal criticals).  

Looking a little deeper, for some odd reason info->bytes_total seems to be 4096.  So, this thing crashes as soon as more than 4K bytes are copied.  I don't grok gnome-vfs, so I don't know why it thought there were only 4K bytes to download (the file size is like 81K that it needed), but it is.  So, we need someone to figure out why it has the wrong download size (and note that wget seems to figure it out just fine...)






Comment 2


Fernando Herrera





          2006-01-05 17:15:25 UTC
        



Ey sorry Elijah I completely missed your bug report. I reported the gnome-vfs bug after seeing that the GnomeVfsProgressInfo struct was completly zeroed in the async_xfer callback only with gnome-vfs 2.13

We added a similiar workaround like this from another bug report to let people submit bugs until gnome-vfs get fixed.



*** This bug has been marked as a duplicate of 325707 ***