Bug 492894 - Kde connect Daemon crashes when BT headset are switched off
Summary: Kde connect Daemon crashes when BT headset are switched off
Status: RESOLVED DUPLICATE of bug 477104
Alias: None
Product: kdeconnect
Classification: Applications
Component: plasmoid (show other bugs)
Version: 23.08.5
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Albert Vaca Cintora
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-09-09 16:09 UTC by Alessio Bettarello
Modified: 2024-10-09 20:30 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Alessio Bettarello 2024-09-09 16:09:50 UTC
SUMMARY
Hi,
whenever I put back in the case my Sony WF-1000XM4 (paired in HSP/HFP mode, with mSBC codec), it disconnects from my laptop Bluetooth and this causes a problem in pulse audio. Somehow consequently a crash is reported for KdeConnect Daemon. Follows backtrace (I recently updated from 22.04.1 LTS to 24.04 LTS)

STEPS TO REPRODUCE
1. Pull the headphones out of the case and wait for them to connect via BT  (already paired with HSP/HFP mode, with mSBC codec as default), they will initially connect as AD2P and later move to the preset I choose
2. Put the headphones back in the case

OBSERVED RESULT
A crash in KDEconnect Daemon happens and the mobile phone is not connecting no more to the daemon

EXPECTED RESULT
Kdeconnect continues working as before

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-41-generic (64-bit)
Graphics Platform: offscreen
Processors: 16 × AMD Ryzen 7 PRO 6850U with Radeon Graphics
Memory: 30.1 GiB of RAM
Graphics Processor: AMD Radeon Graphics

ADDITIONAL INFORMATION

Application: KDE Connect Daemon (kdeconnectd), signal: Segmentation fault

[KCrash Handler]
#4  0x0000777f9a1c0607 in ?? () from /lib/x86_64-linux-gnu/libKF5PulseAudioQt.so.3
#5  0x0000777f9a173dcf in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#6  0x0000777f9a10e558 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-16.1.so
#7  0x0000777f9a1129ec in pa_pdispatch_run () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-16.1.so
#8  0x0000777f9a1621db in ?? () from /lib/x86_64-linux-gnu/libpulse.so.0
#9  0x0000777f9a119aaf in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-16.1.so
#10 0x0000777f9a11b3c7 in ?? () from /usr/lib/x86_64-linux-gnu/pulseaudio/libpulsecommon-16.1.so
#11 0x0000777f9be61829 in ?? () from /lib/x86_64-linux-gnu/libpulse-mainloop-glib.so.0
#12 0x0000777fb6f145b5 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#13 0x0000777fb6f73717 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#14 0x0000777fb6f13a53 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#15 0x0000777fb8335279 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#16 0x0000777fb82d6a7b in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#17 0x0000777fb82df3e8 in QCoreApplication::exec() () from /lib/x86_64-linux-gnu/libQt5Core.so.5
#18 0x00005fd8f6f5906d in ?? ()
#19 0x0000777fb782a1ca in __libc_start_call_main (main=main@entry=0x5fd8f6f58bd0, argc=argc@entry=1, argv=argv@entry=0x7ffdfa41f858) at ../sysdeps/nptl/libc_start_call_main.h:58
#20 0x0000777fb782a28b in __libc_start_main_impl (main=0x5fd8f6f58bd0, argc=1, argv=0x7ffdfa41f858, init=<optimized out>, fini=<optimized out>, rtld_fini=<optimized out>, stack_end=0x7ffdfa41f848) at ../csu/libc-start.c:360
#21 0x00005fd8f6f59295 in ?? ()
[Inferior 1 (process 43515) detached]
Comment 1 Alessio Bettarello 2024-09-09 16:11:11 UTC
I can't always reproduce but that happens frequently when I perform the steps described on the summary.
Comment 2 Justin Zobel 2024-09-11 16:14:28 UTC
Unfortunately, the crash report is missing symbols.

