On Friday 05 August 2016 05:18:10 deloptes wrote:
Gene Heskett wrote:
On Thursday 04 August 2016 20:58:50 deloptes wrote:
Gene Heskett wrote:
and type in the fix it: alsactl restore.
perhaps try alsactl store ? It helps.
Only if you have called up the alsoctl.gui and made it functional. No use storing defective settings into your home dir.
No issue here with the sound and never had, though this problem was visible from time to time during the years on different machines after upgrades, migration to new hardware etc etc. Storing the settings solves it. This should be called on shutdown/reboot as well same as restore on boot by the init script AFAIR. I am not sure if TDE saves the state. My impression is it reads the state from alsa.
In which case it is reading a defective file in /root since the shutdowen and init stuff runs as root, whereas if I run the restore from a terminal, as me, then it reads a good file from my home dir, one that I previously saved after calling up the gui as me and making it work.
It is neither in user dir not in root dir. It is saved in /var/lib/alsa/asound.state
So it is. Owned by root but world rw. Then why, if root can access it during the init phase, is it not active for me until I do an alsactl restore ? Something in starting the x stuff as the usr after the login, is killing the sound UNTIL the user does a restore. And its a right PIMA. Just for S & G, I just added an aplay command to be executed by me, immediately after a line in rc.local that does a theoretical restore, as me to play the front-center channel id file. I'll see if that plays when I next reboot. Which is not eminent ATM.
regards
To unsubscribe, e-mail: trinity-users-unsubscribe@lists.pearsoncomputing.net For additional commands, e-mail: trinity-users-help@lists.pearsoncomputing.net Read list messages on the web archive: http://trinity-users.pearsoncomputing.net/ Please remember not to top-post: http://trinity.pearsoncomputing.net/mailing_lists/#top-posting
Cheers, Gene Heskett