| Summary: | Plasmashell crashes on Arma 3 launch through steam. | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | grappastudiols <grappastudiols> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | kde, nate |
| Priority: | NOR | ||
| Version First Reported In: | 5.27.2 | ||
| Target Milestone: | --- | ||
| Platform: | Arch Linux | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed/Implemented In: | ||
| Sentry Crash Report: | |||
|
Description
grappastudiols@gmail.com
2023-03-01 17:15:13 UTC
> The Wayland connection broke. Did the Wayland compositor die This generally means that kwin_wayland crashed. Can you get a backtrace of the crash, perhaps using `coredumpctl`? See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl (In reply to Nate Graham from comment #1) > > The Wayland connection broke. Did the Wayland compositor die > This generally means that kwin_wayland crashed. Can you get a backtrace of > the crash, perhaps using `coredumpctl`? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl There's no process related with kwin_wayland nor plasmashell to choose from. After crash occurrence of course. If kwin_wayland would crash wouldn't title bar be affected? It seems to be present and usable. backtrace of plasmashell with gdb: https://pastebin.com/YmYk3vVe >The Wayland connection broke. Did the Wayland compositor die?
Plasmashell isn't the one that crashed, we would need a backtrace of kwin
Like I said: coredumpctl does not contain kwin_wayland after crash. Is there any way hooking to an existing process? Just checked: kwin_wayland never crashes during plasmashell crash. It's running all the way. 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! |