| Summary: | Crash back to login screen after moving the cursor over an open app in the panel | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Claudius Ellsel <claudius.ellsel> |
| Component: | general | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | kde.org, plasma-bugs |
| Priority: | NOR | ||
| Version: | git master | ||
| Target Milestone: | --- | ||
| Platform: | Manjaro | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
| Attachments: | Backtrace attempted to get from coredump | ||
|
Description
Claudius Ellsel
2020-10-16 18:41:36 UTC
Operating System: Manjaro Linux KDE Plasma Version: 5.20.0 KDE Frameworks Version: 5.75.0 Qt Version: 5.15.1 Kernel Version: 5.8.14-1-MANJARO OS Type: 64-bit Processors: 4 × Intel® Xeon® CPU E3-1225 v3 @ 3.20GHz Memory: 11.6 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics P4600/P4700 Just happened to me again I think in a session that has been running for a longer time. I also experienced this with the compiled session from master. Might be related to https://bugs.kde.org/show_bug.cgi?id=427826. Since it crashes back to login, I guess the product should be kwin instead of just plasmashell, so changing accordingly. I will try to get a backtrace when this happens now. Not tested on X11, probably only Wayland related. Unfortunately I cannot reproduce it right now, so no backtrace. Do you have any coredumps? I don't know. I don't really know what that term means or how to get them. After a short web search I found https://blogs.kde.org/2009/03/27/setting-things-get-core-dumps and https://wiki.archlinux.org/index.php/Core_dump Still I don't have much idea how that works. Are they generated by default? If yes I can look for them if you can tell me what places to look for. Run `coredumpctl list kwin_wayland` and check if there is any relevant core dump. If there is one, run `coredumpctl gdb <pid>` to get the backtrace. Created attachment 133241 [details]
Backtrace attempted to get from coredump
There was one. Unfortunately I seemed to have not enough space available when invoking `coredumpctl gdb <pid>`.
Right after that this bug described here happened again and I was back at SDDM.
Now the previous coredump from the compiled session was missing and only the one from the normal Plasma 5.20.2 session that just crashed is available (truncated).
I hope that is alright as well.
I tried to generate a backtrace, although it seems not really successful.
This bug report is quite old and unfortunately lacks proper debug information. Can you still reproduce this issue with KDE 5.23? If so, can you please install debugging packages following the info provided in https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports, try to reproduce the bug and submit a backtrace with debugging information. 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! |