Ubuntu
ltspfs package

Thin clients won't boot after udev rule transition

Bug #317848 reported by Tommaso R. Donnarumma on 2009-01-16

Affects		Status	Importance	Assigned to	Milestone
	ltspfs (Ubuntu)	Invalid	Undecided	Unassigned

Bug Description

Binary package hint: ltspfs

After the transition of udev rules from /etc/udev/rules.d to /lib/udev/rules.d, thin clients fail to boot with the following error message:

udevd-event[2451]: mknod(/dev/pktcdvd/control, 020660, (10,62) failed: Not a directory

I will now try to workaround this by manually copying the rules to /lib/udev/rules.d inside the chroot and updating everything. Please, let me know if there's any other information I can provide.

ProblemType: Bug
Architecture: amd64
DistroRelease: Ubuntu 9.04
Package: ltspfs 0.5.8-1
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: ltspfs
Uname: Linux 2.6.28-4-generic x86_64

Tags:

Revision history for this message

Tommaso R. Donnarumma (tawmas) wrote on 2009-01-16:

Dependencies.txt Edit (1.5 KiB, text/plain; charset="utf-8")

Revision history for this message

Tommaso R. Donnarumma (tawmas) wrote on 2009-01-16:

I tried to work around this issue with these steps:

1) copied the rules.d directory (and files within) from /opt/ltsp/i386/etc/udev to /opt/ltsp/i386/lib/udev
2) rebuilt the ltsp image
3) updated the ltsp kernels

I performed the same steps for the amd64 chroot as I'm also testing with amd64 clients.

The results are as follows: i386 clients display the usplash screen with the floating progress bar, then hang on a black screen without any message; the amd64 clients display the usplash sceen with the floating progress bar, then the normal progress bar, then hang with the message above.

In short, the behaviour of amd64 clients is unchanged from what they did before the workaround, while the behaviour of i386 clients has worsened (previously they behaved exactly as accounted above for amd64 clients).

Revision history for this message

Stéphane Graber (stgraber) wrote on 2009-03-15:

What's in your /etc/udev/rules.d/ ?

I'm wondering if your problem is really LTSP specific as LTSP only has one udev rule and this one will let you boot even if it doesn't exist. Sounds more like an hardware issue or hardware detection issue that'd affect Ubuntu as a whole and not only LTSP thin clients.

Revision history for this message

Stéphane Graber (stgraber) wrote on 2009-10-24:

Haven't received any more information after more than 6 months, closing that bug.
Feel free to reopen and give more information if it's still happening, also make sure to test with 9.10 if you can.
Thanks