I don't believe this is related to the exact package being installed, rather the installer itself or a back-end process.
And the various tests for nice values (i.e. Pauls comment #8 : https://launchpad.net/ubuntu/+source/xorg/+bug/68267/comments/8), is there other code to ensure that the value being tested is truly a number?
I.e. if the validate_nice_value() subroutine gets sent text (i.e. "x1" rather than "1"), won't this also produce a similar error?
How about this:
---
validate_nice_value () {
_retval=1
# first, try to subtract number from itself to validate numeric input
# (expr is noisy, always throw away its output)
set +e
# Check for blank/null $1 variable.
if [ ! -z "$1" ]; then
# Exit because we were given a blank line.
fi
# >>>NOTE 1<<<
expr "$1" - "$1" > /dev/null 2>&1
if [ $? -ne 2 ]; then
# now check for valid range
---
I can't think of a concise way to test for a string versus number to put in at the "NOTE 1" location.
I don't believe this is related to the exact package being installed, rather the installer itself or a back-end process.
And the various tests for nice values (i.e. Pauls comment #8 : https:/ /launchpad. net/ubuntu/ +source/ xorg/+bug/ 68267/comments/ 8), is there other code to ensure that the value being tested is truly a number? nice_value( ) subroutine gets sent text (i.e. "x1" rather than "1"), won't this also produce a similar error?
I.e. if the validate_
How about this:
---
validate_nice_value () {
_retval=1
# first, try to subtract number from itself to validate numeric input
# (expr is noisy, always throw away its output)
set +e
# Check for blank/null $1 variable.
if [ ! -z "$1" ]; then
# Exit because we were given a blank line.
fi
# >>>NOTE 1<<<
expr "$1" - "$1" > /dev/null 2>&1
if [ $? -ne 2 ]; then
# now check for valid range
---
I can't think of a concise way to test for a string versus number to put in at the "NOTE 1" location.
Dan