https://bugzilla.novell.com/show_bug.cgi?id=209619 ------- Comment #2 from inglor@seznam.cz 2006-10-04 02:05 MST ------- Reverted yast2-sound back to the original version. See the description of the bugs below. BTW Cannot find it now, but I believe that installation of a newer yast sound module was suggested in some online forum by a Czech user whose name reminded me of some Czech branch Suse employee (I happen to personally know a lot of them). To tell the truth, he never indicated to take the package from the Factory - in fact, he did not indicate any source for them at all. As for the bugs: I have two soundcards, CMI-8738 on the motherboard and Audigy 4 in a PCI slot. When I start Yast sound setup, I can setup the Audigy correctly as snd-card-0, and I can delete the other card (which I do not want to use). I can even play the loudness setting sound during the setting. But when I try to save these settings and click Finish, the saving freezes in 60% (startup of the sound card). I have to kill the frozen app then. When I restart Yast sound setup after killing the frozen app, the Audigy card seems to be setup correctly and the CMI seems to be inactive - correctly, too. But no sound can be played by the user, programs like mplayer and realplayer end up in message "cannot open audio device" etc. Root can play sounds and use mplayer and realplayer without problems. On recommendation of a friend, I tried to add the user to group audio, to no avail. I haven't changed any access rights manually. What should I do to be able to play music as a normal user? (In reply to comment #1)
(In reply to comment #0)
Upgraded yast2-sound to version 2.13.15-3 from a RPM foung on http://download.opensuse.org/distribution/SL-OSS-factory/inst-source/suse/i5...
Using Factory packages on 10.1 is a very bad idea. Please re-install the original 10.1 package(s).
If you still have problems, please attach the y2logs (see http://en.opensuse.org/Bugs/YaST )
-- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug, or are watching someone who is.