Created attachment 588858 [details] emerge --info I updated to gui-libs/wlroots-0.7.0 on Fri Aug 30 at 08:50:22 2019 EDT. I already had sway running at the time, so it wasn't until I had logged out and tried to restart sway that I realized I was unable. Logs are a little hard to come by, because my computer hard-locked as soon as I attempted to start sway; however, I will try to get the output of sway started in --debug --verbose mode. I recall that there was a message something like "logind: user has no sessions". I was able to get back in by downgrading gui-libs/wlroots to 0.6.0, however, that was made harder by the fact that gui-wm/sway-1.2 is now pinned to gui-libs/wlroots-0.7.0; I had to revert /usr/portage to before commit 6908a1d to get back to the functional state my machine was in on Wednesday and Thursday last week. I am now on gui-wm/sway-1.2 with gui-libs/wlroots-0.6.0 and it works very nicely, but I will have to go through some contortions to keep /usr/portage sane and not upgrade sway and wlroots until this is resolved.
Created attachment 591290 [details] sway --debug --verbose stderr with wlroots-0.6.0 Here is the standard error of sway --debug --verbose when I'm using wlroots-0.6.0
Created attachment 591292 [details] sway --debug --verbose stderr with wlroots-0.7.0 Here is the standard error of sway --debug --verbose with wlroots-0.7.0, which appears make the entire machine unresponsive.
(In reply to michael@smith-li.com from comment #2) > Created attachment 591292 [details] > sway --debug --verbose stderr with wlroots-0.7.0 > > Here is the standard error of sway --debug --verbose with wlroots-0.7.0, > which appears make the entire machine unresponsive. Are you still having this issue with 0.8.0? Also, this may be a bug that needs to be opened upstream.
Build 0.8.1-r1 over the weekend. It's still behaving almost the same way, although I did notice that my computer seemed to shut itself down after the freeze when I waited a minute. I am happy to open a bug upstream, but what I'm asking Gentoo maintainers to do is to keep wlroots-0.6.0 in portage until this is resolved, since that is the only version that works and it's a slog to have to roll back, manifest, and patch sway to accept it every time there's an update.
The bug has been closed via the following commit(s): https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=cf2fe59269cd5db1fbec28717e9efeafe937c959 commit cf2fe59269cd5db1fbec28717e9efeafe937c959 Author: Aaron Bauman <bman@gentoo.org> AuthorDate: 2019-11-13 03:46:57 +0000 Commit: Aaron Bauman <bman@gentoo.org> CommitDate: 2019-11-13 03:46:57 +0000 gui-libs/wlroots: restore 0.6.0 per user request Closes: https://bugs.gentoo.org/693376 Signed-off-by: Aaron Bauman <bman@gentoo.org> gui-libs/wlroots/Manifest | 1 + gui-libs/wlroots/wlroots-0.6.0.ebuild | 77 +++++++++++++++++++++++++++++++++++ 2 files changed, 78 insertions(+)
