Created attachment 174188 [details] Output from journalctl SUMMARY After updating from Qt 6.7.2 to 6.7.3 the "Sound" menu in system settings stays blank after opening it. It only shows the devices and playback streams after interacting with other sound controls (e.g. "Show inactive devices" or the widget in the panel) or when switching to a different menu and switching back to "Sound". Actual audio playback is not impacted and works fine. This did not happen with Qt 6.7.2. STEPS TO REPRODUCE 1. Update to Qt 6.7.3 2. Open "System Settings" 3. Open "Sound" OBSERVED RESULT No audio devices or playback streams are shown. EXPECTED RESULT Audio devices and playback streams are shown. ADDITIONAL INFORMATION If you interact with the sound widget in the panel (e.g. switching output) while the blank "Sound" menu is open, the devices and playback streams appear in the "Sound" menu right away and can be interacted with. This also happens if you toggle the "Show inactive devices" control if it is present. Alternatively you can also open "Sound" and if it stays blank switch to another menu (e.g. "Accessibillity") and then switch back to "Sound". Then the devices and playback streams also show up and can be interacted with. This happens on 2 PCs with completely different hardware / sound hardware (1x all AMD desktop and 1x all Intel laptop). But the software on both is the same (Linux distro, Plasma version, Qt version, ...) and it was no issue before updating to Qt 6.7.3 on both. SOFTWARE/OS VERSIONS Operating System: EndeavourOS (Arch Linux) KDE Plasma Version: 6.1.5 KDE Frameworks Version: 6.6.0 Qt Version: 6.7.3 Kernel Version: 6.10.10-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 16 × AMD Ryzen 7 7800X3D 8-Core Processor Memory: 30,9 GiB of RAM Graphics Processor: AMD Radeon RX 7900 XTX
Created attachment 174189 [details] Sound menu stays blank after opening
Created attachment 174190 [details] Devices are shown in widget and audio works
Created attachment 174191 [details] Devices and playback streams show up after interacting with widget
*** This bug has been marked as a duplicate of bug 493266 ***