Bug 423629 - Output device doesn't display multiple ports in the KCM; works in pavucontrol app
Summary: Output device doesn't display multiple ports in the KCM; works in pavucontrol...
Status: RESOLVED FIXED
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_pulseaudio (show other bugs)
Version: 5.18.5
Platform: Other Linux
: NOR normal
Target Milestone: ---
Assignee: David Rosca
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-06-28 20:21 UTC by Maurizio Paolini
Modified: 2020-07-07 14:18 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 5.19.0


Attachments
screenshot with both applet and Audio Volume Settings opened (929.19 KB, image/png)
2020-07-02 20:46 UTC, Maurizio Paolini
Details
screenshot with both audio settings panel and pavucontrol panel (929.51 KB, image/png)
2020-07-03 04:58 UTC, Maurizio Paolini
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Maurizio Paolini 2020-06-28 20:21:23 UTC
SUMMARY

with version 5.17 audio settings presented a checkbox that allowed to force
use of headphones (or internal speakers) independently of sensing insertion
of audio jack.  This was useful for me since I have a defective port.



SOFTWARE/OS VERSIONS

Linux fedora 32 distribution

Linux/KDE Plasma:
KDE Plasma Version: 5.18
KDE Frameworks Version: kf5, version 5.70
Qt Version: qt5, version 5.14
Comment 1 Maurizio Paolini 2020-06-30 08:36:57 UTC
I found that the involved component is actually 'plasma-pa'.  In the 'Additional option' for "Speakers" the section "Ports" is no longer present in the resulting panel.

