When booting the thin client and logging in as an user, I have local device access working perfectly. When logging out and in again as the same user, it works, too. But when logging in as another user afterwards, local devices are gone and don't work anymore. Even /tmp/drives/readonly isn't automatically mounted any more when inserting a CD. All users with which I tried this have local device access (they are in the "fuse" group). The log file .lbussd_out which is created in the home directory only states lbussd found drives for the first user being logged in, after the next login, no found drives are entered (the last line is 'Entering main loop'). I can manually fire up mounts from the server to mount any directory the currently logged-in user has access to, but since removable media are not automounted any more when another user logs in, this is quite useless. I'm using kubuntu "Breezy Badger" with LTSP 4.2-1.
Pretty much having the same problem with debian sarge. When it was in the failed state restarted lbuscd on the terminal in debug mode "lbuscd -d -n" Much to my surprise usb devices started working again after logging in again. Managed to get it to fail by logging out and back in. Looking at the debug output noticed: When it works see a connect from host message then a register messages for the user. When it fails get the connect messages but no register messages. Have done a lot of lot of relogin attempts. Pretty sure floppy never works the second time. Some times usb drive will work after many relogins but will eventually fail My suspicions are that lbuscd gets in a bad state somehow on the terminal probably because the server side is being restarted on each login. Really should look at the souce. but if does what I think it may explain why the problem is worse with a floppy than with usb devices. May be 2 problems: Losing the information on floppy device. The missing Register messages. John
Jim McQuillan posted a fix: http://marc.theaimsgroup.com/?l=ltsp-discuss&m=115087929232138&w=2
The "second login" issue is supposed to be fixed in LTSP 4.2 update 2.
Jens Rabe, Do you still experience this issue with newer soft? Please check the status of your issue.
Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.