Could you please install debug symbols and attach a new symbolicated backtrace generated by using coredumpctl gdb in a terminal window? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl for details about how to do this.
Comment 3 Alessio Bettarello 2024-09-12 12:47:47 UTC
(In reply to Justin Zobel from comment #2)
> Unfortunately, the crash report is missing symbols.
> 
> Could you please install debug symbols and attach a new symbolicated
> backtrace generated by using coredumpctl gdb in a terminal window? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl
> for details about how to do this.

#0  __pthread_kill_implementation (no_tid=0, signo=11, threadid=<optimized out>) at ./nptl/pthread_kill.c:44
#1  __pthread_kill_internal (signo=11, threadid=<optimized out>) at ./nptl/pthread_kill.c:78
#2  __GI___pthread_kill (threadid=<optimized out>, signo=signo@entry=11) at ./nptl/pthread_kill.c:89
#3  0x0000705a3f24526e in __GI_raise (sig=11) at ../sysdeps/posix/raise.c:26
#4  0x0000705a407136bf in KCrash::defaultCrashHandler (sig=11) at ./src/kcrash.cpp:631
#5  <signal handler called>
#6  0x0000705a22bc0607 in PulseAudioQt::CardPrivate::update (this=0x582a5aad4400, info=<optimized out>) at /usr/src/pulseaudio-qt-1.3-2build2/src/card.cpp:72
#7  0x0000705a22b73dcf in context_get_card_info_callback (pd=pd@entry=0x582a5aa2dd10, command=command@entry=2, tag=tag@entry=63, t=t@entry=0x582a5aa1eff0, userdata=userdata@entry=0x582a5aa692b0) at ../src/pulse/introspect.c:990
#8  0x0000705a22b0e558 in run_action (pd=0x582a5aa2dd10, r=0x582a5aa69f10, command=2, ts=0x582a5aa1eff0) at ../src/pulsecore/pdispatch.c:291
#9  0x0000705a22b129ec in pa_pdispatch_run (pd=0x582a5aa2dd10, packet=packet@entry=0x582a5aa28350, ancil_data=ancil_data@entry=0x582a5aa28f18, userdata=userdata@entry=0x582a5a96e240) at ../src/pulsecore/pdispatch.c:344
#10 0x0000705a22b621db in pstream_packet_callback (p=<optimized out>, packet=0x582a5aa28350, ancil_data=0x582a5aa28f18, userdata=0x582a5a96e240) at ../src/pulse/context.c:364
#11 0x0000705a22b19aaf in do_read (p=p@entry=0x582a5aa28c80, re=re@entry=0x582a5aa28e00) at ../src/pulsecore/pstream.c:1023
#12 0x0000705a22b1b3c7 in do_pstream_read_write (p=0x582a5aa28c80) at ../src/pulsecore/pstream.c:261
#13 0x0000705a23ed8829 in dispatch_func (source=source@entry=0x582a5a96e0c0, callback=<optimized out>, userdata=<optimized out>) at ../src/pulse/glib-mainloop.c:581
#14 0x0000705a3e7145b5 in g_main_dispatch (context=0x705a34000ed0) at ../../../glib/gmain.c:3344
#15 0x0000705a3e773717 in g_main_context_dispatch_unlocked (context=0x705a34000ed0) at ../../../glib/gmain.c:4152
#16 g_main_context_iterate_unlocked.isra.0 (context=context@entry=0x705a34000ed0, block=block@entry=1, dispatch=dispatch@entry=1, self=<optimized out>) at ../../../glib/gmain.c:4217
#17 0x0000705a3e713a53 in g_main_context_iteration (context=0x705a34000ed0, may_block=1) at ../../../glib/gmain.c:4282
#18 0x0000705a3fd35279 in QEventDispatcherGlib::processEvents (this=0x582a5a4871a0, flags=...) at kernel/qeventdispatcher_glib.cpp:423
#19 0x0000705a3fcd6a7b in QEventLoop::exec (this=this@entry=0x7ffca7194210, flags=..., flags@entry=...) at ../../include/QtCore/../../src/corelib/global/qflags.h:69
#20 0x0000705a3fcdf3e8 in QCoreApplication::exec () at ../../include/QtCore/../../src/corelib/global/qflags.h:121
#21 0x0000705a40138ecd in QGuiApplication::exec () at kernel/qguiapplication.cpp:1863
#22 0x0000705a4096bcb9 in QApplication::exec () at kernel/qapplication.cpp:2832
#23 0x0000582a5897606d in main (argc=<optimized out>, argv=<optimized out>) at /usr/src/kdeconnect-23.08.5-0ubuntu5/daemon/kdeconnectd.cpp:186
Comment 4 Bug Janitor Service 2024-09-27 03:47:21 UTC
🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME.

For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging.

Thank you for helping us make KDE software even better for everyone!
Comment 5 Nicolas Fella 2024-10-09 20:30:00 UTC
*** This bug has been marked as a duplicate of bug 477104 ***