-
Notifications
You must be signed in to change notification settings - Fork 45
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
Ubuntu 20.04 #154
Comments
I encounter the problem in case hands-on is needed. |
Unfortunately I'm very limited in time currently, so not sure when I'll be able to fix this. |
Might he some package having If you could print both sides of version numbers before this line, we could have samples |
Do you still maintain FireMotD ? |
Im currently working on some other projects and got my hands full. Also, im only using on centos, for other os'es i cant help. Feel free to submit a pr and ill happily accept it. |
The issue is with procps version 2:3.3.16-1. The issue is fixed in 2:3.3.16-5. Find your version with dpkg -l procps. |
how can i update procps to 2:3.3.16-5?? |
Hi I've done this way (on a flavour of Ubuntu 20.04 LTS ( KDE neon User Edition 5.2 or https://www.linuxfx.org/) /usr/local/bin/FireMotD: line 149: ((: 10#3 > 10#UNKNOWN: value too great for base (error token is "10#UNKNOWN") Ciao Sergio |
you can downdload a new version from here https://launchpad.net/ubuntu/+source/procps/2:3.3.16-5ubuntu1/+build/19433805 wget https://launchpad.net/ubuntu/+source/procps/2:3.3.16-5ubuntu1/+build/19433805/+files/procps_3.3.16-5ubuntu1_amd64.deb |
Bug report
We're bundling FireMotD as part of openHABian. I didn't encounter myself but received the following report from two people:
RAM percentage didn't work, and i've the error:
/usr/local/bin/FireMotD: line 149: ((: 10#3 > 10#UNKNOWN: value too great for base (error token is "10#UNKNOWN")
/usr/local/bin/FireMotD: line 153: ((: 10#3 < 10#UNKNOWN: value too great for base (error token is "10#UNKNOWN")
(standard_in) 1: syntax error
(standard_in) 1: syntax error
(standard_in) 1: syntax error
The text was updated successfully, but these errors were encountered: