[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236 Bug Janitor Service changed: What|Removed |Added Resolution|BACKTRACE |WORKSFORME Status|NEEDSINFO |RESOLVED --- Comment #10 from Bug Janitor Service --- 🐛🧹 This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236 --- Comment #9 from Bug Janitor Service --- 🐛🧹 ⚠️ 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! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236 --- Comment #8 from John Kizer --- Hmm - I don't know if there are specific, unique things that need to done on Arch Linux to get a backtrace fully populated, beyond what's listed out on the Community Wiki link that I shared earlier. I'm also still 99% sure that this is an instance of that bug 503703 popping up - so would it work to say: * If you're able to snag a fully populated backtrace from your device, add it as a comment here * If not, then when Kirigami 6.14.1 - the point release that contains the fix for that bug - is packaged and updated for Arch Linux (likely not too long from now), can you check if this crash still occurs? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236 --- Comment #7 from ryan --- I remember being prompted to enable debuginfod when running gdb. I remembering selecting yes. still new to coredumpctl and gdb. Just ran `coredumpctl info kdeconnect-sms` and now No coredumps found. Have rebooted since yesterday, default conf for coredump. Imagine coredumpctl only saves since last boot. Sorry I couldn't be more helpful! On 5/15/25 5:25 PM, John Kizer wrote: > https://bugs.kde.org/show_bug.cgi?id=504236 > > --- Comment #6 from John Kizer --- > Hmm, those repeated "No symbol table info available" lines mean it's still > missing the information about what functions are running when the crash > occurs, > unfortunately. Did it prompt to enable debuginfod when running gdb? > -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236 --- Comment #6 from John Kizer --- Hmm, those repeated "No symbol table info available" lines mean it's still missing the information about what functions are running when the crash occurs, unfortunately. Did it prompt to enable debuginfod when running gdb? -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236
--- Comment #5 from ryan ---
bt full trace for ya:
-
#0 __pthread_kill_implementation (threadid=,
signo=signo@entry=6, no_tid=no_tid@entry=0) at pthread_kill.c:44
tid =
ret = 0
pd =
old_mask = {__val = {140729692962912}}
ret =
#1 0x7ea24eea7813 in __pthread_kill_internal (threadid=, signo=6) at pthread_kill.c:89
No locals.
#2 0x7ea24ee4ddc0 in __GI_raise (sig=sig@entry=6) at
../sysdeps/posix/raise.c:26
ret =
#3 0x7ea24ee3557a in __GI_abort () at abort.c:73
act = {__sigaction_handler = {sa_handler = 0xe36, sa_sigaction
= 0xe36}, sa_mask = {__val = {139235328636360, 140729692962316,
139235581253797, 0, 0, 0, 2, 0, 0, 0, 2, 106942466206976,
2865199500376845312, 140729692962528, 140729692962976,
106942466206976}}, sa_flags = 1370355136, sa_restorer = 0x7ffe2f5bbed0}
#4 0x7ea24f09a421 in std::__glibcxx_assert_fail (file=, line=, function=,
condition=) at
/usr/src/debug/gcc/gcc/libstdc++-v3/src/c++11/assert_fail.cc:41
No locals.
#5 0x7ea2404af430 in ?? ()
No symbol table info available.
#6 0x403e in ?? ()
No symbol table info available.
#7 0x404e in ?? ()
No symbol table info available.
#8 0x8001 in ?? ()
No symbol table info available.
#9 0x403e in ?? ()
No symbol table info available.
#10 0x7ffe2f5bbfd0 in ?? ()
No symbol table info available.
#11 0x7ffe2f5bc240 in ?? ()
No symbol table info available.
#12 0x7ffe2f5bbf40 in ?? ()
No symbol table info available.
#13 0x7ea24f9fa720 in ?? () from /usr/lib/libQt6Core.so.6
No symbol table info available.
#14 0x7ea24f9fa720 in ?? () from /usr/lib/libQt6Core.so.6
No symbol table info available.
#15 0x27c33bc3de96ac00 in ?? ()
No symbol table info available.
#16 0x7ffe2f5bc0a0 in ?? ()
No symbol table info available.
#17 0x in ?? ()
No symbol table info available.
Warning: 'set logging off', an alias for the command 'set logging
enabled', is deprecated.
Use 'set logging enabled off'.
--
replying to this via email, hope the formatting isn't awful for you.
On 5/14/25 8:10 PM, John Kizer wrote:
> https://bugs.kde.org/show_bug.cgi?id=504236
>
> --- Comment #4 from John Kizer ---
> No worries! There are instructions up at the top of that page for making sure
> you have debug info installed on your device too, which helps tag each part of
> the stack with the actual function name that was involved.
>
> I am 99% sure that this issue is https://bugs.kde.org/show_bug.cgi?id=503703 ,
> I just want to make sure with that backtrace before merging the reports
> together :-)
>
--
You are receiving this mail because:
You are watching all bug changes.
[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236 --- Comment #4 from John Kizer --- No worries! There are instructions up at the top of that page for making sure you have debug info installed on your device too, which helps tag each part of the stack with the actual function name that was involved. I am 99% sure that this issue is https://bugs.kde.org/show_bug.cgi?id=503703 , I just want to make sure with that backtrace before merging the reports together :-) -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236 --- Comment #3 from ryan --- Ope! Didn't have GDB installed. Sorry new to low-level stuff and proper programming. running GDB right now, it's checking. May have better result for you in a bit. On 5/14/25 7:58 PM, DoNotReply wrote: > Dead PID from many hours ago, running into issue where crash no longer > occurs. > > On running `coredumpctl gdb #pidnumberhere` i get partial output of > memory locations but also error, Failed to invoke gdb: No such file or > directory. > > Hope this stack trace helps: > > ` > > PID: 1756914 (kdeconnect-sms) > UID: 1000 (rydesk) > GID: 1000 (rydesk) > Signal: 6 (ABRT) > Timestamp: Wed 2025-05-14 13:11:51 PDT (6h ago) > Command Line: /usr/bin/kdeconnect-sms > Executable: /usr/bin/kdeconnect-sms > Control Group: > /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.kdeconnect.sms@f0ad339604ad4402b675343576d75dc4.service > Unit: user@1000.service > User Unit: > app-org.kde.kdeconnect.sms@f0ad339604ad4402b675343576d75dc4.service > Slice: user-1000.slice > Owner UID: 1000 (rydesk) > Boot ID: f72ea514e9cd460898b2d722aa2b927f > Machine ID: ab84d0e1367bf1a6f22bdc73680b5ec0 > Hostname: rydesk-g439 > Storage: > /var/lib/systemd/coredump/core.kdeconnect-sms.1000.f72ea514e9cd460898b2d722aa2b927f.1756914.174725351100.zst > > (present) > Size on Disk: 10.1M > Message: Process 1756914 (kdeconnect-sms) of user 1000 dumped > core. > > Stack trace of thread 1756914: > #0 0x7ea24eea774c n/a (libc.so.6 + 0x9774c) > #1 0x7ea24ee4ddc0 raise (libc.so.6 + 0x3ddc0) > #2 0x7ea24ee3557a abort (libc.so.6 + 0x2557a) > #3 0x7ea24f09a421 > _ZSt21__glibcxx_assert_failPKciS0_S0_ (libstdc++.so.6 + 0x9a421) > #4 0x7ea2404af430 n/a (libKirigami.so.6 + 0xd430) > #5 0x7ea2404d68f8 n/a (libKirigami.so.6 + 0x348f8) > #6 0x7ea2404d85bf n/a (libKirigami.so.6 + 0x365bf) > #7 0x7ea24f559358 > _ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent > (libQt6Core.so.6 + 0x159358) > #8 0x7ea2506fed8e > _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent > (libQt6Widgets.so.6 + 0xfed8e) > #9 0x7ea24f55a018 > _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent > (libQt6Core.so.6 + 0x15a018) > #10 0x7ea251771bf0 > _ZN26QQuickDeliveryAgentPrivate36deliverSinglePointEventUntilAcceptedEP13QPointerEvent > > (libQt6Quick.so.6 + 0x371bf0) > #11 0x7ea251779118 > _ZN19QQuickDeliveryAgent5eventEP6QEvent (libQt6Quick.so.6 + 0x379118) > #12 0x7ea25166d5f8 > _ZN12QQuickWindow5eventEP6QEvent (libQt6Quick.so.6 + 0x26d5f8) > #13 0x7ea2506fed9e > _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent > (libQt6Widgets.so.6 + 0xfed9e) > #14 0x7ea24f55a018 > _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent > (libQt6Core.so.6 + 0x15a018) > #15 0x7ea24fd8bbfa > _ZN22QGuiApplicationPrivate17processWheelEventEPN29QWindowSystemInterfacePrivate10WheelEventE > > (libQt6Gui.so.6 + 0x18bbfa) > #16 0x7ea24fe0d0c4 > _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE > > (libQt6Gui.so.6 + 0x20d0c4) > #17 0x7ea24fe0d2b7 > _ZN22QWindowSystemInterface23flushWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE > > (libQt6Gui.so.6 + 0x20d2b7) > #18 0x7ea24f5a54aa _ZN7QObject5eventEP6QEvent > (libQt6Core.so.6 + 0x1a54aa) > #19 0x7ea2506fed9e > _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent > (libQt6Widgets.so.6 + 0xfed9e) > #20 0x7ea24f55a018 > _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent > (libQt6Core.so.6 + 0x15a018) > #21 0x7ea24f55a3f2 > _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData > (libQt6Core.so.6 + 0x15a3f2) > #22 0x7ea24f7cfea8 n/a (libQt6Core.so.6 + 0x3cfea8) > #23 0x7ea24e72e1e4 n/a (libglib-2.0.so.0 + 0x5e1e4) > #24 0x7ea24e791e97 n/a (libglib-2.0.so.0 + 0xc1e97) > #25 0x7ea24e72d615 g_main_context_iteration > (libglib-2.0.so.0 + 0x5d615) > #26 0x7ea24f7cd59d > _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE > > (libQt6Core.so.6 + 0x3cd59d) > #27 0x7ea24f565376 > _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 > + 0x165376) > #28 0x7ea24f55d159 _ZN16QCoreApplication4execEv > (libQt6Core.so.6 + 0x15d159) > #29
[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236 --- Comment #2 from ryan --- Dead PID from many hours ago, running into issue where crash no longer occurs. On running `coredumpctl gdb #pidnumberhere` i get partial output of memory locations but also error, Failed to invoke gdb: No such file or directory. Hope this stack trace helps: ` PID: 1756914 (kdeconnect-sms) UID: 1000 (rydesk) GID: 1000 (rydesk) Signal: 6 (ABRT) Timestamp: Wed 2025-05-14 13:11:51 PDT (6h ago) Command Line: /usr/bin/kdeconnect-sms Executable: /usr/bin/kdeconnect-sms Control Group: /user.slice/user-1000.slice/user@1000.service/app.slice/app-org.kde.kdeconnect.sms@f0ad339604ad4402b675343576d75dc4.service Unit: user@1000.service User Unit: app-org.kde.kdeconnect.sms@f0ad339604ad4402b675343576d75dc4.service Slice: user-1000.slice Owner UID: 1000 (rydesk) Boot ID: f72ea514e9cd460898b2d722aa2b927f Machine ID: ab84d0e1367bf1a6f22bdc73680b5ec0 Hostname: rydesk-g439 Storage: /var/lib/systemd/coredump/core.kdeconnect-sms.1000.f72ea514e9cd460898b2d722aa2b927f.1756914.174725351100.zst (present) Size on Disk: 10.1M Message: Process 1756914 (kdeconnect-sms) of user 1000 dumped core. Stack trace of thread 1756914: #0 0x7ea24eea774c n/a (libc.so.6 + 0x9774c) #1 0x7ea24ee4ddc0 raise (libc.so.6 + 0x3ddc0) #2 0x7ea24ee3557a abort (libc.so.6 + 0x2557a) #3 0x7ea24f09a421 _ZSt21__glibcxx_assert_failPKciS0_S0_ (libstdc++.so.6 + 0x9a421) #4 0x7ea2404af430 n/a (libKirigami.so.6 + 0xd430) #5 0x7ea2404d68f8 n/a (libKirigami.so.6 + 0x348f8) #6 0x7ea2404d85bf n/a (libKirigami.so.6 + 0x365bf) #7 0x7ea24f559358 _ZN23QCoreApplicationPrivate29sendThroughObjectEventFiltersEP7QObjectP6QEvent (libQt6Core.so.6 + 0x159358) #8 0x7ea2506fed8e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfed8e) #9 0x7ea24f55a018 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x15a018) #10 0x7ea251771bf0 _ZN26QQuickDeliveryAgentPrivate36deliverSinglePointEventUntilAcceptedEP13QPointerEvent (libQt6Quick.so.6 + 0x371bf0) #11 0x7ea251779118 _ZN19QQuickDeliveryAgent5eventEP6QEvent (libQt6Quick.so.6 + 0x379118) #12 0x7ea25166d5f8 _ZN12QQuickWindow5eventEP6QEvent (libQt6Quick.so.6 + 0x26d5f8) #13 0x7ea2506fed9e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfed9e) #14 0x7ea24f55a018 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x15a018) #15 0x7ea24fd8bbfa _ZN22QGuiApplicationPrivate17processWheelEventEPN29QWindowSystemInterfacePrivate10WheelEventE (libQt6Gui.so.6 + 0x18bbfa) #16 0x7ea24fe0d0c4 _ZN22QWindowSystemInterface22sendWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x20d0c4) #17 0x7ea24fe0d2b7 _ZN22QWindowSystemInterface23flushWindowSystemEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Gui.so.6 + 0x20d2b7) #18 0x7ea24f5a54aa _ZN7QObject5eventEP6QEvent (libQt6Core.so.6 + 0x1a54aa) #19 0x7ea2506fed9e _ZN19QApplicationPrivate13notify_helperEP7QObjectP6QEvent (libQt6Widgets.so.6 + 0xfed9e) #20 0x7ea24f55a018 _ZN16QCoreApplication15notifyInternal2EP7QObjectP6QEvent (libQt6Core.so.6 + 0x15a018) #21 0x7ea24f55a3f2 _ZN23QCoreApplicationPrivate16sendPostedEventsEP7QObjectiP11QThreadData (libQt6Core.so.6 + 0x15a3f2) #22 0x7ea24f7cfea8 n/a (libQt6Core.so.6 + 0x3cfea8) #23 0x7ea24e72e1e4 n/a (libglib-2.0.so.0 + 0x5e1e4) #24 0x7ea24e791e97 n/a (libglib-2.0.so.0 + 0xc1e97) #25 0x7ea24e72d615 g_main_context_iteration (libglib-2.0.so.0 + 0x5d615) #26 0x7ea24f7cd59d _ZN20QEventDispatcherGlib13processEventsE6QFlagsIN10QEventLoop17ProcessEventsFlagEE (libQt6Core.so.6 + 0x3cd59d) #27 0x7ea24f565376 _ZN10QEventLoop4execE6QFlagsINS_17ProcessEventsFlagEE (libQt6Core.so.6 + 0x165376) #28 0x7ea24f55d159 _ZN16QCoreApplication4execEv (libQt6Core.so.6 + 0x15d159) #29 0x61436cf2141d n/a (/usr/bin/kdeconnect-sms + 0x1041d) #30 0x7ea24ee376b5 n/a (libc.so.6 + 0x276b5) #31 0x7ea24ee37769 __libc_start_main (libc.so.6 + 0x27769) #32 0x61436cf21675 n/a (/usr/bin/kdeconnect-sms + 0x10675) Stack trace of thread 1756916: #0 0x
[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236 John Kizer changed: What|Removed |Added Resolution|--- |BACKTRACE CC||john.ki...@proton.me Status|REPORTED|NEEDSINFO --- Comment #1 from John Kizer --- Hi - If something crashed, we need a backtrace of it so we can figure out what's going on. Can you please attach a backtrace of the crash using the coredumpctl command-line program, as detailed in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl? Thanks! -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236 Bug Janitor Service changed: What|Removed |Added Severity|critical|crash -- You are receiving this mail because: You are watching all bug changes.
[kdeconnect] [Bug 504236] QML ConversationDisplay - crashes upon scrolling through any particular sms message tree
https://bugs.kde.org/show_bug.cgi?id=504236 ryan changed: What|Removed |Added Component|macos-application |messaging-application Assignee|turx2...@gmail.com |si...@ergotech.com -- You are receiving this mail because: You are watching all bug changes.
