On Mon, 2009-03-16 at 10:04 +0000, BUGabundo wrote: > I upgraded, and once i added a new one, it didnt detect my wired connection > (the only one I'm using right now). > I force to manually use wired and still it failed to measure traffic
I suspect your description may be confusing the issue here, so sorry if I question it. Let's address the points so I am sure I understand completely. 1. My interpretation of "...it didn't detect..." means the applet does not offer the wired connection in the list of devices in the preferences dialog. 2. However, from the debug trace I can see that the wired connection *is* reporting data so should I understand you to mean "the applet does not auto-detect the only currently running interface - which is eth0 - but when I disable automatic detection I can choose the wired connection from the 'Device names' combo-box ? 3. In automatic-detection mode which interface does the applet report information? Does that information include data throughput? Now we've got that sorted out, lets get to the good news :) The trace log you've attached is showing that data through-put for eth0 *is* being reported: > get_device_info() calling glibtop_get_netload(&netload, eth0) > up 1, running 0, bytes_out 12821953, bytes_in 228127882 > get_device_info() calling glibtop_get_netload(&netload, wlan2) > up 0, running 0, bytes_out 0, bytes_in 0 However, look at the "running" value. It should be showing "1" for an in-use interface but for some reason isn't. The 'running' flag is used internally by the applet to detect the 'active' device. If no device is running then, from what I can recall from the source-code, it won't try to measure traffic. So, is there *anything* unusual about the PC's networking configuration? Things like, is the interface configured manually? Is NetworkManager managing the interface? If we can discover why all the interfaces are reporting running = 0 we might solve the issue for netspeed. -- netspeed applet will not measure wired https://bugs.launchpad.net/bugs/335507 You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
