DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
(I'm thinking my issue may be a bug in this version of Conky...)
So I had a conky script that worked perfectly on Arch Linux. I had an "if" statement in effect so if I was using wireless internet, my wlan0 information would be displayed. If I was using eth0 instead, then eth0's information would be displayed. For some reason, this doesn't seem to work in Debian - even though if I "cat" the /sys/class/net/wlan0/operstate file, it clearly states either "up" or "down"
Does anybody have any ideas? Here is my conky configuration (stripped down for troubleshooting and only the important section included):
Before you try to mess with the code before hand, have you compared the versions of conky on both OS's? I say that because it just might be a small bug depending on the versions that you have.
Right now, I am using wlan0 which is clearly stating up in the operstate file. However, when conky refreshes, displays wlan0 for a split second, then goes back to eth0.
Honestly I don't know, I don't have my laptop with me, and I am at my girlfriend's house. I am going back to my place either late tonight or tomorrow, if you care to wait until then.
This MUST be a bug, right? Again, it all worked fine in Arch Linux...
So whatever is happening, it is mixing up the interfaces. If I add a third interface (usb0 for tethering), it just gets all screwed up and ommits parts of the conky script.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.