SUMMARY Crash on subwoofer test in System Settings --> Audio --> Test --> Subwoofer. STEPS TO REPRODUCE 1. Override some pins with hdajackretask 2. Go to System Settings --> Audio 3. Set speaker profile to Analog Surround 2.1 4. Go to Test and click on Subwoofer OBSERVED RESULT Crash EXPECTED RESULT No crash and an error SOFTWARE/OS VERSIONS Linux: 5.15.6 KDE Plasma Version: 5.23.4 KDE Frameworks Version: 5.88.0 Qt Version: 5.15.2 ADDITIONAL INFORMATION This is probably happening because I have tinkered with hdajackretask to configure the front speakers on my laptop. So, while I am not surprised by the crash, an error message would be nicer.
Cannot reproduce. Can you attach a backtrace of the crash? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
(In reply to Nate Graham from comment #1) > Cannot reproduce. Can you attach a backtrace of the crash? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports Ok, so my mistake. The first few times I tried to reproduce it crashed, but now it just freezes and has to be terminated. I reproduced the freeze with gdb and this is the output I got between entering the audio sub-menu and the freeze: > [New Thread 0x7fff7d724640 (LWP 103687)] > org.kde.plasma.pulseaudio: Settings schema org.freedesktop.pulseaudio.module-group is not installed > org.kde.plasma.pulseaudio: Settings schema org.freedesktop.pulseaudio.module-group is not installed > org.kde.plasma.pulseaudio: Settings schema org.freedesktop.pulseaudio.module-group is not installed > QQmlEngine::setContextForObject(): Object already has a QQmlContext > [New Thread 0x7fff7f476640 (LWP 103688)] > org.kde.plasma.pulseaudio: No object for name "alsa_output.pci-0000_04_00.6.analog-surround-21.monitor" > [New Thread 0x7fff6e028640 (LWP 103690)] > [Thread 0x7fff9dffb640 (LWP 103627) exited] > [Thread 0x7fff9e7fc640 (LWP 103626) exited] > [Thread 0x7fff9effd640 (LWP 103625) exited] > [Thread 0x7fff9f7fe640 (LWP 103624) exited] After that it just froze. (Sorry for taking so long btw)
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
I also tried to reproduce it in KDE Neon, but it all worked fine, so this might be an arch specivic issue the only interesting thing i found in gdb was this: > file:///usr/share/kpackage/kcms/kcm_pulseaudio/contents/ui/StreamListItem.qml:22: TypeError: Cannot read property 'width' of null But I'm not sure how helpful this is...
That's not a backtrace; you have to hit `bt` on the GDB prompt to get one.
(In reply to Nate Graham from comment #5) > That's not a backtrace; you have to hit `bt` on the GDB prompt to get one. Ok, I'm sorry, I'm new at reporting bugs 😅 Is this correct? > (gdb) bt > #0 0x00007ffff4fef8ca in __futex_abstimed_wait_common64 () at /usr/lib/libpthread.so.0 > #1 0x00007ffff4fe9270 in pthread_cond_wait@@GLIBC_2.3.2 () at /usr/lib/libpthread.so.0 > #2 0x00007fff7e561c39 in pa_threaded_mainloop_wait () at /usr/lib/libpulse.so.0 > #3 0x00007fff7c894d1c in pulse_driver_play () at /usr/lib/libcanberra-0.30/libcanberra-pulse.so > #4 0x00007ffff01f0ede in ca_context_play_full () at /usr/lib/libcanberra.so.0 > #5 0x00007fff7e5de9fc in () at /usr/lib/qt/qml/org/kde/plasma/private/volume/libplasma-volume-declarative.so > #6 0x00007fff7e5c8af9 in () at /usr/lib/qt/qml/org/kde/plasma/private/volume/libplasma-volume-declarative.so > #7 0x00007ffff5821c9e in () at /usr/lib/libQt5Qml.so.5 > #8 0x00007ffff56fd121 in () at /usr/lib/libQt5Qml.so.5 > #9 0x00007ffff56fef6b in QV4::QObjectMethod::callInternal(QV4::Value const*, QV4::Value const*, int) const () at /usr/lib/libQt5Qml.so.5 > #10 0x00007ffff571c0c0 in () at /usr/lib/libQt5Qml.so.5 > #11 0x00007ffff571edbf in () at /usr/lib/libQt5Qml.so.5 > #12 0x00007ffff56b10df in QV4::Function::call(QV4::Value const*, QV4::Value const*, int, QV4::ExecutionContext const*) () at /usr/lib/libQt5Qml.so.5 > #13 0x00007ffff583cf36 in QQmlJavaScriptExpression::evaluate(QV4::CallData*, bool*) () at /usr/lib/libQt5Qml.so.5 > #14 0x00007ffff57ed53d in QQmlBoundSignalExpression::evaluate(void**) () at /usr/lib/libQt5Qml.so.5 > #15 0x00007ffff57ee799 in () at /usr/lib/libQt5Qml.so.5 > #16 0x00007ffff5821755 in QQmlNotifier::emitNotify(QQmlNotifierEndpoint*, void**) () at /usr/lib/libQt5Qml.so.5 > #17 0x00007ffff6999f3e in () at /usr/lib/libQt5Core.so.5 > #18 0x00007ffff0096882 in QQuickAbstractButtonPrivate::handleRelease(QPointF const&) () at /usr/lib/libQt5QuickTemplates2.so.5 > #19 0x00007ffff00b5f29 in QQuickControl::mouseReleaseEvent(QMouseEvent*) () also, is there a syntax to mark the output above as a diffrent style withouth creating quoutes?
Looks better, thanks! I'm afraid you have to use quotes.
Created attachment 147891 [details] Backtrace for bug 446622 (systemsettings - subwoofer test) ## Versions Ditro: Archlinux Linux: 5.17.1.arch1-1 Kde (systemsettings): 5.24.4-1 Pipewire: 1:0.3.49-1 Alsa: 1.2.6.1-1 `lspci`: ``` 01:00.1 Audio device: NVIDIA Corporation TU104 HD Audio Controller (rev a1) ``` `pactl list sources short`: ``` 369 alsa_output.pci-0000_01_00.1.hdmi-surround-extra3.monitor PipeWire s32le 6ch 48000Hz IDLE ``` Attached another **full** backtrace.
This looks like https://bugs.kde.org/show_bug.cgi?id=445523, which got fixed from 5.24.5 *** This bug has been marked as a duplicate of bug 445523 ***