Date: Fri, 09 May 2025 11:36:57 +0000 From: bugzilla-noreply@freebsd.org To: bugs@FreeBSD.org Subject: [Bug 286692] unix(4): regressed after base d15792780760 Message-ID: <bug-286692-227@https.bugs.freebsd.org/bugzilla/>
index | next in thread | raw e-mail
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=286692 Bug ID: 286692 Summary: unix(4): regressed after base d15792780760 Product: Base System Version: 15.0-CURRENT Hardware: Any OS: Any Status: New Keywords: regression Severity: Affects Some People Priority: --- Component: kern Assignee: bugs@FreeBSD.org Reporter: 2khramtsov@gmail.com CC: glebius@FreeBSD.org x11-wm/sway starts normally, though executing a command through it, e.g. dmenu-wl (I have this in ~/.config/sway/config): set $menu dmenu-wl_path | dmenu-wl -h 30 -nb '#FFFFFF' -sb '#BFBFBF' -nf '#000000' -sf '#000000' | xargs swaymsg exec -- $ dbus-run-session seatd-launch sway ($mod+d pressed, dmenu-wl appears) (sway starts consuming 100% WCPU in top(1) output) Another config hotkey exec that causes this: $mod+End exec 'swaymsg "output * power off"' Using a hotkey that spawns x11/foot terminal through exec does not cause this issue, so maybe swaymsg reproduces this? git bisect told me this is base d15792780760 I reverted the commits fixing d15792780760 (to avoid revert d15792780760 conflicts), then reverted d15792780760, rebuilt kernel, then the issue is gone. Sorry, I can't provide a more minimal reproducer because ENOTIME. -- You are receiving this mail because: You are the assignee for the bug.home | help
Want to link to this message? Use this
URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?bug-286692-227>