| Summary: | plasmashell exits with timeout reading from pipe | ||
|---|---|---|---|
| Product: | [Plasma] plasmashell | Reporter: | Guido Winkelmann <guido-kdebugs> |
| Component: | generic-crash | Assignee: | Plasma Bugs List <plasma-bugs-null> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | crash | CC: | nate |
| Priority: | NOR | Keywords: | wayland-only |
| Version First Reported In: | 5.24.1 | ||
| Target Milestone: | 1.0 | ||
| Platform: | Gentoo Packages | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Guido Winkelmann
2022-02-22 16:54:43 UTC
> The Wayland connection broke. Did the Wayland compositor die? This means kwin_wayland crashed. Can you get a backtrace of it using `coredumctl`? 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 means kwin_wayland crashed. Can you get a backtrace of it using > `coredumctl`? See > https://community.kde.org/Guidelines_and_HOWTOs/Debugging/ > How_to_create_useful_crash_reports#Retrieving_a_backtrace_using_coredumpctl My system does not have that utility. It looks like this a systemd utility, and I'm not running systemd. Oh, well then you can use some other method to get a backtrace of the kwin_wayland crash. Are you sure kwin_wayland crashed anyway? I'd think that would have even worse consequences, like the entire graphical session stopping to work. Oh, so no other apps died too? (In reply to Nate Graham from comment #5) > Oh, so no other apps died too? No, it was literally just plasmashell that died (as far as I could tell). All the other running applications kept running, and I could even still switch between the virtual desktops (with Ctrl-F1, Ctrl-F2 etc. because the panels were all gone) and switch between applications by moving the mouse into their windows, and when I restarted plasmashell from the konsole, everything was back to normal. Oh ok, my mistake then. Usually "The Wayland connection broke. Did the Wayland compositor die?" means that the Wayland compositor (KWin) did in fact die, but I guess that's not what happened here! In any event, we still need a backtrace of the crash to do something with this. Sorry it took me so long to get back to you. Can I ask you to upgrade to Plasma 6 (which is due to be released in 5 days) and try it again there, to see if it's still happening? If so, please use the instructions I previously provided to get a backtrace, and attach it here. Thanks a lot! (In reply to Nate Graham from comment #8) > In any event, we still need a backtrace of the crash to do something with > this. Sorry it took me so long to get back to you. Can I ask you to upgrade > to Plasma 6 (which is due to be released in 5 days) and try it again there, > to see if it's still happening? If so, please use the instructions I > previously provided to get a backtrace, and attach it here. Thanks a lot! I don't have coredumpctl on my system. I googled it and it seems that's a systemd utility, but I'm not using systemd. Then you'll have to get a backtrace of the crash the old-fashioned way, by running plasmashell in `gdb`. 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! |