Bug 10068

Summary:	Kmix main channel should be set to highest priority audio device
Product:	Mageia	Reporter:	Morgan Leijström <fri>
Component:	RPM Packages	Assignee:	Mageia Bug Squad <bugsquad>
Status:	RESOLVED OLD	QA Contact:
Severity:	normal
Priority:	Normal	CC:	balcaen.john, lmenut, mageia, mageia
Version:	3
Target Milestone:	---
Hardware:	All
OS:	Linux
Whiteboard:
Source RPM:		CVE:
Status comment:
Attachments:	Screenshot: KDE asks to hide the audiodevice currently working.

Description Morgan Leijström 2013-05-12 02:13:53 CEST

I had sound, right from install but the volume control was not working.

I had to right click it and select "Choose main channel..." (translated)
and switch it from mu video card HDMI to "Built-in Audio"
Very simple once you think of where to look...

Looking in (translated)
  KDE settings > Hardware > Phonon > Device_settings
I see the Built-in Audio have higher priority than Barts HDMI Audio (Graphic card)

I think Kmix should default to use the prioritised device.

Version: of what? This is a network install from may 5.

Reproducible: 

Steps to Reproduce:

Comment 1 Morgan Leijström 2013-05-13 10:03:35 CEST

Weird: after one reboot it again had got set, and when i tried to open dialog to again set Kmix to use main board audio, i got a message that KDE have detected the unit have been removed and asked me if i wanted to hide it permanently.
(Of course i answered no)
Without rebooting i could use the other KDE settings panel in background of screenshot to sucessfully generate a test sound on the built in mainboard audio...
So KDE is a bit scizzofrenic here...
Since then I have set Kmix to use Built-in, rebooted a few times, and it so fr remember my setting.

But somtimes/rarely it seems that KDE thinks it is not working and automatically set Kmix to secondary audio device...?

Comment 2 Morgan Leijström 2013-05-13 10:04:57 CEST

Created attachment 3957 [details]
Screenshot: KDE asks to hide the audiodevice currently working.

Manuel Hiebel 2013-05-28 21:51:03 CEST

CC: (none) => balcaen.john, lmenut, nicolas.lecureuil
Component: Installer => RPM Packages
Version: Cauldron => 3

Manuel Hiebel 2013-05-28 21:53:31 CEST

CC: (none) => mageia

Comment 3 Colin Guthrie 2013-05-29 09:53:46 CEST

This isn't really something to track downstream. I'm not personally hacking much on kmix these days and actually that dialog you see in comment 2 doesn't even come from kmix anyway but some other bits of KDE.

I should spend some time and tidy it up again at some point but right now I've not really got the time.

Upstream, kmix has had a good tidy up and thus it might make it tolerable to hack on again at some point in the future. When that lands I'll maybe take a look.

But to be perfectly honest, I doubt having this bug open here will do much...

Comment 4 Morgan Leijström 2013-05-29 14:26:07 CEST

OK i understand.
So set it UPSTREAM & WONTFIX?

Actually it have survived latest X crashes (Bug 10165) without needing manual correction so it *might* have been fixed by some KDE update already.

Comment 5 Colin Guthrie 2013-05-29 16:14:34 CEST

I don't think any KDE update addresses this but who knows!

Comment 6 Marja Van Waes 2015-03-31 16:06:50 CEST

Mageia 3 changed to end-of-life (EOL) status 4 months ago.
http://blog.mageia.org/en/2014/11/26/lets-say-goodbye-to-mageia-3/ 

Mageia 3 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of Mageia
please feel free to click on "Version" change it against that version of Mageia
and reopen this bug.

Thank you for reporting this bug and we are sorry it could not be fixed.

--
The Mageia Bugsquad

Status: NEW => RESOLVED
Resolution: (none) => OLD