[pkg-fso-maint] Bug#602511: Fwd: Re: upstart support for nodm

[jidanni at jidanni.org]

All I know is you fellows broke nodm rather royally for me.
I use nodm on desktops and laptops, with Debian flavor:
deb http://ftp.us.debian.org/debian experimental main contrib non-free
deb http://ftp.us.debian.org/debian unstable main contrib non-free

I did aptitude forbid-version nodm and will stay with
nodm:
  Installed: 0.7-1.1
  Candidate: 0.8-1
for now. http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=633089
I fear assisting further test will injure my monitors, judging from how
the multitude of different behaviors observed upon start, no matter the
value of NODM_USER, including root and vanilla test accounts.

The old nodm started right away, no ifs ands or buts. On my three
computers, the new one just sputters along, popping in and out of a
blank screen and then back to the console and back to the blank screen.
Or dying completely. Or getting into X but not reading ~/.Xresources ...
etc. Must be some kind of a race condition, that's all I know. Yes, I
purged and reinstalled. Snap, crackle, pop. No more testing for me lest
I need to go to town to buy a new monitor.

P.S., Upon install we are asked "start at boot...?" Well if we say "no",
we will never be able to start it, and the rest of the configuration is
aborted. That message needs to be updated to sysv-rc-conf(8) era
thinking. Giving more details, for the user who still wants
/etc/init.d/nodm start to work, but not to start at boot. (I start via a
question with countdown in /etc/rc.local myself).