[Splashy-devel] Bug#455259: stop_splashy() from /etc/lsb-base-logging.sh does not check umount's exit value
Miroslaw L. Baran
baran at hell.pl
Sun Dec 9 15:27:28 UTC 2007
Package: splashy
Version: 0.3.7-1
Severity: serious
--- Please enter the report below this line. ---
Hi,
The exit code of umount, as called as in /etc/lsb-base-logging.sh,
decides about the exit code of stop_splashy(); if the $STEPS_DIR is
already unmounted (i.e. almost all the time) this will prevent from
start anything that calls lsb's log_daemon_message and has name of
'?dm'.
Adding simple '|| true' or checking if the $STEPS_DIR is mounted before
an umount attempt will alleviate the problems.
Jubal
--- System information. ---
Architecture: i386
Kernel: Linux 2.6.23-1-686
Debian Release: lenny/sid
990 unstable www.debian-multimedia.org
990 unstable uqm.debian.net
990 unstable ftp.de.debian.org
500 stable volatile.debian.org
--- Package information. ---
Depends (Version) | Installed
===========================================-+-======================
initramfs-tools | 0.91c
libc6 (>= 2.7-1) | 2.7-4
libdirectfb-1.0-0 | 1.0.1-3
libgcc1 (>= 1:4.2.1) | 1:4.2.2-4
libglib2.0-0 (>= 2.14.0) | 2.14.4-2
libmagic1 | 4.21-3
libsplashy1 | 0.3.7-1
lsb-base | 3.1-24
zlib1g (>= 1:1.2.3.3.dfsg-1) | 1:1.2.3.3.dfsg-7
More information about the Splashy-devel
mailing list