Bug 480807

Summary: No error reporting when context breaks
Product: [Unmaintained] plasma-pa Reporter: Konstantin <ria.freelander>
Component: appletAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: isma.af, nate, nowrep, sitter
Priority: NOR Keywords: qt6
Version First Reported In: 5.93.0   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Screen of bug. There is both applet and systemsettings (OK) view.
Full Plasma log from those boot

Description Konstantin 2024-02-03 21:14:34 UTC
Created attachment 165512 [details]
Screen of bug. There is both applet and systemsettings (OK) view.

***
There is no devices shown
***


STEPS TO REPRODUCE
1. Open applet extended view (left click)
2. See results
3. 

OBSERVED RESULT
No devices shown

EXPECTED RESULT
Devices are shown

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 5.93.0
KDE Frameworks Version: 5.249.0
Qt Version: 6.7.0 beta 2

ADDITIONAL INFORMATION
This is pipewire used + bluetooth headphones.
On Systemsettings is all OK.
Comment 1 Konstantin 2024-02-03 21:17:16 UTC
There is pipewire and pipewire-pulse.
I assume than these socket name is not handled.
Comment 2 Harald Sitter 2024-02-04 18:09:12 UTC
Does the following command also have the problem?

`QT_LOGGING_RULES="org.kde.plasma.pulseaudio=true" plasmawindowed org.kde.plasma.volume`

If so: please attach the output.

If not: does the plasma applet have this problem across reboots or was this a one-off issue?
Comment 3 Konstantin 2024-02-04 19:13:26 UTC
It was one-off, across reboots is looks like semi-normal.
Comment 4 Harald Sitter 2024-02-04 20:00:35 UTC
In case you have persistent journald enabled can you take a look if you have the output

"context kaput"
and/or
"Giving up after"

My best guess is that pipewire was or restarting or something and we failed to re-establish a connection to the daemon.
Comment 5 Konstantin 2024-02-04 20:52:18 UTC
There is some fragments in log:
 фев 03 23:40:31 archlinux systemsettings[3012]: org.kde.plasma.pulseaudio: Settings schema org.freedesktop.pulseaudio.module-group is not installed
фев 03 23:40:31 archlinux systemsettings[3012]: org.kde.plasma.pulseaudio: Settings schema org.freedesktop.pulseaudio.module-group is not installed
фев 03 23:40:31 archlinux systemsettings[3012]: org.kde.plasma.pulseaudio: Settings schema org.freedesktop.pulseaudio.module-group is not installed

фев 03 23:42:36 archlinux plasmashell[1369]: kpipewire_logging: PipeWire remote error:  -2 target not found
фев 03 23:42:36 archlinux plasmashell[1369]: kpipewire_logging: PipeWire remote error:  -2 unknown resource 3 op:7

But I do not know WTF it is.
Comment 6 Konstantin 2024-02-04 20:55:05 UTC
Created attachment 165547 [details]
Full Plasma log from those boot

There is a full Plasma log with a bunch of Pipewire errors.
Comment 7 Harald Sitter 2024-02-04 21:06:52 UTC
Sounds unrelated.

I doubt we'll get to the bottom of this since it's not reproducible.

That being said, we currently have no proper error reporting when the daemon connection explodes, so I think we'll just resolve this bug by adding some more useful output in the hopes that future issues like this will become easier to debug.
Comment 8 Nate Graham 2024-02-05 21:42:57 UTC
Sounds eminently sane.
Comment 9 Harald Sitter 2024-09-25 15:11:56 UTC
Error reporting landed for 6.2 so this should be more obvious and recoverable moving forward.