Debian Bug report logs - #770219
nodm does not start

Reply or subscribe to this bug.

Toggle useless messages

Message #5 received at submit@bugs.debian.org (full text, mbox, reply):

From: Michal Suchanek <hramrach@gmail.com>

To: Debian Bug Tracking System <submit@bugs.debian.org>

Subject: nodm does not start

Date: Wed, 19 Nov 2014 21:02:45 +0100

Package: nodm
Version: 0.11-1.3
Severity: normal

Hello,

I rebooted my PC and noticed nodm did not start. Running
/etc/init.d/nodm restart by hand corrects the problem.

reportbug reminds me I have a modified nodm initscript:
--- /etc/init.d/nodm    2011-12-03 16:27:26.000000000 +0100
+++ /etc/init.d/nodm.dpkg-dist  2011-11-20 12:50:47.000000000 +0100
@@ -37,7 +37,7 @@
 # set allowed_users=anybody in /etc/X11/Xwrapper.config
 
 # Gracefully exit if the package or its dependencies have been removed (but not purged).
-[ -x /usr/sbin/nodm -a -x "$NODM_XSESSION" -a -x "$NODM_XINIT" ] || exit 0
+[ -x /usr/sbin/nodm ] || exit 0
 
 
 # Load the VERBOSE setting and other rcS variables
@@ -49,7 +49,6 @@
 
 case "$1" in
        start)
-               plymouth --wait --quit || true
                [ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
                if [ "$NODM_ENABLED" = "no" ] || [ "$NODM_ENABLED" = "false" ]
                then

However, first change should be harmless and would break restart as well and I don't have plymouth.
# ls {/usr,}/{s,}bin/plymouth
ls: cannot access /usr/sbin/plymouth: No such file or directory
ls: cannot access /usr/bin/plymouth: No such file or directory
ls: cannot access /sbin/plymouth: No such file or directory
ls: cannot access /bin/plymouth: No such file or directory

I am not sure what could cause this issue. Any idea what to look at?

I am running systemd.

Thanks

Michal


-- System Information:
Distributor ID:	Ubuntu
Description:	Ubuntu GNU/Linux testing (jessie)
Release:	testing
Codename:	jessie
Architecture: amd64 (x86_64)
Foreign Architectures: i386

Kernel: Linux 3.16-3-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_US.UTF-8, LC_CTYPE=en_US.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash

Versions of packages nodm depends on:
ii  debconf [debconf-2.0]  1.5.53
ii  libc6                  2.19-13
ii  libpam0g               1.1.8-3.1
ii  libx11-6               2:1.6.2-3
ii  x11-common             1:7.7+7
ii  x11-xserver-utils      7.7+3+b1

nodm recommends no packages.

nodm suggests no packages.

-- Configuration Files:
/etc/init.d/nodm changed:
set -e
PATH=/bin:/usr/bin:/sbin:/usr/sbin
DESC="Automatic Display Manager"
NAME=nodm
PIDDIR=/var/run/
PIDFILE=${PIDDIR}/${NAME}.pid
NODM_ENABLED=no
NODM_XINIT=/usr/bin/xinit
NODM_FIRST_VT=7
NODM_XSESSION=/etc/X11/Xsession
NODM_X_OPTIONS="-nolisten tcp"
NODM_USER=root
NODM_MIN_SESSION_TIME=60
if [ -f /etc/default/$NAME ]
then
	. /etc/default/$NAME
fi
export NODM_XINIT NODM_XSESSION NODM_X_OPTIONS NODM_USER NODM_MIN_SESSION_TIME NODM_FIRST_VT
[ -x /usr/sbin/nodm -a -x "$NODM_XSESSION" -a -x "$NODM_XINIT" ] || exit 0
.. /lib/init/vars.sh
.. /lib/lsb/init-functions
case "$1" in
	start)
		plymouth --wait --quit || true
		[ "$VERBOSE" != no ] && log_daemon_msg "Starting $DESC" "$NAME"
		if [ "$NODM_ENABLED" = "no" ] || [ "$NODM_ENABLED" = "false" ]
		then
			log_warning_msg "Not starting $NAME because NODM_ENABLED is '$NODM_ENABLED' in /etc/default/$NAME"
		else
			start-stop-daemon --start --oknodo --pidfile ${PIDFILE} --make-pidfile --background --exec /usr/sbin/nodm
		fi
		[ "$VERBOSE" != no ] && log_end_msg $?
		;;
	stop)
		[ "$VERBOSE" != no ] && log_daemon_msg "Stopping $DESC" "$NAME"
		start-stop-daemon --stop --pidfile ${PIDFILE} --oknodo
		rm -f ${PIDFILE}
		[ "$VERBOSE" != no ] && log_end_msg $?
		;;
	restart|force-reload)
		$0 stop
		$0 start
		;;
	*)
		log_success_msg "Usage: $0 {start|stop|restart|force-reload}" >&2
		exit 1
		;;
esac
exit 0


-- debconf information:
  nodm/xinit: /usr/bin/xinit
  nodm/user: hramrach
  nodm/xsession: /etc/X11/Xsession
  nodm/min_session_time: 60
  nodm/enabled: true
  nodm/x_options: vt7 -nolisten tcp
  nodm/first_vt: 7

Send a report that this bug log contains spam.