However, in Maverick the /opt/ltsp/i386/etc/rcS.d/S32ltsp-client-setup
file is substantially smaller and not reference is made to jetpipe at
all. udev is refered to, but there are no udev script to run in the
event that a device is connected.
Does anyone know how this works and what is wrong?
--
It seems that it doens't work in Maverick anymore. The behaviour that
was described 9.04 is also found in 10.10.
Python serial is installed, yet jetpipe is not triggered when a USB
printer is plugged into a thin client machine.
--
ltsp-client chroot is missing the python-serial package
https://
Dependency has been fixed in Karmic.
** Changed in: ltsp (Ubuntu)
Status: Confirmed => Fix Released
--
ltsp-client chroot is missing the python-serial package
https://bugs.launchpad.net/bugs/368079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscr
I found the exact same problem yesterday and can confirm the bug. I
think this is a high importance bug as printers that were working no
longer work and it's a case for a SRU.
** Changed in: ltsp (Ubuntu)
Status: New => Confirmed
--
ltsp-client chroot is missing the python-serial package
I can confirm that the above-mentioned workaround solves the problem.
Thank you!
--
ltsp-client chroot is missing the python-serial package
https://bugs.launchpad.net/bugs/368079
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu
the following workaround should fix the issue:
sudo chroot /opt/ltsp/i386 apt-get install python-serial
sudo ltsp-update-image
apparently there was no dependency added to the ltsp-client package when
jetpipe grew serial support.
** Summary changed:
- ltsp not launching jetpipe on startup
+ ltsp
