-
Notifications
You must be signed in to change notification settings - Fork 18
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
System information not appearing #26
Comments
Hi @paulmadore can you please tell me the distro you are running on. I have had similar problems with arch linux users. Nice work with your theme BTW. |
I'm on Debian stretch: $ lsb_release -a |
Do you have an /etc/lsb-release or /etc/os-release file on you system. If you do and you still have this problem, i might have to find another way to get that information for debian users. |
It looks like I don't. I installed the "lsb-core" package and that didn't seem to help that "no modules" situation either. It's really weird that it will allow it to have the info for Root, but not otherwise. There's apparently something you can do with the sudoers file to whitelist a program, but I've never done it before and I'm nervous about editing that file willy nilly. |
Hmm, you can still access that file without running as root. Have you tired changing permissions on the file. |
I just want to say, also, that I think this program is WAY better than Conky and that styling with HTML/CSS is a brilliant move. I'd like to see that method expanded to a whole desklet system. |
Thanks. It should be a file in the /etc directory. Thats where cysboard will look for it. If it does not find a file named |
No errors: However, it appears that my os-release file is located in /usr/lib. Again, it shows the correct (at least, the ram -- still doesn't know it's on Debian) output when run as root: Where is the line of code I can change to make it look in /usr/lib instead? Perhaps a good long-term fix for this is to have a configuration file associated with it that can change defaults like this. |
The code is in the |
Okay, I'll have a look. Glad to know it wasn't just bad configuration on my part. |
Well, this is helpful information: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=444678 Debian does not have an /etc/lsb_release file. I'm wondering if I can create one myself. |
By creating a file /etc/lsb-release with the following lines: DISTRIB_ID=Debian I was able to get it to print Debian. This is quick hack until it is learned how to get the information in Debian. The ram still does not display without running as root. Looking into that next. |
The ram issue was a problem with my template. What I am going to do is write a little script that generates an lsb-release file for Debian systems, and this can be an optional fix for Debian users whilst you create something more universal. |
Thanks for the work around. Looks like i'll have to have the files in a list generated at compile time for different distros and select from that at runtime. |
Yeah, and that's a bit more work than I want to do at this point. I'm going to create a theme repository for Cysboard at lucky.computer/cysboard For whatever reason Debian broke with the standardized way of providing system information. They minimally comply with the LSB standard by having output via the lsb_release command. My computer company will still be shipping Debian but I think I will have to do something about this issue, some script that generates a standard lsb-release file during updates. It's really great to see a conky alternative that is more fun to work with. |
It will appear if I run the program as root. How can I fix this?
The text was updated successfully, but these errors were encountered: