Summary: | Crash during use of Sublimetext4 | ||
---|---|---|---|
Product: | [I don't know] kde | Reporter: | Steven <geconsultant> |
Component: | general | Assignee: | Unassigned bugs mailing-list <unassigned-bugs> |
Status: | RESOLVED WORKSFORME | ||
Severity: | normal | CC: | cwo.kde, geconsultant |
Priority: | NOR | ||
Version: | unspecified | ||
Target Milestone: | --- | ||
Platform: | Debian stable | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: | |||
Attachments: | debug report |
Description
Steven
2024-04-19 19:47:46 UTC
Created attachment 168694 [details]
debug report
Thank you for the bug report! Unfortunately I can't reproduce the crash myself on current git master, and the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: #8 0x00007f960aa01a9b in ?? () from /lib/x86_64-linux-gnu/libkdeinit5_kfmclient.so #9 0x00007f960aa03088 in ?? () from /lib/x86_64-linux-gnu/libkdeinit5_kfmclient.so #10 0x00007f960aa042c5 in kdemain () from /lib/x86_64-linux-gnu/libkdeinit5_kfmclient.so 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. Thanks again! ๐๐งน โ ๏ธ 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! ๐๐งน This bug has been in NEEDSINFO status with no change for at least 30 days. Closing as RESOLVED WORKSFORME. |