GithubHelp home page GithubHelp logo

Comments (13)

TobBrandt avatar TobBrandt commented on July 24, 2024

Please try the following in a console:

killall indicator-netspeed && indicator-netspeed & disown

Does your interface now appear in the list?

If not, please post the output of

ifconfig

from indicator-netspeed.

denispr avatar denispr commented on July 24, 2024

yes, now ppp0 appears on the list.
But selecting it in the list does not work, wlan0 still appears as the monitored interface and downloading files shows "0,0 Kb/s" in netspeed.

from indicator-netspeed.

TobBrandt avatar TobBrandt commented on July 24, 2024

The reason why ppp0 doesn't initially appear in the list is probably that indicator-netspeed starts before the modem is picked up by the OS. We never refresh the interface list after it's populated once (that's a known issue, I'll create a ticket for it).

However, I would have expected ppp0 to be selectable after the restart. Can you select "all"? Does that show any traffic?

from indicator-netspeed.

denispr avatar denispr commented on July 24, 2024

selecting "all" does not work either, "wlan0" still appears as the monitored interface after that operation.

from indicator-netspeed.

TobBrandt avatar TobBrandt commented on July 24, 2024

Could you please select ppp0 from the interface list, then run the following in a console and post the output

dconf read /apps/indicators/netspeed/if-name

In case you don't have dconf installed, you need to install package dconf-cli (at least that's how it's called on Debian and Ubuntu).

from indicator-netspeed.

denispr avatar denispr commented on July 24, 2024

well, strangely, after I performed dconf read /apps/indicators/netspeed/if-name (which returned "ppp0"), netspeed works, displaying non zero throughput and showing that the monitored interface is ppp0...

from indicator-netspeed.

TobBrandt avatar TobBrandt commented on July 24, 2024

Interesting. I will investigate this further and get back to you. Thanks for your input!

from indicator-netspeed.

TobBrandt avatar TobBrandt commented on July 24, 2024

I've added some tracing. Would you be so kind and check out to the latest revision, go to the checkout directory, then execute

make
killall indicator-netspeed
./indicator-netspeed --trace

and after a few second you can kill it with Ctrl+C.

The output should show something like

Tracing is on
populating list of interfaces
adding interface eth0
skipping loopback interface
adding interface ppp0
adding interface wlan0

followed by repeatedly

getting net traffic...
selected interface is ppp0

and

processing interface XXX

for each interface.

What does it do for interface ppp0. Does it show any in/out traffic or does it say "skipping"? Does "processing interface ppp0" appear at all?

from indicator-netspeed.

denispr avatar denispr commented on July 24, 2024

Good news, after rebooting, it still worked, showing traffic on ppp0.

And after recompiling with the tracing option, the output is:

Tracing is on
populating list of interfaces
adding interface ppp0
adding interface wlan0
skipping loopback interface
adding interface eth0

getting net traffic...
selected interface is ppp0

processing interface ppp0
in: 164595, out: 0

processing interface wlan0
skipping

processing interface lo
skipping loopback interface

processing interface eth0
skipping

...

Just one thing, I also tried to select "all", just to see what it does, and it made indicator-netspeed crash with segmentation fault.

from indicator-netspeed.

TobBrandt avatar TobBrandt commented on July 24, 2024

Just one thing, I also tried to select "all", just to see what it does, and it made indicator-netspeed crash with segmentation fault.

Does that happen every time you click all? I can not reproduce this here.

from indicator-netspeed.

denispr avatar denispr commented on July 24, 2024

I tried three times, it happened each time.

from indicator-netspeed.

TobBrandt avatar TobBrandt commented on July 24, 2024

Sorry, my fault. Recompiling helps :-)

This problem should be fixed now. I introduced it accidentally in my previous commit. In my defense: the GTK docs aren't very clear on who owns what memory and who's responsibility it is to free it again.

from indicator-netspeed.

denispr avatar denispr commented on July 24, 2024

Thanks, I tested the new release, no more crash !

from indicator-netspeed.

Related Issues (12)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    πŸ–– Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. πŸ“ŠπŸ“ˆπŸŽ‰

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❀️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.