reassign 490068 splashy,system-tools-backends /etc/lsb-base-logging.sh: line 259: runlevel: command not found /usr/sbin/invoke-rc.d: line 274: /sbin/runlevel: No such file or
> > This happened during today's upgrade. I know nothing more. I used to > > have package "splashy" installed which apparently messes with some of > > the lsb settings (it's "ubuntufying" them, making the startup sequence > > look like Ubuntu's). FYI, it has nothing to do with ubuntu. > > Apparently splashy left /etc/lsb-base-logging.sh installed. As it should on remove. You probably didn't purge splashy. > > I'd report this bug to both splashy and system-tools-backends if I knew > > how to. It's certainly splashy wreaking havoc, too, but I upgraded many > > packages yesterday and none has complained except system-tools-backends Niko Cavallini Araya schreef: > Lines 259 and 264 of lsb-base-logging.sh are: > > _____________________________________________________________ > 255 # Splashy code > 256 # Stop splashy on *dm but not if we are rebooting/shutting down > 257 if [ -z "${RUNLEVEL:-}" ]; then > 258 # we need only the current level > 259 RUNLEVEL=`runlevel | sed 's/^. //'` > 260 # Bug # 470816 > 261 if [ -z "$RUNLEVEL" ]; then > 262 # if we can't figure out the runlevel (such as when run > 263 # from a cron job) then don't do anything with Splashy > 264 exit $1 > 265 fi > 266 fi > 267 if [ "x$RUNLEVEL" = "x6" ] || [ "x$RUNLEVEL" = "x0" ]; then > 268 return 0 > 269 fi > _____________________________________________________________ > > > This are checking for $RUNLEVEL which in the first line of the error is > not found, so this looks like it comes from elsewhere not splashy. No, you didn't read it right. If $RUNLEVEL is not defined it will run /sbin/runlevel to find the $RUNLEVEL . Apparently the users machine doesn't have a runlevel as you can see from the two error messages. Now the question is: why not? Probably the user doesn't have sysvinit for booting (but upstart or so?)... Now splashy should have a dependency on sysvinit, but that doesn't help; if it is _removed_ /etc/lsb-base-logging.sh is still there. The solution to this (minor) problem would be to check for the splashy executable and bail out if it is not there. grts Tim -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]