The "Ports" section allows to select also "(unplugged)" ports, e.g. Line-Out or Headphones.
Comment 2 Nate Graham 2020-07-02 01:33:28 UTC
Yes, we hid this in the applet to save space, and have gotten various complaints from people with broken jacks. The feature is still there, it just moved to being exclusively visible in the KCM. Here's how you can do it: Open the Audio Volume System Tray applet > click on the "Configure" button > go to the Audio page > Set the port override over there.
Comment 3 Maurizio Paolini 2020-07-02 07:39:41 UTC
(In reply to Nate Graham from comment #2)
> Yes, we hid this in the applet to save space, and have gotten various
> complaints from people with broken jacks. The feature is still there, it
> just moved to being exclusively visible in the KCM. Here's how you can do
> it: Open the Audio Volume System Tray applet > click on the "Configure"
> button > go to the Audio page > Set the port override over there.

Unfortunately I cannot find how to do that.  I can assure you that I tried to navigate the Audio system settings in the past days but couldn't find the analogue of the Port list that used to be found in the applet.

In the "Devices" tab, Playback Devices section, I can only see the present choice (e.g. "Speakers (Built-in Audio Analog Stereo)" with the possibility
of muting it and changing its volume.  Nothing more than that and in particular no "additional options" as was the case in the applet.

Maybe this is a "Fedora 32" packaging problem, dunno... or perhaps I cannot find the proper place where the Ports list has been moved.
Sorry to bother you, however this is for me an important feature that I now miss a lot (as a workaround I now reinstalled the old 5.17 'plasma-pa' fedora package
Comment 4 Nate Graham 2020-07-02 20:17:15 UTC
Can you attach a screenshot of it?
Comment 5 Maurizio Paolini 2020-07-02 20:46:04 UTC
Created attachment 129852 [details]
screenshot with both applet and Audio Volume Settings opened

Here is a screenshot with the contents of the Audio settings panel as I get it
Comment 6 Maurizio Paolini 2020-07-02 20:47:30 UTC
(In reply to Maurizio Paolini from comment #5)
> Created attachment 129852 [details]
> screenshot with both applet and Audio Volume Settings opened
> 
> Here is a screenshot with the contents of the Audio settings panel as I get
> it

Sure!  I just attached a screenshot of my entire screen with both the applet
opened and the 'audio settings' opened.

Maurizio
Comment 7 Nate Graham 2020-07-02 23:31:56 UTC
Aha! It's not even seeing multiple ports in the first place. This means that the issue is deeper than anything in any KDE software, and it's somewhere in PulseAudio itself, which is somehow no longer exposing multiple ports to Plasma's UI. You can check this in the 3rd-party Pulse Audio Volume Control (AKA pavucontrol) app; I bet it shows the same thing.

I believe Fedora 32 is shipping the unreleased PulseAudio 14 (as version 13.99 or something like that) so it's quite likely that this is a PulseAudio regression. I would recommend reporting the issue to either the Fedora devs at https://bugzilla.redhat.com, or to the PulseAudio devs directly, at https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/
Comment 8 Maurizio Paolini 2020-07-03 04:34:56 UTC
(In reply to Nate Graham from comment #7)
> Aha! It's not even seeing multiple ports in the first place. This means that
> the issue is deeper than anything in any KDE software, and it's somewhere in
> PulseAudio itself, which is somehow no longer exposing multiple ports to
> Plasma's UI. You can check this in the 3rd-party Pulse Audio Volume Control
> (AKA pavucontrol) app; I bet it shows the same thing.

Sorry, but I must contradict you, I just tried pavucontrol (I didn't know of its existence) and it DOES show multiple ports!
I will shortly provide a screenshot of that.
Comment 9 Maurizio Paolini 2020-07-03 04:58:07 UTC
Created attachment 129858 [details]
screenshot with both audio settings panel and pavucontrol panel

"spectacle" does not allow to capture the pop-down menu that appears when clicking in the "Speakers" Port entry of pavucontrol, however it lists three
entries:

  Speakers
  Headphones (unplugged)
  Line Out (unplugged)
Comment 10 Maurizio Paolini 2020-07-03 04:59:49 UTC
Anyway, by using pavucontrol I actually have a workaround for my problem
Comment 11 Nate Graham 2020-07-03 05:17:39 UTC
All right, if pavucontrol sees the ports, they should be visible in the KCM as well. Looks like it is our bug after all.
Comment 12 Maurizio Paolini 2020-07-03 05:27:38 UTC
(In reply to Nate Graham from comment #11)
> All right, if pavucontrol sees the ports, they should be visible in the KCM
> as well. Looks like it is our bug after all.

I am using plasma-pa-5.18.5-1.fc32.x86_64; the corresponding SPEC file
of the rpm package starts with:

----------------------
Name:    plasma-pa
Version: 5.18.5
Release: 1%{?dist}
Summary: Plasma applet for audio volume management using PulseAudio

License: LGPLv2+ and GPLv2+
URL:     https://cgit.kde.org/%{name}.git

%global revision %(echo %{version} | cut -d. -f3)
%if %{revision} >= 50
%global stable unstable
%else
%global stable stable
%endif
Source0: http://download.kde.org/%{stable}/plasma/%{version}/%{name}-%{version}.tar.xz
----------------------

meaning that the source package is taken from

http://download.kde.org/stable/plasma/5.18.5/plasma-pa-5.18.5.tar.xz

I do not see any patch being applied to that.  It might be that a problem exists in that particular version of plasma-pa
Comment 13 Nate Graham 2020-07-03 14:16:01 UTC
Any chance you could somehow upgrade Plasma-pa or all of Plasma to 5.19 (or even better, git the master version) in Fedora to see if it's better? I ask because some audio handling stuff was re-done after 5.18, so it's possible this has already been fixed.
Comment 14 Maurizio Paolini 2020-07-04 07:47:46 UTC
(In reply to Nate Graham from comment #13)
> Any chance you could somehow upgrade Plasma-pa or all of Plasma to 5.19 (or
> even better, git the master version) in Fedora to see if it's better? I ask
> because some audio handling stuff was re-done after 5.18, so it's possible
> this has already been fixed.

I just tried the fedora-rawhide rpm: plasma-pa-5.19.2-1.fc33.x86_64
and it works just fine!  As expected I have the possibility to select
"Headphones (unplugged)"...
Comment 15 Nate Graham 2020-07-06 16:12:03 UTC
Excellent.
Comment 16 Maurizio Paolini 2020-07-07 13:58:03 UTC
Well, actually there is still a problem for users of Fedora 32. Perhaps the correct course of action is to open a bug report on bugzilla.redhat.com
Comment 17 Nate Graham 2020-07-07 14:18:44 UTC
Yes, they could backport the changes.