FYI: Sound issue after recent update; 13.1 KDE

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|

FYI: Sound issue after recent update; 13.1 KDE

Rajko M.

openSUSE 13.1
KDE

Recent update killed my sound.

After some lost time with driver, KDE and YaST settings etc, I checked
mixer, and surprise, my onboard sound was muted and HDMI (not
connected) enabled.

It passed a lot of time since last time KDE tried to be smarter than
user. Setup script can't know what is connected and what not, and user
can't guess that setup has changed something that should not be changed.

In other words, if for any reason you have to rescan devices, please,
note that result is different from user settings and ask user what he
wants to do. It will save your users some frustration.

--
Regards, Rajko.
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: FYI: Sound issue after recent update; 13.1 KDE

Bernhard Voelker
On 06/21/2014 09:21 PM, Rajko wrote:
>
> openSUSE 13.1
> KDE
>
> Recent update killed my sound.
>
> After some lost time with driver, KDE and YaST settings etc, I checked
> mixer, and surprise, my onboard sound was muted and HDMI (not
> connected) enabled.

Thanks!
I experienced the same issue today .. and I remember the same thing
happen already about 2-3 weeks ago.  Maybe it's after every boot?

Have a nice day,
Berny
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]

Reply | Threaded
Open this post in threaded view
|

Re: FYI: Sound issue after recent update; 13.1 KDE

Patrick Shanahan-2
* Bernhard Voelker <[hidden email]> [06-21-14 17:17]:

> On 06/21/2014 09:21 PM, Rajko wrote:
> >
> > openSUSE 13.1
> > KDE
> >
> > Recent update killed my sound.
> >
> > After some lost time with driver, KDE and YaST settings etc, I checked
> > mixer, and surprise, my onboard sound was muted and HDMI (not
> > connected) enabled.
>
> Thanks!
> I experienced the same issue today .. and I remember the same thing
> happen already about 2-3 weeks ago.  Maybe it's after every boot?

I have also noticed this and more predominately of late.  Wrong device is
selected and w/o any user intervention.  And if memory serves, usually
after a reboot for a new kernel but please account for aged brain cells
(or those remaining)  :^).

--
(paka)Patrick Shanahan       Plainfield, Indiana, USA          @ptilopteri
http://en.opensuse.org    openSUSE Community Member    facebook/ptilopteri
http://wahoo.no-ip.org        Photo Album: http://wahoo.no-ip.org/gallery2
Registered Linux User #207535                    @ http://linuxcounter.net
--
To unsubscribe, e-mail: [hidden email]
To contact the owner, e-mail: [hidden email]