Re: sway-1.2_1 crashes
Jan Beich <[email protected]>
| Newsgroups | gmane.os.freebsd.devel.x11 |
|---|---|
| Message-ID | <[email protected]> |
John Kennedy <[email protected]> writes: > On Fri, Oct 11, 2019 at 10:24:09AM +0200, Tamas Szakaly wrote: > >> Hi, >> I've already left a comment on the Sway issue, but thought I should also >> mention it here, that the broken VT switching is not a sway/wlroots issue, but >> a libepoll-shim one. See https://github.com/jiixyj/epoll-shim/pull/7 for >> details. VT switching works on my 13.0-CURRENT HardenedBSD system with the >> latest version of libepoll-shim from jiixyj's repo. >> >> I think that issue could cause other weird behaviour too, so maybe it worth >> checking if these crashes occur with the latest version of libepoll-shim. > > On Thu, 10 Oct 2019 19:54:28 +0200, Jan Beich wrote: >> VT switching is broken in Sway, see https://github.com/swaywm/sway/issues/3612 >> Other than direct session Sway can use ConsoleKit2 if wlroots is built with >> CONSOLEKIT port option enabled. But I don't remember if it helps VT swich issue. > > It looks like you (Tamas) and Jan are talking about the same thing. > > Jan's link eventually leads to this: > > https://github.com/freebsd/freebsd-ports/commit/a7c3fd3d428e That didn't land in the mainline. I've used a commit from Greg's repo[1] (frequently rebased) to save time on testing. GitHub allows referencing commits from any fork, so one has to pay attention to tags and branches a commit exists in. Using the original repo instead of a fork allows to reference a commit even if the fork is removed or renamed but if the commit is orphaned for prolonged time it maybe garbage-collected. -- [1] https://github.com/myfreeweb/freebsd-ports-dank/commits/lite A lot of stuff have been submitted on bugzilla but not everything. _______________________________________________ [email protected] mailing list https://lists.freebsd.org/mailman/listinfo/freebsd-x11 To unsubscribe, send any mail to "[email protected]"