Bug 19691 - phonon defaults to Pulse backend even if PulseAudio is disabled
: phonon defaults to Pulse backend even if PulseAudio is disabled
Status: NEW
Product: Mageia
Classification: Unclassified
Component: RPM Packages
: Cauldron
: All Linux
: release_blocker Severity: major
: Mageia 6
Assigned To: KDE maintainers
:
:
:
:
:
: 17523
  Show dependency treegraph
 
Reported: 2016-11-01 18:06 CET by David Walser
Modified: 2017-03-07 03:08 CET (History)
1 user (show)

See Also:
Source RPM: phonon-4.9.0-2.mga6.src.rpm
CVE:
Status comment:


Attachments

Description David Walser 2016-11-01 18:06:38 CET
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.
Comment 1 David Walser 2016-11-01 18:07:16 CET
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.
Comment 2 David Walser 2016-11-01 18:18:36 CET
Amarok seems to reset itself to 0% at every log in.  Not sure if this is Amarok or Phonon's fault.
Comment 3 Nicolas Lécureuil 2017-03-05 21:56:19 CET
is the sound to 0% only in amarok ? or in plasma-pa too ?
Comment 4 Samuel Verschelde 2017-03-06 16:04:35 CET
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.
Comment 5 David Walser 2017-03-07 03:08:57 CET
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.

Note You need to log in before you can comment on or make changes to this bug.