Hi Daniel,
Daniel Echeverry <epsi...@debian.org> writes: > On Wed, Jan 08, 2020 at 11:25:05PM -0500, Daniel Echeverry wrote: >> tags 948404 + moreinfo unreproducible >> thanks >> >> Hi! >> >> Thanks for your report! Unfortunately I can't reproduce this bug, I install >> glances via ap-get install and works fine, However, I think that bug is >> related with this other bug[1], One Question, Do you have network interfaces? >> >> Regards. >> >> [1]: https://github.com/nicolargo/glances/issues/1535 > > Hi! > > Excuse me, In the reply, I forgot to cc you, do you see the message? Yes I indeed have network interface 1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000 link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00 3: docker0: <NO-CARRIER,BROADCAST,MULTICAST,UP> mtu 1500 qdisc noqueue state DOWN mode DEFAULT group default link/ether 02:42:11:40:33:45 brd ff:ff:ff:ff:ff:ff 8: wlp3s0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc pfifo_fast state UP mode DORMANT group default qlen 1000 link/ether 64:5a:ed:e8:cc:87 brd ff:ff:ff:ff:ff:ff But now I can launch glances fine. I'm not sure what really changed. I did a couple of update of system initially glances from pip was only getting launched. I think for now the bug can safely be closed. Thanks for maintaining glances in Debian Cheers, Vasudev
