Bug 445460 - [kded5] Systemd-coredump
Summary: [kded5] Systemd-coredump
Status: RESOLVED WORKSFORME
Alias: None
Product: frameworks-kded
Classification: Frameworks and Libraries
Component: general (other bugs)
Version First Reported In: 5.87.0
Platform: Arch Linux Linux
: NOR minor
Target Milestone: ---
Assignee: David Faure
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2021-11-14 07:36 UTC by kded5coredump
Modified: 2021-12-04 19:24 UTC (History)
2 users (show)

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


Attachments
Coredump_Logfile (36.91 KB, text/x-log)
2021-11-14 07:36 UTC, kded5coredump
Details
thread apply all bt full (5.56 KB, text/x-log)
2021-11-27 23:04 UTC, kded5coredump
Details

Note You need to log in before you can comment on or make changes to this bug.
Description kded5coredump 2021-11-14 07:36:48 UTC
Created attachment 143531 [details]
Coredump_Logfile

SUMMARY
***
I was monitoring  Journalctl and noticed Systemd was core dumping kded5. 
I haven't noticed any issues (performance or graphical) using the desktop and only reported due to Systemd's recommendation,
"This usually indicates a programming error in the crashing program and should be reported to its vendor as a bug" 
***


STEPS TO REPRODUCE


OBSERVED RESULT


EXPECTED RESULT


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux x86_64  / 5.23.3-1
(available in About System)
KDE Plasma Version: plasma-desktop 5.23.3-1
KDE Frameworks Version: plasma-framework 5.87.0-1 
Qt Version: qt5-base 5.15.2+kde+r254-1

ADDITIONAL INFORMATION
More than happy to supply with more information, ask away.
Comment 1 Nate Graham 2021-11-23 18:54:33 UTC
Can you please use the core dump file to get a backtrace that shows the crashing thread? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
Comment 2 kded5coredump 2021-11-27 14:03:57 UTC
(In reply to Nate Graham from comment #1)
> Can you please use the core dump file to get a backtrace that shows the
> crashing thread? See
> https://community.kde.org/Guidelines_and_HOWTOs/Debugging/
> How_to_create_useful_crash_reports

Hi, Sorry for the late reply. 
I recompiled kded with debug options for a backtrace and tried to crash it, however nothing happened. I could be the new version of kded ( 5.88.0-1) that fixed the issue or something else. 

Should I keep this issue open or close it. 
if it crashes again I will update this issue whether its closed or open. 

Happy Holidays!
Comment 3 kded5coredump 2021-11-27 23:03:39 UTC
I got it to crash, hopefully the back trace is usefull. 
Filename: kded5_backtrace.log
Comment 4 kded5coredump 2021-11-27 23:04:26 UTC
Created attachment 144013 [details]
thread apply all bt full

backtrace without paging
Comment 5 Nate Graham 2021-11-29 20:15:02 UTC
#4  0x00007f7ca80a79e8 in  () at /usr/lib/qt/plugins/kf5/kded/kded_touchpad.so

Thanks. Now we know that it's something in the touchpad kded plugin. Unfortunately because you're using Arch, there are no debug symbols so it's impossible to know what's causing it. Can you recompile plasma with debug symbols and get a useful backtrace that shows us where in the plugin it's crashing?

See https://wiki.archlinux.org/title/Debugging/Getting_traces
Comment 6 kded5coredump 2021-12-04 18:54:01 UTC
(In reply to Nate Graham from comment #5)
> #4  0x00007f7ca80a79e8 in  () at
> /usr/lib/qt/plugins/kf5/kded/kded_touchpad.so
> 
> Thanks. Now we know that it's something in the touchpad kded plugin.
> Unfortunately because you're using Arch, there are no debug symbols so it's
> impossible to know what's causing it. Can you recompile plasma with debug
> symbols and get a useful backtrace that shows us where in the plugin it's
> crashing?
> 
> See https://wiki.archlinux.org/title/Debugging/Getting_traces

I have been trying to crash it again for the past couple days and it just won't crash. Maybe the new version of plasma-desktop [5.23.4] fixed this issue.
Comment 7 Nate Graham 2021-12-04 19:24:26 UTC
OK, well let us know if it happens again!