Bug 553856 - Prefs disabled despite modules being present
Summary: Prefs disabled despite modules being present
Keywords:
Status: CLOSED DUPLICATE of bug 528557
Alias: None
Product: Fedora
Classification: Fedora
Component: paprefs
Version: 12
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Lennart Poettering
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-09 05:01 UTC by Phip
Modified: 2010-01-11 17:00 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-01-11 17:00:21 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Phip 2010-01-09 05:01:26 UTC
The checkboxes in paprefs I want to use are grayed out with an "Install..." button beside them, and clicking install does not help. Further, the modules it says I need to install are already present!

Examples:
- "Enable network access to local sound devices" requires module-esound-protocol-tcp.so and module-native-protocol-tcp.so, which are included with the main pulseaudio package, obviously installed.
- "Make discoverable PulseAudio network sound devices available locally" requires module-zeroconf-discover.so,
- "Allow other machines on the LAN to discover local sound devices" requires module-zeroconf-publish.so, both inside pulseaudio-module-zeroconf, which I have installed.

I have paprefs 0.9.9-4 and pulseaudio 0.9.21-2 installed.

I observe two unusual things that may be of help: first, when I click the install buttons beside the disabled checkboxes, they all list pulse-0.9.19 paths, despite my having pulse-0.9.21:

"The following file is required:
/usr/lib64/pulse-0.9.19/modules/module-zeroconf-discover.so" 

Second, and this may deliberate but for some reason I have both /usr/lib64/pulse-0.9.19 and /usr/lib64/pulse-0.9.21 directories, although yum tells me only 0.9.21 is installed.

Observed identically on both a ppc and a x86_64 machine.

Comment 1 Lennart Poettering 2010-01-11 17:00:21 UTC

*** This bug has been marked as a duplicate of bug 528557 ***


Note You need to log in before you can comment on or make changes to this bug.