Bug 486513

Summary: Steam Deck doesn't see built–in speakers
Product: [Applications] systemsettings Reporter: Overko Ivan <overivanzp>
Component: generic-crashAssignee: Plasma Bugs List <plasma-bugs-null>
Status: RESOLVED DOWNSTREAM    
Severity: crash CC: nate
Priority: NOR Keywords: drkonqi
Version First Reported In: 5.27.10   
Target Milestone: ---   
Platform: SteamOS   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: attachment-3076650-0.html

Description Overko Ivan 2024-05-03 15:18:25 UTC 
Application: systemsettings (5.27.10)
 (Compiled from sources)
Qt Version: 5.15.12
Frameworks Version: 5.115.0
Operating System: Linux 6.5.0-valve3-3-neptune-65-gf73fe24f1b3a x86_64
Windowing System: X11
Distribution: SteamOS
DrKonqi: 5.27.10 [KCrashBackend]

-- Information about the crash:
After updating the system, the Steam Deck lost sound; in desktop mode, when i try to enter the settings, the program crashes. Audio panel doesn't see speakers.

The crash can be reproduced every time.

-- Backtrace:
Application: System Settings (systemsettings), signal: Bus error

[KCrash Handler]
#4  0x00007fad0cf79101 in ??? () at /usr/lib/libc.so.6
#5  0x00007fad0d694b70 in ??? () at /usr/lib/libQt5Core.so.5
#6  0x00007fad0d685009 in QPluginLoader::setFileName(QString const&) () at /usr/lib/libQt5Core.so.5
#7  0x00007fad0e97adec in KPluginMetaData::KPluginMetaData(QString const&, KPluginMetaData::KPluginMetaDataOption) () at /usr/lib/libKF5CoreAddons.so.5
#8  0x00007fad0e97b1ea in ??? () at /usr/lib/libKF5CoreAddons.so.5
#9  0x00007fad0e97872a in KPluginMetaData::findPlugins(QString const&, std::function<bool (KPluginMetaData const&)>, KPluginMetaData::KPluginMetaDataOption) () at /usr/lib/libKF5CoreAddons.so.5
#10 0x00007fad0e978b08 in KPluginMetaData::findPlugins(QString const&, std::function<bool (KPluginMetaData const&)>) () at /usr/lib/libKF5CoreAddons.so.5
#11 0x000055f4a22972ed in ??? ()
#12 0x000055f4a2298047 in ??? ()
#13 0x00007fad0d6bb964 in QObject::event(QEvent*) () at /usr/lib/libQt5Core.so.5
#14 0x00007fad0f05e03e in KXmlGuiWindow::event(QEvent*) () at /usr/lib/libKF5XmlGui.so.5
#15 0x00007fad0e3578ff in QApplicationPrivate::notify_helper(QObject*, QEvent*) () at /usr/lib/libQt5Widgets.so.5
#16 0x00007fad0d693ef8 in QCoreApplication::notifyInternal2(QObject*, QEvent*) () at /usr/lib/libQt5Core.so.5
#17 0x00007fad0d698e5b in QCoreApplicationPrivate::sendPostedEvents(QObject*, int, QThreadData*) () at /usr/lib/libQt5Core.so.5
#18 0x00007fad0d6deec8 in ??? () at /usr/lib/libQt5Core.so.5
#19 0x00007fad0bf0df69 in ??? () at /usr/lib/libglib-2.0.so.0
#20 0x00007fad0bf6c3a7 in ??? () at /usr/lib/libglib-2.0.so.0
#21 0x00007fad0bf0c162 in g_main_context_iteration () at /usr/lib/libglib-2.0.so.0
#22 0x00007fad0d6e2d0c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#23 0x00007fad0d692c04 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () at /usr/lib/libQt5Core.so.5
#24 0x00007fad0d6940a3 in QCoreApplication::exec() () at /usr/lib/libQt5Core.so.5
#25 0x000055f4a228dbd9 in ??? ()
#26 0x00007fad0ce43cd0 in ??? () at /usr/lib/libc.so.6
#27 0x00007fad0ce43d8a in __libc_start_main () at /usr/lib/libc.so.6
#28 0x000055f4a228e575 in ??? ()
[Inferior 1 (process 7459) detached]

Reported using DrKonqi
Comment 1 Nate Graham 2024-05-05 00:37:30 UTC 
Did you actually compile the sources yourself, or is this a stock installation?
Comment 2 Overko Ivan 2024-05-05 09:44:08 UTC 
Created attachment 169205 [details]
attachment-3076650-0.html

Yes, this is stocke installation, but now after update sistem, everything
is working. Thanks đź‘Ť

On Sun, May 5, 2024, 02:37 Nate Graham <bugzilla_noreply@kde.org> wrote:

> https://bugs.kde.org/show_bug.cgi?id=486513
>
> --- Comment #1 from Nate Graham <nate@kde.org> ---
> Did you actually compile the sources yourself, or is this a stock
> installation?
>
> --
> You are receiving this mail because:
> You reported the bug.
Comment 3 Nate Graham 2024-05-06 20:34:20 UTC 
Ok, great! Sounds like maybe there was an update issue that cleared itself up on the next one.