ltsp-client-setup changes order of lts.conf "RCFILE_nn" and breaks some scripts
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
ltsp (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
In /var/lib/
scripts to run on the client at each boot, I was having a big issue with
a script I created to turn on headphone-
the clients. It worked fine in Feisty, but in Gutsy it broke.
Manually running the script after client bootup worked fine.
I manually chrooted and created my own symlinks to my script in default runlevels, ala:
---
# chroot /opt/ltsp/i386/
# update-rc.d ipaqsoundfix.sh defaults 98
---
So, the order of executing RCFILE_nn parms in lts.conf changed from Feisty to Gutsy, causing my script (which contains a single 'amixer set' command to turn on headphone-
Thanks for your assistance!
well, we didnt change anything in this code, but the alsa stack and its initialization procedure changed completely, probably your sound devices are not there or not properly initialized at the point your script runs...
can you put: asoundconf list
in your script and redirect the output to a file to see if alsa sees your card at that point ?