Upgrade from Mageia 5 where phonon was already set to use the default (ALSA) backend and PulseAudio was disabled.
PulseAudio is still disabled, but trying to play something in Amarok didn't work. Trying to go through Amarok's configuration (Playback) to access Phonon configuration results in Amarok freezing.
Phonon configuration can be accessed through systemsettings (though it's slow to start) and backend setting fixed.
Previous Mageia versions handled this correctly IIRC.
Once the configuration was fixed and I logged out and back in, Amarok was set to 0% volume, so I had to change that to 100% to hear it playing anything.
Amarok seems to reset itself to 0% at every log in. Not sure if this is Amarok or Phonon's fault.
is the sound to 0% only in amarok ? or in plasma-pa too ?
As I just told on the dev@ mailing list, I'm moving this bug report to the "Intended for Mageia 6" list because it does not strictly qualify for Release Blocker.
Setting back to release blocker, as this may not be totally fixable after release. Once a user has logged into Plasma once, the setting may persist in their profile. It's also at that point not going to be obvious how to fix it, especially given the difficulty of accessing the setting.
(In reply to Nicolas Lécureuil from comment #3)
> is the sound to 0% only in amarok ? or in plasma-pa too ?
If that 0% sound only affects Amarok, it would be better to keep it out of the scope of this issue (maybe open a new one). This issue should focus only on preserving the Phonon backend configured in KDE4 when upgrading to Plasma 5.
(In reply to Rémi Verschelde from comment #6)
> If that 0% sound only affects Amarok, it would be better to keep it out of
> the scope of this issue (maybe open a new one). This issue should focus only
> on preserving the Phonon backend configured in KDE4 when upgrading to Plasma
David, can you confirm if it only affects Amarok or also other applications?
I need to do a fresh test, hopefully this weekend, but the incorrect phonon setting is a global thing.
can you report this upstream please ?
Changing from release blocker to a "for errata" bug, see the council meeting logs.
@ David Walser
Do you mind adding it to the errata, or proposing a text for the errata here?
Report what upstream? Our own tools set the sound configuration and pulse vs. no-pulse. They should be fixing this so that KDE/Phonon doesn't default to Pulse when it has been disabled.
I suppose the part where the Configure Phonon button in Amarok essentially doesn't work could be reported to their developers.
This is a pretty serious issue, and it shouldn't matter that Pulse disabled isn't our "default," it's a supported and very common configuration. Isn't there anything that can be done about this issue?
As far as an errata text, it would read something like this:
"Users that have PulseAudio disabled will need to correct a misconfiguration in Phonon's audio settings. The setting can be accessed through System Settings > Multimedia > Audio and Video. Under Audio Playback, Default should be moved to the top of the Audio Playback Device Preference list for each category."
Speaking of which, it's not intuitive how to even do that, as there's no up/down buttons. Apparently you have to drag it up (which took a few tries for it to work). I also just noticed that you have to fix it for each of six (!) different categories. That also confirms that this affects a LOT more than just Amarok.
Please test new PA ( pushed in both mga6 and cauldron ).
It fixes https://bugs.kde.org/show_bug.cgi?id=324975
(In reply to Nicolas Lécureuil from comment #12)
> Please test new PA ( pushed in both mga6 and cauldron ).
> It fixes https://bugs.kde.org/show_bug.cgi?id=324975
OK, but we'll need a new Mageia bug report if we're going to do anything with this. The main issue in this bug was the Phonon configuration being incorrect, which was the only serious issue in Mageia 6 I was aware of when we released. It still needs to be fixed if possible.
Also, I'm not sure the 0% volume I reported earlier in this bug had anything to do with PulseAudio, as it sounds like I saw that *after* disabling it in the Phonon configuration.