network usage wrong because of scaling

do you use warty or hoary? upstream have a bug about this and that should be
fixed with the hoary version: http://bugzilla.gnome.org/show_bug.cgi?id=88654

I'm now using Hoary.
It's not fixed here, still as I described it. It takes about 1-2 min. to rescale the graph to
~100% when idle. Don't know what other info I can give to help...

I'm not sure that's a bug. The applet auto-scale to fix the issue pointed by
http://bugzilla.gnome.org/show_bug.cgi?id=88654. What behaviour would you like
to get for the applet?

------- Additional Comment #8 From Benoît Dejean 2005-01-10 08:29 UTC -------

Fixed in CVS HEAD.

gnome-applets (2.12.1-0ubuntu1) breezy; urgency=low

  * New upstream release: "Lies, Damn Lies and Statistics":
    - This is the first maintainance release of GNOME Applets for stable
      consumption. It contains only fixes and translations. GNOME-Applets
      will branch for development after this release.
    - Fixes:
      - Build fixes for Cygwin (Cygwin Team)
      - Add figures to tarball (Ryan Lortie) (Ubuntu: #14535)
      - Drivemount: correctly fall back to volume activation URI (James
        Henstridge)
      - Drivemount: ensure button relief is set on newly-created drives
        (Ryan Lortie)
      - GSwitchIt: small polish, improvement for plugins (Sergey Udaltsov)
      - GTik: Properly escape stock symbols (Ryan Lortie) (Ubuntu: #12573)
      - Gtik: report 3 digits as upstream does (Ryan Lortie)
      - Gtik: clean ups, remove strtok() (Ryan Lortie)
      - "Maintainer stuff" (Davyd Madeley)
      - Mixer: fix rounding errors for setting new volume (Ronald S.
        Bultje)
      - Documentation: charpick/it (Luca Ferretti), charpick/pt_BR
        (Pedro de Medeiros), gweather/uk (Maxim Dziumanenko), gweather/es
        (Francisco Javier F. Serrador), mini-commander/pt_BR (Pedro de
        Medeiros), trashapplet/it (Luca Ferretti)
      - Translations: it (Alessio Frusciante, Luca Ferretti), gl (Ignacio
        Casal Quinteiro), zh_TW (Chao-Hsiung Liao), bg (Yavor Doganov), bn
        (Mahay Alam Khan), vi (Clytie Siddall), eu (Inaki Larranaga), de
        (Frank Arnold), ja (Takeshi AIHANA), fi (Ilkka Tuohela)
      - Ubuntu: #14560, #9129.
  * debian/patches/05_gtik_3decimalplaces.patch:
    - dropped, done upstream.
  * debian/patches/12_activation-uri_from_volume.patch:
    - dropped, done upstream.
  * debian/rules:
    - disabled broken portion in the clean target.
  * debian/gnome-applets-{data,dev}.install:
    - updated.

 -- Daniel Holbach <email address hidden> Tue, 4 Oct 2005 08:56:19 +0200

*** Bug 24760 has been marked as a duplicate of this bug. ***

The GNOME bug report has a comment from exactly a year ago today saying that
this has been fixed "in CVS HEAD".

A year later, the fix still hasn't made its way into dapper. There's still no
way I can see to set the maximum, so the applet auto-scales and is therefore
basically useless.

I'm on a 6Mbit link, and am currently transferring a steady 10Kb/s - that's
around 1% of capacity, but the applet is showing "100% in use".

If I could tell the applet that 100% means 6Mbit/s then it would know that I'm
using effecting no bandwidth.

Has this bug been overlooked? It is marked as "RESOLVED FIXED".

I'm running gnome-applets version 2.13.1-0ubuntu3.

Followed up on the upstream bug report.

The upstream bug says "Fix Released". Can someone please check if everything works as expected now on the latest Dapper? If the problem does not persist, then we could close this bug.

Thank you.

Nothing appears to have been changed upstream. The applet automatically scales, and doesn't tell you what scale it's using, and so ends up providing almost no information.

Download at a steady 10kB/s or a steady 10MB/s and you'll see the same - a flat graph saying that the network is 100% used. What good is that?

Changing the tooltip to display actual data (like current up and down speeds for example) rather than just a meaningless percentage would help, but to fix the bug properly the user should be allowed to specify the scale to use. It's a nonsense to tell me that my network is 100% in use when you have no idea what my network speed is.

I asked back on the upstream bug.