Description of problem: KDE has detected that one or more internal audio devices had been elimiated. Would you like KDE to forget about this devices?. This is the list of devices that KDE belives that should be eliminated: Capture: C-Media USB Audio Device (USB Audio) Capture: C-Media USB Audio Device (USB Audio) Capture: USB Device 0x46d:0x807 (USB Audio) Capture: USB Device 0x46d:0x807 (USB Audio) Output: C-Media USB Audio Device (USB Audio) Output: C-Media USB Audio Device (USB Audio This problem everytime I disconnect my C-Media USB headset. It worked most of the time with Mageia 1, but with Mageia 2 Cauldron Alpha 1 it stop working. I cannot change the audio devices on system settings / phonon system preferences The only way to make my headset work is using pavucontrol. Version-Release number of selected component (if applicable): System Preferences 1.0 - KDE4 4.7.3 How reproducible: Steps to Reproduce: 1.Reconnect C-Media USB headset 2. 3.
Yeah Phonon platform plugin has a nasty habit of doing this... I need to find a way to kill it. You can pretty much totally ignore those messages. I'm more interested in finding out why you cannot change the device order in system settings/phonon settings. What devices are listed there? Do you see both your built in card and your USB headset listed? If in doubt, attach a screenshot. Also please indicate which application you are wanting to move. Phonon works on categories so we have to make sure you adjust the correct categories priority list.
CC: (none) => mageia
Keywords: (none) => NEEDINFOSource RPM: (none) => phonon
@ Ezequiel Please reply to the questions above within two weeks from now, to avoid this bug being closed as OLD.
CC: (none) => marja11
Since there are insufficient details provided in this report for us to investigate the issue further, and we have not received feedback to the information we have requested above, we will assume the problem was not reproducible, or has been fixed in one of the updates we have released for the reporter's distribution. Users who have experienced this problem are encouraged to upgrade to the latest update of their distribution, and if this issue turns out to still be reproducible in the latest update, please reopen this bug with additional information. Closing as OLD.
Status: NEW => RESOLVEDResolution: (none) => OLD