Bug 928167 - The latest update patch from pulseaudio breaks HDMI sound function on a X201 Lenovo with docking station
Summary: The latest update patch from pulseaudio breaks HDMI sound function on a X201 ...
Status: RESOLVED DUPLICATE of bug 928035
Alias: None
Product: openSUSE Distribution
Classification: openSUSE
Component: Sound (show other bugs)
Version: 13.2
Hardware: x86-64 openSUSE 13.2
: P5 - None : Major (vote)
Target Milestone: ---
Assignee: Takashi Iwai
QA Contact: E-mail List
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-04-22 11:56 UTC by Stakanov Schufter
Modified: 2015-04-22 11:59 UTC (History)
0 users

See Also:
Found By: ---
Services Priority:
Business Priority:
Blocker: ---
Marketing QA Status: ---
IT Deployment: ---


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Stakanov Schufter 2015-04-22 11:56:29 UTC
After installing patch RU-2015:071-1 did break completely the sound function on the following setup:

Lenovo X201 notebook
Lenovo Ultrabase dockingstation
HDMI sound over a Medion MD20666

Everything worked well with HDMI sound selected when on dockingstation and normal analog when on notebook only. 
Now after the update the HDMI as channel is not available. Sound is, if it is possible to configure the sound card (possible one time in two) only over the speakers of the machine. 
Channels are indicated correctly when in kmix, priority is set correctly but not respected. 
When selecting to set up for all channels the audio configuration this is not set and not respected and one has to do by hand. But then it has no effect on the problem. The different soundcard resources are shown only with no application running. When running e.g. kaffeine, reproduces over the notebookspeakers, and as channels in Kmix there is only "sound server pulseaudio". But that soundserver does not seem to respect the settings done in channels before. 

Shortly it is a mess. Up to the update everything went quite smooth.
Comment 1 Takashi Iwai 2015-04-22 11:59:09 UTC
The fix will be released soon.

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