GNOME Bugzilla – Bug 423676
multiload applet tooltip does not refresh
Last modified: 2010-06-21 19:50:13 UTC
The bug has been opened on https://launchpad.net/bugs/97190 "Binary package hint: gnome-applets Description of the problem: The tooltip displayed on any of the graphs shown by the multiload applet does not update itself to the most recent value as the graph is updated. Steps to reproduce: 1. Press the right mouse button over a piece of empty panel at the top of the screen. 2. Type monitor in to the search box at the to right. Click on System Monitor then click on the Add button at the bottom. 3. A CPU monitor applet should be added to the panel. Start a gnome-terminal and run sleep 10s; glxgears 4. Move the mouse over the monitor applet and (assuming your system is not busy) a tooltip should appear saying that the Processor is (some value less than 100%) in use. Do not move the mouse and the tooltip should remain displayed. 5. Wait 10 seconds. Expected result: Tooltip to say processor is 100% in use (assuming a single CPU machine). Actual result: Tooltip says Processor is (some value less than 100%) in use as at step 4 even though the graph clearly indicates full usage (assuming a single CPU machine). Additional information: The behaviour was as the expected result for this applet on Edgy. Other programs like the rhythmbox tray applet update their tooltip even when the mouse is not moved and the tooltip is already being displayed. Version information: Ubuntu Feisty gnome-applets 2.18.0-0ubuntu1"
Still here in Gutsy. Version information: Ubuntu Gutsy (development branch) gnome-applets 2.19.1-0ubuntu4
Still here in Ubuntu Hardy. Version information: Ubuntu 8.04 gnome-applets 2.22.1-0ubuntu2
Still here. Ubuntu 9.10 2.28.0-0ubuntu2 The tooltip does update properly if I open System Monitor (i.e. by clicking), and then close it again without moving the mouse.
Still here in Ubuntu Lucid. Version information: Ubuntu 10.04 gnome-applets 2.30.0-0ubuntu2 Sebastian: Could you update the version on this bug?
*** This bug has been marked as a duplicate of bug 617992 ***