Bug 98792

Summary:	Set as fallback — confusing button
Product:	PulseAudio	Reporter:	mrblooter
Component:	pavucontrol	Assignee:	pulseaudio-bugs
Status:	RESOLVED MOVED	QA Contact:	pulseaudio-bugs
Severity:	normal
Priority:	medium	CC:	lennart, trondsg+bugzilla+freedesktop
Version:	unspecified
Hardware:	x86-64 (AMD64)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description mrblooter 2016-11-20 09:05:19 UTC

For input and output devices, the button for "Set as fallback" doesn't behave intuitively. It appears to be a normal button, which remembers its state (pressed or not). That leads to the situation described below.

— Initial situation
Sources (asterisk marks the default as reported by pacmd):
1) *
2)
Select source #2 in the GUI and click the "Set as fallback" button.

— New situation
Sources:
1)
2) *
Number 2 is now the fallback as expected. The button is now in a "pressed" state. By clicking it again, one might assume that source #2 will not be the fallback any more, as it's represented by the button moving back to the "unpressed" state. However by checking the pacmd output again, source #2 is still the fallback. The button can still be clicked to make it change its state, however it has no effect on the sources itself.

Would it be possible to change the button type to something that would represent the situation more clearly? Maybe even add "Default Source" or similar next to the source or sinks (input and output devices), to easier convey which one is the default (fallback).

Pavucontrol version 3.0.
Pulseaudio version 9.0.

Comment 1 Tanu Kaskinen 2016-11-20 10:27:09 UTC

Thanks for the feedback! I agree, the current UI is pretty bad in this regard. However, I don't think I'll have time for improving it any time soon, so "patches welcome", as the saying goes.

Comment 2 Tanu Kaskinen 2016-11-27 21:23:17 UTC

*** Bug 98880 has been marked as a duplicate of this bug. ***

Comment 3 GitLab Migration User 2018-07-30 09:28:16 UTC

-- GitLab Migration Automatic Message --

This bug has been migrated to freedesktop.org's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.freedesktop.org/pulseaudio/pavucontrol/issues/14.

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.