| Summary: | kcm_pulseaudio Doesn't Load on the First Launch with Qt 6.8 | ||
|---|---|---|---|
| Product: | [Applications] systemsettings | Reporter: | Dashon <dashonwwIII> |
| Component: | kcm_pulseaudio | Assignee: | Plasma Bugs List <plasma-bugs> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | normal | CC: | bugseforuns, dashonwwIII, eugene.shalygin+bugzilla.kde, iodreamify, isma.af, kde, nate, nepnep, nicolas.fella, notmart, omano, phamtruonggiang726, profrporcaro, rafal.zuchnik, sam, sitter, yasielordonezabreu |
| Priority: | HI | Keywords: | regression |
| Version: | 6.1.90 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| See Also: | https://bugreports.qt.io/browse/QTBUG-129165 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Example of what appears instead of the correct audio page. | ||
Changed this to systemsettings kcm bug instea of plasma-pa. Since new information gathered during the process of filing this bug has made me realize that trying to get to this page for the first time seems broken in general right now. Can confirm on master. This started happening after a recent update to the versions on Kubuntu 22.10 (dev): - pipewire -V > Compiled with libpipewire 1.2.3 - wireplumber > Compiled with libwireplumber 0.5.6 The devices reappear after restarting wireplumber but are not updated afterwards (for instance switching profile from the applet): `systemctl --user restart wireplumber.service` Other categories like "Streams" or "Inactive Cards" are also not shown. The applet show the items without issue (also pavucontrol) Already checkout that commit "eae94ed4 allow user to rename devices and select a preferred name source" has nothing to do with this (it was the only recent main change to this part of the code). FWIW bisecting up to some time in plasma-pa or pulseaudio-qt didn't also fix the issue. *** Bug 493282 has been marked as a duplicate of this bug. ***
> Hey, this is either an Arch Packaging problem or a Qt 6.8 beta bug since I couldn't reproduce this on openSUSE Tumbleweed with Krypton repos.
Commenting on this, it might be an issue with Qt6.8, since it works on my distro session (Qt6.6.2, Plasma 6.1.5) for the same versions of pw and wp, but it fails on my dev session even when downgrading to the same compiled versions.
Operating System: Kubuntu 24.10
KDE Plasma Version: 6.1.90
KDE Frameworks Version: 6.7.0
Qt Version: 6.8.0
Kernel Version: 6.8.0-41-generic (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Core™ i7-8565U CPU @ 1.80GHz
Memory: 15.3 GiB of RAM
Graphics Processor: Mesa Intel® UHD Graphics 620
Manufacturer: LG Electronics
Product Name: 15Z990-V.AA78B
System Version: 0.1
can you paste the terminal output that happens by having systemsettings launched in konsole? (In reply to Marco Martin from comment #5) > can you paste the terminal output that happens by having systemsettings > launched in konsole? Not much output even when enabling the debug rules for pulseaudio. It's the same thing when launching kcmshell6 or systemsettings > export QT_LOGGING_RULES="org.kde.plasma.pulseaudio=true" > systemsettings kcm_pulseaudio Using fontconfig file: "/home/isma/.config/fontconfig/fonts.conf" qt.qpa.wayland: eglSwapBuffers failed with 0x300d, surface: 0x0 org.kde.pulseaudio: No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor" No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo" No object for name "alsa_output.pci-0000_00_1f.3.analog-stereo.monitor" On exiting there's a bunch (14 lines) of: QObject::startTimer: Timers can only be used with threads started with QThread (In reply to Marco Martin from comment #5) > can you paste the terminal output that happens by having systemsettings > launched in konsole? I noticed the same results that @Ismael Asensio did. Easily reproduced. It's a regression somewhere in qtquick listview. https://invent.kde.org/qt/qt/qtdeclarative/-/commit/e64662650f351c24a5818f89e84c7a7dc4133e73 https://invent.kde.org/qt/qt/qtdeclarative/-/commit/477c15def834bd49553c00b90f3a2006456ea931 seem to blame at a glance Upstream bug report: https://bugreports.qt.io/browse/QTBUG-129165 It's marked as a P0 blocker upstream, I think we don't have to act on this. I'm sure it will be taken care of *** Bug 493661 has been marked as a duplicate of this bug. *** *** Bug 493794 has been marked as a duplicate of this bug. *** *** Bug 493813 has been marked as a duplicate of this bug. *** This regression has trickled down to Qt 6.7.3 *** Bug 494341 has been marked as a duplicate of this bug. *** *** Bug 494370 has been marked as a duplicate of this bug. *** *** Bug 494515 has been marked as a duplicate of this bug. *** *** Bug 494655 has been marked as a duplicate of this bug. *** *** Bug 494692 has been marked as a duplicate of this bug. *** |
Created attachment 173768 [details] Example of what appears instead of the correct audio page. SUMMARY Hey, this is either an Arch Packaging problem or a Qt 6.8 beta bug since I couldn't reproduce this on openSUSE Tumbleweed with Krypton repos. Anyways, clicking on the cogwheel / gear / settings icon or whatever in the audio applet on the system tray will open up the audio kcm in system settings, but the page is empty. Navigating away and then back to the sound page makes things appear fine. STEPS TO REPRODUCE 1. Click audio applet in system tray. 2. Click cogwheel / gear icon. OBSERVED RESULT Empty sound settings page. EXPECTED RESULT All applicable options should appear. SOFTWARE/OS VERSIONS Operating System: EndeavourOS KDE Plasma Version: 6.1.90 KDE Frameworks Version: 6.6.0 Qt Version: 6.8.0 Kernel Version: 6.10.10-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 5800X 8-Core Processor Memory: 62.7 GiB of RAM Graphics Processor: NVIDIA GeForce RTX 3080/PCIe/SSE2 Manufacturer: Micro-Star International Co., Ltd. Product Name: MS-7C95 System Version: 1.0 ADDITIONAL INFORMATION Also trying to get the audio kcm from the application launcher has the same result. Manually running the command `systemsettings kcm_pulseaudio` will of course give the same result also. Lastly, opening system settings and then going to sound will result in the same problem. It seems I can only open it if I click on some other settings module and then go back to sound.