Sorry again wrong:

Actual Results:

No sound before unmute

Expected Results:

Sounds work when start

I have HDA NVidia on board sound and I'm experiencing something similar. After boot, KMix shows Master as being muted. Unmute and sound works fine. After reboot, the Master is muted again.

Same here using snd_hda_intel with an ABIT-supplied "Intel 82801I" controller

The message "ATI SB doesn't work" is a known problem, and it's actually mostly harmless and you can ignore it.  The sound backend should use the default anyway.  The problem is rather who muted the master volume.

Try to boot in runlevel 3 (add "3" to boot option), then login in linux console there without X.  Check whether the sound is muted, e.g. via alsamixer.  If muted, you must see "MM" in the corresponding (e.g. "Master") volume control.  Then, run alsa-info.sh with --no-upload option, and attach the generated file.

If it was muted, unmute it, then once reboot again with runlevel 3 to check whether the unmuted status is saved properly.

After checking the mute status at the system level, try to login on X, either run "init 5" or just reboot.  Check the mute status again.

Created attachment 290184 [details]
alsa-info.txt without mute

When I rebooted with runlevel 3 sounds are not muted default. If I mute it, sounds are muted and if I unmute and reboot sounds are unmuted. So problem is in runlevel 5.

Created attachment 290185 [details]
alsa-info muted

I muted sounds and run script on runlevel 3

Created attachment 290187 [details]
alsa-info with X, so it's muted with every reboot

After I have unmuted sounds I changed runlevel with telinit to 5 and sounds are now muted. Some days ago I tried to run "alsactl store" as root and I set sounds unmuted. When I log out and log in I got rare messages from xterm. I can do it again and write messages here if you want.

Hello.

I am getting this bug too. Different hardware to what has been reported to date. Happy to help if I can.

Cheers
Steve

P.S. Can't find this bug reported at KDE.

I think this is a problem with pulseaudio or related application/library as I have completely removed pulseaudio and this problem has gone away (ie. I am using base alsa layer directly).

The same bug here. And the sound goes muted just after KMix is started.
At boot time the sound driver is loaded correctly and the sound works fine. However, when KDE starts, the sound goes muted just after the start of KMix.

Hardware:

82801G (ICH7 Family) High Definition Audio Controller
Configured as sound card number 0
Driver snd-hda-intel

Same within VirtualBox. KMix is muted on every login but works just fine once it gets unmuted.

Also it gets muted again if one logs out & in again into KDE.

If it happens in virtualbox, it means a software issue independent from the driver.  I guess it's PA, too.

Scott, any clue?

It would be helpful to see if this occurs whenever pulse is started or just on reboot. Could you
1. unmute sound, quit all apps playing sound.
2. "pulseaudio -k"  - shutdown the pulse daemon
3. "pulseaudio -v"  - run the daemon verbose

does the sound get muted again? If so could you attach the verbose output from step #3.

Created attachment 296419 [details]
PA log

Did the requested steps - see the attached log for details.

FWIW: Everytime I unmute the sound & log out of KDE and log in again the sound is muted again. Therefore it might be some KDE problem (or is anyone of the above commenters running Gnome / non KDE?).

My apologies, I forgot to add the mute state.

After executing the requested commands the sound isn't muted but works just fine.

How to reproduce this:

Simply install current Factory within VirtualBox and try it.

I did the pulseaudio commands also. Sound remains unmuted. I will post the output if you need one in addition to comment #15.

Still muted in Milestone 3

Just submitted an update for pulseaudio to Factory that should fix this. It will probably take awhile to sync out as Factory build is quite loaded right now.  Could you test this new version (or try in Milestone 4). Make sure your pulseaudio changelog has the entry for Jul 10 2009 in it and restart pulse once you upgrade.

It's been ten days since comment #19 was posted and I still don't see anything in the repo. Will it be at download.opensuse.org/factory/repo/oss?

I installed pulseaudio-0.9.15-3.1 in Milestone 4. Sound is still muted at boot.

After running the commands from comment #14, sound remains unmuted.

Created attachment 309819 [details]
debug log

Yeah, there is still a problem.  After debugging into this some more I find that when the session is being torn down at shutdown, pulse tries to query the alsa mute state via snd_mixer_selem_get_playback_switch().  This appears to incorrectly indicate a muted state. pulse then stores that muted value in it's restore database and then next time it starts up it mutes the sound.

I will look at this more when I get back in a week.
Meanwhile, Takashi - do you have any hints, does the attached debug log give any clues.

My rough guess is that pulseaudio is still alive at shutdown even after the alsasound init script mutes the output to avoid the click noise at power down on laptops.

When the system goes to the runlevel 6 or 0, the alsasound init script doesn't kill the processes by itself because the system will do it anyway.  But, now pulseaudio is killed after this mute.  This is likely how the problem occurs.

Please try the packages on OBS home:tiwai:branches:multimedia:libs/alsa repo.
  http://download.opensuse.org/repositories/home:/tiwai:/branches:/multimedia:/libs/

Does the mute still happen after reboot?

I installed the recommended packages and sound is still muted at boot. I just updated today to Milestone 5.

Make sure that alsa.rpm, specially /etc/init.d/alsasound was updated.
Check "rpm -q alsa --changelog | head" output.  The latest one should be
  - Fix PA mute problem after reboot (bnc#499445)

After checking it, try the following:

- unmute on X
- logout, go to linux console via ctrl+alt+F1, login as root
- go to runlevel 3
  # init 3
- kill remaining PA processes to be sure
  # killall pulseaudio
- check the mixer status, e.g. run alsamixer.
  if it's muted, unmute manually
- run "/usr/sbin/alsactl store"
- reboot
- check the mute status again

If the mute still appears, try to uncomment the line calling "mute_system" in /etc/init.d/alsasound script.  Then do again the procedure above.

I installed the recommended version af alsa and followed the steps above. Sound has remained unmuted through three reboots. I'm using Milestone 5. However, there is no start up or shut down sound. 

I'll report back if sound turns up muted at some later time.

Hmm, do other system sounds work properly?

Is this the same as bug 520426?

(In reply to comment #28)
> I installed the recommended version af alsa and followed the steps above. Sound
> has remained unmuted through three reboots. I'm using Milestone 5. However,
> there is no start up or shut down sound. 

If notifications do not work for you in KDE, check whether installing
phonon-xine-backend solves it. There are issues with gstreamer! (bug 440786)

Actually, it's phonon-backend-xine and it's already installed. I'm not sure which apps or utilities have system sounds, but along with no start up or shut down sounds, there's no beep when using ctrl>alt>del.

There's also no chime when using the halt command in the cli like there is in 11.1. The sound test in system settings works with phonon output device selected.

The beep thing might be be a different issue.  Depending on the hardware, the beep signal can be hooked through the sound codec chip when the chip is initialized, and you won't hear beep unless you adjust the proper mixer volume.  This is a feature and no bug.

Check other "normal" sound playback like audio file playback.  Do you get any sounds at all?  If yes, the system-sound issue is basically irrelevant with this bug report.  Please open another bug report.  In this bug, we handle only the problem of "mute after reboot".

solved kde + pulseaudo + kmix  muted problem: do not disable the "Master" Channel, even if it does nothing. But sure you can select another channel for sliding.

Now the fix is already in FACTORY, so let's close this bug.
The KDE system sound is another issue that is irrelevant with this original bug.
Please create an appropriate bug entry.