Hi Gustin :) > Take the time to read the whole post, to the end.
Not today. I wonder why Novell's AppArmor is used by Ubuntu ;). I'm not fine with the Novell-Microsoft deal, but I don't trust Mark Shuttleworth, because of his biography and I wish that a project like KDE is sponsored by different companies. It's okay if it's done by Canonical and Novell, but I don't like monopolies and it looks like Mark Shuttelworth will become pope of Linux. It's not an objective aspect, I speculate because of insight into human nature. > This is not a trick, it is preventing esd from locking the sound > hardware. You could just as easily stop esd via whatever mechanism is > appropriate. > > Changing hw:1 is only useful if you have 2 or more sound devices > attached to your system. When I attach a USB sound device, it becomes > hw:1 while the onboard remains hw:0. It is useful to figure out what > some of this stuff *means*. I don't have to kill esd, Jack is fine with hw:0 without doing it. Why has Peter to kill esd? It's not a solution to kill something, where nothing should run, resp. it's a solution, but without knowing what went wrong. So I think it might be a way to check out, if an application starts the default hw:0 or if jackd is the cause of this problem and an evidence might be, if there will be a message "hw:1(or any number but 0) already in use" after giving the sound card a fixed index but index 0. I hoped pstree could say if ALSA or OSS is used by an application, but it won't. Cheers, Ralf
signature.asc
Description: OpenPGP digital signature
_______________________________________________ 64studio-users mailing list [email protected] http://lists.64studio.com/mailman/listinfo/64studio-users
