| Summary: | Pressing Ctrl+C on KDE Plasma Wayland logs out the user immediately (FreeBSD 14.3) | ||
|---|---|---|---|
| Product: | [Plasma] kwin | Reporter: | Chris <christer.edwards> |
| Component: | wayland-generic | Assignee: | KWin default assignee <kwin-bugs-null> |
| Status: | RESOLVED DOWNSTREAM | ||
| Severity: | normal | CC: | grahamperrin, hunter2k1, nate, rmavella+kde |
| Priority: | NOR | Keywords: | wayland-only |
| Version First Reported In: | 6.3.5 | ||
| Target Milestone: | --- | ||
| Platform: | FreeBSD Ports | ||
| OS: | FreeBSD | ||
| See Also: | https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286592 | ||
| Latest Commit: | Version Fixed In: | ||
| Sentry Crash Report: | |||
|
Description
Chris
2025-06-12 22:21:24 UTC
Well that doesn't sound like it's supposed to happen. :) Without logs it's hard to be sure, but my first guess is that this triggers a Wayland protocol error that causes KWin to close. Can you attach the output of `journalctl --user-unit plasma-kwin_wayland --boot 0`? 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! Sorry for the delay. Trouble is, FreeBSD does not use systemd/journalctl so I'm not able to provide the logs as requested. I can try to provide different logs, but in my searching I haven't found much that is useful (but perhaps I'm not looking in the right place). I have discussed the issue with a handful of other FreeBSD users and they can all reproduce the issue. If you have any suggestions on alternate logs to review, let me know. Until then, I'm back on KDE on X11 and it's not nearly as functional as the Wayland edition, but this bug is too much of a showstopper to use. (In reply to Chris from comment #3) > Sorry for the delay. Trouble is, FreeBSD does not use systemd/journalctl so > I'm not able to provide the logs as requested. I can try to provide > different logs, but in my searching I haven't found much that is useful (but > perhaps I'm not looking in the right place). > > I have discussed the issue with a handful of other FreeBSD users and they > can all reproduce the issue. > > If you have any suggestions on alternate logs to review, let me know. Until > then, I'm back on KDE on X11 and it's not nearly as functional as the > Wayland edition, but this bug is too much of a showstopper to use. The problem is that none of us (kwin developers) have experience with FreeBSD. I asked FreeBSD developers for help regarding this issue. Maybe of interest: Peter Wemm's response to <https://mastodon.bsd.cafe/@grahamperrin/114888161580474815>. 🐛🧹 ⚠️ This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information, then set the bug status to REPORTED. If there is no change for at least 30 days, it will be automatically closed as RESOLVED WORKSFORME. For more information about our bug triaging procedures, please read https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging. Thank you for helping us make KDE software even better for everyone! (In reply to Chris from comment #0) > The screen briefly flashes a log message (too fast to read), and then > returns to the SDDM login manager. I managed to capture a few frames of this on video, they were all of the form "hdac0: Command 0x20373100 timeout on address 2." This looks like lines from dmesg so I'm not sure if it is helpful, maybe there is an even quicker message that I haven't captured on frame yet. I also see some core dumps from baloo_file earlier in dmesg but again, probably not the culprit, this has been a longstanding issue for me even before the Ctrl+C bug. It's not a KDE-specific issue. I have found that launching any Wayland sessions from SDDM in an environment that has no elogind or systemd-logind (such as my distro PCLinuxOS, CRUX, Venom, or FreeBSD in your case) will cause it to exhibit shell-like behavior where pressing Ctrl + C crashes the entire session. Using greetd works. Sounds like an integration issue that the FreeBSD folks should know about! |