[Pkg-ltsp-devel] Bug#700881: ltsp-client-core: thin client can't boot if it has set PRINTER_0_DEVICE in lts.conf

[Vagrant Cascadian]

Control: forwarded 700881 https://bugs.launchpad.net/ltsp/+bug/996533
Control: tags 700881 confirmed fixed-upstream

On Mon, Feb 18, 2013 at 02:30:55PM -0500, James McQuillan wrote:
> Setting PRINTER_0_DEVICE in the lts.conf file will cause the workstation to
> stop booting.
> Sample config:
> 
>   PRINTER_0_DEVICE = /dev/lp0
...
> This bug has been fixed in the ltsp upstream package.
> 
> here's the link to 2 patches:
> 
>  http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2382

The first one seems simple enough, though I've heard some reports that it still
doesn't properly daemonize, and dies after serving the first print request.


>  http://bazaar.launchpad.net/~ltsp-upstream/ltsp/ltsp-trunk/revision/2395

This one seems a bit too invasive for wheezy... it rewrites jetpipe to daemonize
without the use of python-daemon.


Looking at the code, it seems like jetpipe is running from init-ltsp.d, which
seems a bit early to be starting daemons... It seems to run fine when started
from /etc/init.d/ltsp-client-core with a quick test.

Will work on another patch that will hopefully be acceptible for wheezy, 
starting jetpipe from the ltsp-client-core init script.


live well,
  vagrant