Jorge Fábregas wrote:
I've been recording radio shows (using sox) all this time without any single problem. Suddenly I'm now unable to to record them.
The only different thing I'm doing now is that I log out from KDE before leaving my house in the morning. When I arrive from work at night I now notice that nothing is being recorded. (I have a cron job scheduled at 4pm to record show).
Do you start in runlevel 3 or 5 (i.e. console or graphical). My guess is 5, and logging out of kde logs you out, which changes the permissions on the devices per resmgr. For this to work, IIANM, you would need to be logged in.
Before this, I always left my KDE session open. Today I did a test...I sshed to my home around the time the show was going to be recorded ...and I typed:
Unless you change it from the default, an ssh session does log into the resmgr. Therefore, perms are as if you are not logged in.
aumix -q and I got "error opening mixer ". I even tried playing an mp3 file from command line (using mpg123) and I got the following error: ALSA lib confmisc.c:672:(snd_func_card_driver) cannot find card '0'
For it to work for ssh sessions, check /etc/pam.d/sshd
Is there like a timeout for the sound module? No If it's not being used for a certain time...will it be unloaded? No. How come this never happend while I had my KDE session going? You were logged in, and registered with resource manager (resmgr), which allowed you access permissions. What does KDE do in order to make the sound-module loaded all the time? I don't believe kde is doing anything, and the problem is not the sound module, but device permissions. HTH
-- Joe Morris Registered Linux user 231871