Hello all,
I just installed F12 on my private workstation, and upgrade the "built-in" KDE to 4.3.4 from kde-redhat unstable (x86_64, some i686 libs taken from the i386 repo). Login, logout, and no more sound. By looking at the control center, I can see that KDE only sees the Pulseaudio sound server (instead of Pulse + on-board HDA Intel (alsa) + SB Audigy 2 (alsa) and USB microphone (USB camera). Far worse, when I try to test the pulse audio server (from the control center), I get a "Pulse audio server not responding - falling back to (empty).".
Trying to access the pulse server from pavucontrol or mplayer (-ao pulse), seems to work OK, so it doesn't look like a pulse problem.
I moved to init 1, killed all the user-mode services, cleaned /tmp and /var/tmp and switched back to init 5, with no effect.
Switching backends from xine to gstreamer, had little effect.
Any ideas?
$ rpm -qa | egrep 'pulse|phonon' | sort phonon-4.3.80-2.fc12.i686 phonon-4.3.80-2.fc12.x86_64 phonon-backend-gstreamer-4.3.80-2.fc12.i686 phonon-backend-gstreamer-4.3.80-2.fc12.x86_64 phonon-backend-xine-4.3.80-2.fc12.i686 phonon-backend-xine-4.3.80-2.fc12.x86_64 phonon-devel-4.3.80-2.fc12.x86_64 pulseaudio-0.9.21-1.fc12.x86_64 pulseaudio-esound-compat-0.9.21-1.fc12.x86_64 pulseaudio-gdm-hooks-0.9.21-1.fc12.x86_64 pulseaudio-libs-0.9.21-1.fc12.i686 pulseaudio-libs-0.9.21-1.fc12.x86_64 pulseaudio-libs-devel-0.9.21-1.fc12.x86_64 pulseaudio-libs-glib2-0.9.21-1.fc12.i686 pulseaudio-libs-glib2-0.9.21-1.fc12.x86_64 pulseaudio-libs-zeroconf-0.9.21-1.fc12.x86_64 pulseaudio-module-bluetooth-0.9.21-1.fc12.x86_64 pulseaudio-module-gconf-0.9.21-1.fc12.x86_64 pulseaudio-module-x11-0.9.21-1.fc12.2.rex.x86_64 pulseaudio-utils-0.9.21-1.fc12.x86_64 wine-pulseaudio-1.1.32-1.fc12.i686
- Gilboa
Gilboa Davara wrote:
Hello all,
I just installed F12 on my private workstation, and upgrade the "built-in" KDE to 4.3.4 from kde-redhat unstable (x86_64, some i686 libs taken from the i386 repo). Login, logout, and no more sound. By looking at the control center, I can see that KDE only sees the Pulseaudio sound server (instead of Pulse + on-board HDA Intel (alsa) + SB Audigy 2 (alsa) and USB microphone (USB camera).
that's expected, see also, http://colin.guthr.ie/2009/10/so-how-does-the-kde-pulseaudio-support-work- anyway/
Far worse, when I try to test the pulse audio server (from the control center), I get a "Pulse audio server not responding - falling back to (empty).".
Boo, obviously PA has gotten confused/wonky. reboot?
-- Rex
On Thu, 2009-12-17 at 07:45 -0600, Rex Dieter wrote:
Gilboa Davara wrote:
Hello all,
I just installed F12 on my private workstation, and upgrade the "built-in" KDE to 4.3.4 from kde-redhat unstable (x86_64, some i686 libs taken from the i386 repo). Login, logout, and no more sound. By looking at the control center, I can see that KDE only sees the Pulseaudio sound server (instead of Pulse + on-board HDA Intel (alsa) + SB Audigy 2 (alsa) and USB microphone (USB camera).
that's expected, see also, http://colin.guthr.ie/2009/10/so-how-does-the-kde-pulseaudio-support-work- anyway/
Is it something -very- new? I mean, I never saw it before. (Both KDE 4.3.3 under F11 and KDE 4.3.3 under F12 gave me the full list of devices, including non-PA ones...)
Far worse, when I try to test the pulse audio server (from the control center), I get a "Pulse audio server not responding - falling back to (empty).".
Boo, obviously PA has gotten confused/wonky. reboot?
Gaaah.... Reboot? It's very weird, if it indeed it was a PA problem, neither mplayer, nor skype (...) would have worked.
... Plus, I killed PA and ran it under gdb in a console, it nothing looks out of the ordinary.
-- Rex
- Gilboa
Gilboa Davara wrote:
On Thu, 2009-12-17 at 07:45 -0600, Rex Dieter wrote:
Gilboa Davara wrote:
Hello all,
I just installed F12 on my private workstation, and upgrade the "built-in" KDE to 4.3.4 from kde-redhat unstable (x86_64, some i686 libs taken from the i386 repo). Login, logout, and no more sound. By looking at the control center, I can see that KDE only sees the Pulseaudio sound server (instead of Pulse + on-board HDA Intel (alsa) + SB Audigy 2 (alsa) and USB microphone (USB camera).
that's expected, see also, http://colin.guthr.ie/2009/10/so-how-does-the-kde-pulseaudio-support-
work-
anyway/
Is it something -very- new? I mean, I never saw it before. (Both KDE 4.3.3 under F11 and KDE 4.3.3 under F12 gave me the full list of devices, including non-PA ones...)
Yes, new as of our kde-4.3.4 builds (this same support is/will-be in kde-4.4 upstream).
You should also get the full list of real devices if you have the PA device- manager module loaded. If this isn't available, you'll now only is PulseAudio. The logic being if PulseAudio is loaded, none of the other devices are available or usable anyway, so why bother to display them?
This is all outlined/explained in Colin Guthrie's recent blogs on the topic.
-- Rex
Petrus de Calguarium wrote:
I have yum searched for this device manager, after following both this thread and Colin Guthrie's very informative series of articles, but I have been unable to locate this package.
What is is it called?
It's included in the latest pulseaudio build: https://admin.fedoraproject.org/updates/pulseaudio-0.9.21-2.fc12 The build is also mirrored in kde-redhat testing (so you don't have to wait for the push).
Kevin Kofler
Kevin Kofler wrote:
in kde-redhat testing
I got them all, installed and rebooted.
Before the update, I had pulseaudio and only pulseaudio in the sound and video configuration/device preference for both audio output and audio capture.
Now, after the update, I have internal audio analog sound 4.0 and Internal Audio Analog Stereo for audio output and capture respectively.
Now, didn't Colin's articles this morning state that with this new device-manager one is supposed to have all of the audio out-/inputs if pulseaudio is present and only one in the case that pulseaudio is not enabled? I definitely have pulseaudio, ans I previously had it and just updated.
On 12/17/2009 07:06 PM, Petrus de Calguarium wrote:
Kevin Kofler wrote:
in kde-redhat testing
I got them all, installed and rebooted.
Before the update, I had pulseaudio and only pulseaudio in the sound and video configuration/device preference for both audio output and audio capture.
Now, after the update, I have internal audio analog sound 4.0 and Internal Audio Analog Stereo for audio output and capture respectively.
I have Internal Audio Analog Stereo for both output and capture.
Now, didn't Colin's articles this morning state that with this new device-manager one is supposed to have all of the audio out-/inputs if pulseaudio is present and only one in the case that pulseaudio is not enabled?
Depends on how you interpret what he is saying. I thought that without module-device-manager you would only see one entry like "Pulse Audio Server" (which I did see before). With module-device-manager you see what you see now.
I definitely have pulseaudio,
ans I previously had it and just updated.
fedora-kde mailing list fedora-kde@lists.fedoraproject.org https://admin.fedoraproject.org/mailman/listinfo/fedora-kde New to KDE4? - get help from http://userbase.kde.org
Yeah, ok. I guess I get it. I thought I was supposed to see the different streams, like alsa, built-in digital, built-in analog, etc., or perhaps even different audio applications, so that one can separately and independently set the volume for each, like pulseaudio is touted to do.
Yes, I have only one sound card attached at present, the one on the main board and no pci one, and I configured it with Lennart a few months back to get 4-speaker stereo sound when we were debugging a problem. Luckily this update didn't change that, but I believe the problem turned out to be an alsa, not a pulseaudio, one.
Petrus de Calguarium wrote:
Kevin Kofler wrote:
in kde-redhat testing
I got them all, installed and rebooted.
Before the update, I had pulseaudio and only pulseaudio in the sound and video configuration/device preference for both audio output and audio capture.
Now, after the update, I have internal audio analog sound 4.0 and Internal Audio Analog Stereo for audio output and capture respectively.
Now, didn't Colin's articles this morning state that with this new device-manager one is supposed to have all of the audio out-/inputs if pulseaudio is present and only one in the case that pulseaudio is not enabled? I definitely have pulseaudio, ans I previously had it and just updated.
Apparently you have only one sound "card" (the onboard sound chip), so obviously only that one is shown.
Kevin Kofler
On Thu, 2009-12-17 at 10:17 -0600, Rex Dieter wrote:
Gilboa Davara wrote:
Yes, new as of our kde-4.3.4 builds (this same support is/will-be in kde-4.4 upstream). You should also get the full list of real devices if you have the PA device- manager module loaded. If this isn't available, you'll now only is PulseAudio. The logic being if PulseAudio is loaded, none of the other devices are available or usable anyway, so why bother to display them?
OK. Switched to the latest PA from updates-testing - I can see the d-m-d .so module - but do I enable it? (Google didn't really return anything - neither did the blog)
This is all outlined/explained in Colin Guthrie's recent blogs on the topic.
Read it. Still no sound :(
- Gilboa
Gilboa Davara wrote:
On Thu, 2009-12-17 at 10:17 -0600, Rex Dieter wrote:
Gilboa Davara wrote:
Yes, new as of our kde-4.3.4 builds (this same support is/will-be in kde-4.4 upstream). You should also get the full list of real devices if you have the PA device- manager module loaded. If this isn't available, you'll now only is PulseAudio. The logic being if PulseAudio is loaded, none of the other devices are available or usable anyway, so why bother to display them?
OK. Switched to the latest PA from updates-testing - I can see the d-m-d .so module - but do I enable it? (Google didn't really return anything - neither did the blog)
pactl list | grep device-manager
will output something if it is loaded. It gets autoloaded by /etc/xdg/autostart/pulseaudio-kde.desktop
Can manually do so by running /usr/bin/start-pulseaudio-kde
This is all outlined/explained in Colin Guthrie's recent blogs on the topic.
Read it. Still no sound :(
That's likely unrelated to pa device-manager
-- Rex
On Fri, 2009-12-18 at 09:35 -0600, Rex Dieter wrote:
Gilboa Davara wrote:
On Thu, 2009-12-17 at 10:17 -0600, Rex Dieter wrote:
Gilboa Davara wrote:
Yes, new as of our kde-4.3.4 builds (this same support is/will-be in kde-4.4 upstream). You should also get the full list of real devices if you have the PA device- manager module loaded. If this isn't available, you'll now only is PulseAudio. The logic being if PulseAudio is loaded, none of the other devices are available or usable anyway, so why bother to display them?
OK. Switched to the latest PA from updates-testing - I can see the d-m-d .so module - but do I enable it? (Google didn't really return anything - neither did the blog)
First, thanks for the help :)
pactl list | grep device-manager
OK. module seems to be active.
$ pactl list | grep device-manager Name: module-device-manager
will output something if it is loaded. It gets autoloaded by /etc/xdg/autostart/pulseaudio-kde.desktop
Can manually do so by running /usr/bin/start-pulseaudio-kde
This is all outlined/explained in Colin Guthrie's recent blogs on the topic.
Read it. Still no sound :(
That's likely unrelated to pa device-manager
I'm lost. The problem is KDE only. (I restarted pulse using start-pulseaudio-kde) mplayer works, skype works, VLC works... everything except phonon works.
What's the next step?
Thanks, - Gilboa
Gilboa Davara wrote:
I'm lost. The problem is KDE only. (I restarted pulse using start-pulseaudio-kde) mplayer works, skype works, VLC works... everything except phonon works.
What's the next step?
Do you also have phonon-4.3.80 from updates-testing or kde-testing? You should.
Kevin Kofler
On Sat, 2009-12-19 at 07:24 +0100, Kevin Kofler wrote:
Gilboa Davara wrote:
I'm lost. The problem is KDE only. (I restarted pulse using start-pulseaudio-kde) mplayer works, skype works, VLC works... everything except phonon works.
What's the next step?
Do you also have phonon-4.3.80 from updates-testing or kde-testing? You should.
Yep.
$ rpm -qa | grep phonon | sort phonon-4.3.80-2.fc12.i686 phonon-4.3.80-2.fc12.x86_64 phonon-backend-gstreamer-4.3.80-2.fc12.i686 phonon-backend-gstreamer-4.3.80-2.fc12.x86_64 phonon-backend-xine-4.3.80-2.fc12.i686 phonon-backend-xine-4.3.80-2.fc12.x86_64 phonon-devel-4.3.80-2.fc12.x86_64
- Gilboa
Gilboa Davara wrote:
I'm lost. The problem is KDE only. (I restarted pulse using start-pulseaudio-kde) mplayer works, skype works, VLC works... everything except phonon works.
What's the next step?
Is xine-lib-pulseaudio installed? It should be (at least until we move it into the main xine-lib package). It's missing on the live image which is the cause of most F12 KDE sound issues.
Kevin Kofler
On Sat, 19 Dec 2009 17:49:08 +0100, Kevin Kofler kevin.kofler@chello.at wrote:
Gilboa Davara wrote:
I'm lost. The problem is KDE only. (I restarted pulse using start-pulseaudio-kde) mplayer works, skype works, VLC works... everything except phonon
works.
What's the next step?
Is xine-lib-pulseaudio installed? It should be (at least until we move
it
into the main xine-lib package). It's missing on the live image which is the cause of most F12 KDE sound issues.
Kevin Kofler
Gilboa, you're not alone on this one. I'm having the exact same problem on my desktop pc here at home.
Latest Phonon, PulseAudio and xine stuff installed here (including xine-lib-pulseaudio). Checked against the kde-* repo's and updates-testing.
On a side note, I'm using a preupgraded F11 Live KDE -> F12 here which was working fine pré KDE 4.3.4. :)
On an other side note, this might be worth mentioning too:
<rdieter> in pavucontrol's playback tab, you should see amarok, with an animated volume shown <Kaboon> erm, it's empty except for "System sounds" <rdieter> ok, so phonon isn't using pulseaudio... for somereason. ??
and Rex had to leave.
I guess this one is out of my league so if you guys want me to have something changed / tested just let me know and I'll see what I can do. :)
On Sat, 2009-12-19 at 17:49 +0100, Kevin Kofler wrote:
Gilboa Davara wrote:
I'm lost. The problem is KDE only. (I restarted pulse using start-pulseaudio-kde) mplayer works, skype works, VLC works... everything except phonon works.
What's the next step?
Is xine-lib-pulseaudio installed? It should be (at least until we move it into the main xine-lib package). It's missing on the live image which is the cause of most F12 KDE sound issues.
Kevin Kofler
That solved it. Thanks! xine-lib-pulseaudio was missing.
Missing Require: in the phonon spec?
- Gilboa
On 12/19/2009 10:44 PM, Gilboa Davara wrote:
On Sat, 2009-12-19 at 17:49 +0100, Kevin Kofler wrote:
Gilboa Davara wrote:
I'm lost. The problem is KDE only. (I restarted pulse using start-pulseaudio-kde) mplayer works, skype works, VLC works... everything except phonon works.
What's the next step?
Is xine-lib-pulseaudio installed? It should be (at least until we move it into the main xine-lib package). It's missing on the live image which is the cause of most F12 KDE sound issues.
Kevin KoflerThat solved it. Thanks! xine-lib-pulseaudio was missing.
Missing Require: in the phonon spec?
Basically yeah, we're using this to address it:
https://admin.fedoraproject.org/updates/xine-lib-1.1.16.3-5.fc12
-- Rex
On Sat, 2009-12-19 at 23:45 -0600, Rex Dieter wrote:
On 12/19/2009 10:44 PM, Gilboa Davara wrote:
On Sat, 2009-12-19 at 17:49 +0100, Kevin Kofler wrote:
Gilboa Davara wrote:
I'm lost. The problem is KDE only. (I restarted pulse using start-pulseaudio-kde) mplayer works, skype works, VLC works... everything except phonon works.
What's the next step?
Is xine-lib-pulseaudio installed? It should be (at least until we move it into the main xine-lib package). It's missing on the live image which is the cause of most F12 KDE sound issues.
Kevin KoflerThat solved it. Thanks! xine-lib-pulseaudio was missing.
Missing Require: in the phonon spec?
Basically yeah, we're using this to address it:
https://admin.fedoraproject.org/updates/xine-lib-1.1.16.3-5.fc12
-- Rex
OK, thanks.
- Gilboa
On Sat, 2009-12-19 at 23:45 -0600, Rex Dieter wrote:
On 12/19/2009 10:44 PM, Gilboa Davara wrote:
On Sat, 2009-12-19 at 17:49 +0100, Kevin Kofler wrote:
Gilboa Davara wrote:
I'm lost. The problem is KDE only. (I restarted pulse using start-pulseaudio-kde) mplayer works, skype works, VLC works... everything except phonon works.
What's the next step?
Is xine-lib-pulseaudio installed? It should be (at least until we move it into the main xine-lib package). It's missing on the live image which is the cause of most F12 KDE sound issues.
Kevin KoflerThat solved it. Thanks! xine-lib-pulseaudio was missing.
Missing Require: in the phonon spec?
Basically yeah, we're using this to address it:
https://admin.fedoraproject.org/updates/xine-lib-1.1.16.3-5.fc12
-- Rex
Spoke too soon. Updated to the latest xine, pulse crashed (... no abrt), and I reverted to the old "Pulseaudio Sound Server" only mode.
On the up side, once I started pulse in console, this sink was capable of playing sound (both using the test button and by from amarok), but I could not longer manage to devices from the control center.
Is the intended behavior? (According to blog, I should be seeing all the possible pulse devices in the control center...)
- Gilboa
On 12/20/2009 11:51 AM, Gilboa Davara wrote:
Spoke too soon. Updated to the latest xine, pulse crashed (... no abrt), and I reverted to the old "Pulseaudio Sound Server" only mode.
On the up side, once I started pulse in console, this sink was capable of playing sound (both using the test button and by from amarok), but I could not longer manage to devices from the control center.
Is the intended behavior? (According to blog, I should be seeing all the possible pulse devices in the control center...)
You see the devices if the "device-manager" module is loaded, which is included in the script /usr/bin/start-pulseaudio-kde
-- Rex
On Sun, 2009-12-20 at 12:29 -0600, Rex Dieter wrote:
On 12/20/2009 11:51 AM, Gilboa Davara wrote:
Spoke too soon. Updated to the latest xine, pulse crashed (... no abrt), and I reverted to the old "Pulseaudio Sound Server" only mode.
On the up side, once I started pulse in console, this sink was capable of playing sound (both using the test button and by from amarok), but I could not longer manage to devices from the control center.
Is the intended behavior? (According to blog, I should be seeing all the possible pulse devices in the control center...)
You see the devices if the "device-manager" module is loaded, which is included in the script /usr/bin/start-pulseaudio-kde
-- Rex
Ugggh... Sorry, yeah. You already told me that. My brain seems to be off today.
Restart pulse, the -right- way (read: start-pulseaudio-kde), and all the devices are accounted for. (Actually, once device is missing from the record list, but this is mostly a pulse-only issue)
Thanks again. (And sorry for being a pest :)) - Gilboa
-
Eelko Berkenpies -
Gilboa Davara -
Kevin Kofler -
Patrick Boutilier -
Petrus de Calguarium -
Rex Dieter