Summary: | Crash KDE System Preferences | ||
---|---|---|---|
Product: | [Applications] systemsettings | Reporter: | Javier <javier> |
Component: | kcm_kscreen | Assignee: | kscreen-bugs-null <kscreen-bugs-null> |
Status: | RESOLVED WORKSFORME | ||
Severity: | crash | CC: | bednarczyk.pawel, nate, plasma-bugs |
Priority: | NOR | Keywords: | drkonqi |
Version: | 5.26.4 | ||
Target Milestone: | --- | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Javier
2022-12-05 01:17:58 UTC
Thank you for the bug report! Unfortunately the backtrace is incomplete and missing debug symbols for the following lines that we need to figure out exactly what's going wrong: > #4 0x00007fd8f04d3101 in KScreen::Config::clone() const () from /usr/lib/libKF5Screen.so.7 > #5 0x00007fd8f05491dd in ?? () from /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_kscreen.so > #6 0x00007fd8f0549ed3 in ?? () from /usr/lib/qt/plugins/plasma/kcms/systemsettings/kcm_kscreen.so Could you please install debug symbols for kscreen, reproduce the crash, and attach a new symbolicated backtrace? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports The backtrace looks similar to the one in Bug 447199, but it's impossible to be sure without the fully symbolicated backtrace. If it's the same, I'll mark this as a duplicte of Bug 447199 and re-open it since apparently the issue is still present. Thanks again! since the reporter seems to be on Arch, here is what you can do: -make sure Debuginfod is enabled: https://wiki.archlinux.org/title/Debuginfod -install gdb -find the crash dump pid: > $ coredumpctl list --reverse -coredumpctl gdb 4469 in terminal (replace 4469 with pid of the crashing process). GDB will read and download the missing symbols - once in gdb prompt execute set logging enabled on and then thread apply all bt full gdb.txt file will be saved in your homr folder, you can attach it here. Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. 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. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone! |