Bug 209619

(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/i586/

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 )

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/i586/
> 
> 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 )
> 

Created attachment 100225 [details]
Yast 2 Logs

(In reply to comment #3)
> Created an attachment (id=100225) [edit]
> Yast 2 Logs
> 

Dear Novell Team, it has been some time since I have entered this bug. Is anyone working on it, or has it been abandoned?

Best Regards

Marian Kechlibar

No, it's not abadoned. I have been working on other (more serious) bug reports.

I cannot reproduce it in openSUSE10.2, it works for me (=> decreasing the severity).

I need more information about your configuration:

- is the resource manager running? (use 'ps -A | grep resmgr' command)
- permissions for /dev/audio ('ls -l /dev/audio')
- ACL permissions for /dev/audio ('getfacl /dev/audio')

The resource manager daemon should set permissions for the local user (see the getfacl output).

Dear Mr. Slezak,

I have installed a fresh version of openSUSE10.2 on my PC, on a new HDD (previous versions were upgrades of 9.3, 10.0 respectively). The problem persists.

resmgrd runs, not resmgr

Permissions:

crw-rw---- 1 root audio 14, 4 2006-12-08 11:44 /dev/audio

ACL permissions:

getfacl: Removing leading '/' from absolute path names
# file: dev/audio
# owner: root
# group: audio
user::rw-
group::rw-
other::---


(In reply to comment #6)
> I cannot reproduce it in openSUSE10.2, it works for me (=> decreasing the
> severity).
> 
> I need more information about your configuration:
> 
> - is the resource manager running? (use 'ps -A | grep resmgr' command)
> - permissions for /dev/audio ('ls -l /dev/audio')
> - ACL permissions for /dev/audio ('getfacl /dev/audio')
> 
> The resource manager daemon should set permissions for the local user (see the
> getfacl output).
> 

Marian, how did you log in into the system? (KDM/XDM/GDM or console/ssh...?) The permissions depend on that...

(In reply to comment #10)
> Marian, how did you log in into the system? (KDM/XDM/GDM or console/ssh...?)
> The permissions depend on that...
> 

I believe it is KDM, since I use KDE and all default settings from a normal SUSE installation. 

ps aux | grep "kdm" gives

root      3633  0.0  0.0   3376   692 ?        Ss   09:13   0:00 
/opt/kde3/bin/kdm

Ms. Bernathova told me that she was able to recreate the bug on a laptop, but then it somehow mended itself again.

PS, when I try to run alsamixer as a normal user, the following error shows up:


marian@saruman:~/circletech/src/Util/SigningManager> alsamixer

alsamixer: function snd_ctl_open failed for default: No such device

Takashi, any idea what can be wrong? I have never seen such problem...

It looks mostly like hal / resmgr issue.  Make sure that hal, resmgr, and hal-resmgr are properly installed, and relevant services are running.

Thanks Takashi!

Marian, please check the components mentioned in comment #14.

No feedback, resolving as INVALID

(you can reopen the bug and provide the needed information, see comment #14 and comment #15)