I found two things there. I found “Notification Sounds” (set to 0%),
and I found “virt-manager: playback” set to 73%.
I happened to be running “virt-manager”. If I were not running that, then I would have only had “Notification Sounds”. And if I had disabled notification sounds, then it would not be surprising if there was nothing there.
So I started playing some music with Amarok. And that immediately showed up in the Audio Volume window.
So my question: were you actually playing any sounds at the time you opened the audio volume window?
The symptoms of no ‘Audio Hardware Setup’ would be consistent with the pulseaudio daemon not running. A bit confusing though, since earlier you reported that it was running. What happens if you try launching it manually from a terminal (as user) like this?
then check the KDE System Settings > Hardware > Multimedia > Audio and Video again
Enabling PulseAudio for ALSA...
Enabling PulseAudio for libao...
Default driver is pulse already in /etc/libao.conf
Enabling PulseAudio for mplayer...
Enabling PulseAudio for OSS...
Application aumix already setup for PulseAudio
Application sox already setup for PulseAudio
Enabling PulseAudio for SDL...
Enabling PulseAudio for Timidity...
Timidity already setup for using PulseAudio
Enabling PulseAudio for Phonon...
Enabling PulseAudio for Kmix...
Enabling PulseAudio for speech dispatcher...
Enabling PulseAudio for SoX...
Setting auto sink/src for gstreamer
Enabling PulseAudio for QEMU/KVM
Enabling PulseAudio autospawn...
E: [pulseaudio] main.c: Failed to kill daemon: No such process
solves the problem but that doesn’t stick after logging out and back in again.
No, it won’t be persistent, I just wanted to know if it would start for the new user. In general if pulse-audio is enabled already, then when you switch user there should be another instance of the daemon for that user. For reference I get…
I’m not sure why PulseAudio is not started for your second user account, but one possible workaround would be to make it autostart at login via
System Settings > Startup and Shutdown > Autostart > Add Program…, then type ‘pulseaudio’, select the ‘Application’ tab and ensure that the command is ‘pulseaudio -D’, then click ‘OK’. That should be all that’s required. It will take effect when you next login as this user.
Log out and log in didn’t work yesterday. But after booting the computer today, it seems to have worked. Weird.
Another weird thing: the problem remains when logging into my root account so I ran the above command. Again, logging out and logging in did nothing, but I expect it will work after booting the computer tomorrow.
I always use a fresh user account to make sure everything works fine. This differentiates between (a) real problems and (b) problems that occur because of old configuration files.
Anyway, decided to make another fresh user account to make sure it creates a functioning user account. AND IT DID !!! The problem seems to be solved.
I think, with hindsight, that the problem started with the installation procedure not configuring my sound card. Thus pulseaudio probably couldn’t create a proper set-up. Configuring my sound card made the sound work, but did nothing for the pulseaudio set-up. It had to be run again. At least that’s my amateur perspective on it.
This works in my user accounts. The pulseaudio daemon restarts. Everything works.
Why doesn’t this work from the root account? Because then I have to use
each time. It’s weird that I can configure the sound card, perform the updates, add Packman and install the packages for multimedia, yet be unable to make the pulseaudio daemon persistent in the root account.