> So looks like only that user's some config file that gets read when the > user logs in to KDE is the culprit. Ideas?
It is, but damfino what it is. I posted about a similar problem. Actually the same thing. "IEC958 Optical Raw Playback," right? I got a lot of people throwing out random and ultimately useless suggestions, but nobody had a clue where this is really coming from. I haven't been able to figure it out myself. My solution was to fix the mixer, then do an alsactl store 0, then copy /var/somewhere/asound.state to make a copy of what it looked like with the mixer working. Whenever something goes awry (like right after any of my users log in) I can just click an icon to run a script to copy that back over and run an alsactl restore 0 to fix everything. I'm sure there is a more tidy way than this ugly hack, but at least it works the same way every time, and I have found a way to live with this mysterious KDE flummy that keeps screwing everything up. -- Michael McIntyre ---- Silvan <[EMAIL PROTECTED]> Linux fanatic, and certified Geek; registered Linux user #243621 http://www.geocities.com/Paris/Rue/5407/ http://rosegarden.sourceforge.net/tutorial/ -- To UNSUBSCRIBE, email to [EMAIL PROTECTED] with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
