| Summary: | Wayland compositor crashed when changing display scale of primary monitor from 300% to 200%. | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Roke Julian Lockhart Beedell <4wy78uwh> |
| Component: | wayland-generic | Assignee: | Roke Julian Lockhart Beedell <4wy78uwh> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | nate, nicolas.fella |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 5.27.0 | ||
| Target Milestone: | --- | ||
| Platform: | unspecified | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Screenshot of output of sudo + initial command specified by documentation. | ||
|
Description
Roke Julian Lockhart Beedell
2023-02-25 19:22:23 UTC
Unfortunately this bug report only has a crash of the akonadi server. Can you attach a backtrace for kwin_wayland? (In reply to Nate Graham from comment #1) > Unfortunately this bug report only has a crash of the akonadi server. Can > you attach a backtrace for kwin_wayland? Glad to. Do you have the specific commands to run? I don't know how to. If this report looks like it's missing something (such as the desired backtrace) that might be because I had to force-kill drkonqi after about an hour of it endlessly "submitting report". (In reply to Nate Graham from comment #3) > Yep, see > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl. That documentation is vaguely confusing, and anyway, I don't have the time currently to read through it. Can you just tell me the exact commands to run? I'm happy to provide the output, if the logs still exist. I'm using the same system and OS, so ideally they should. The section I linked you to tells you exactly what you need to do. I can't give you the commends myself because they will be different depending on the output of `coredumpctl --reverse`. Created attachment 157341 [details] Screenshot of output of sudo + initial command specified by documentation. (In reply to Nate Graham from comment #5) > The section I linked you to tells you exactly what you need to do. I can't > give you the commends myself because they will be different depending on the > output of `coredumpctl --reverse`. My last log is from 2023-03-03T13:54:10+0000 rather than 2023-02-25T19:22Z, which appears to be when bugzilla reports that this reported. Reckon that the log has been lost? 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! Still waiting for a backtrace of the crashing kwin_wayland process. We can't move forward without it. 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! |