Date: Thu, 13 Jun 2019 19:36:26 +0000 From: Dale Brazelton <dalebrazelton@outlook.com> To: Johannes Lundberg <johalun@FreeBSD.org>, Greg V <greg@unrelenting.technology> Cc: "x11@freebsd.org" <x11@freebsd.org> Subject: Re: Sway, Wayland, and Xwayland Message-ID: <MWHPR19MB1533F831FF9399393762104FA7EF0@MWHPR19MB1533.namprd19.prod.outlook.com> In-Reply-To: <bf0951a2-2d6c-5d57-8cc0-82247390be7c@FreeBSD.org> References: <MWHPR19MB1533A40AB67B06DE58DA3CECA7130@MWHPR19MB1533.namprd19.prod.outlook.com> <lfy8-x4i7-wny@FreeBSD.org> <3112c733-c168-8683-892f-d3042b136ec7@FreeBSD.org> <1560288228.78549.0@unrelenting.technology>, <bf0951a2-2d6c-5d57-8cc0-82247390be7c@FreeBSD.org>
next in thread | previous in thread | raw e-mail | index | archive | help
Even after implementing all the suggestions from Jan I was unable to get fi= refox to work in sway, neither natively in wayland or with xwayland. After = spending a good part of yesterday testing it, I'm convinced my problems are= due to the implementation of amdgpu in FreeBSD 12 stable. For example, I c= ould only run sway once per boot. If I ever exited sway and tried to restar= t it my computer would hang and I'd have to power it off. (I realize I'm pr= obably the only person in the world trying to run a FreeBSD desktop on an a= md Vega 64 graphics card!) I'll postpone further testing until we have a mo= re up to date amdgpu, mesa, xorg-server, and xwayland in 12 stable. Thanks = to everyone for your help and suggestions! Get Outlook for Android<https://aka.ms/ghei36>; ________________________________ From: Johannes Lundberg <johalun@FreeBSD.org> Sent: Thursday, June 13, 2019 1:32:55 AM To: Greg V Cc: Dale Brazelton; x11@freebsd.org Subject: Re: Sway, Wayland, and Xwayland On 6/11/19 2:23 PM, Greg V wrote: > > > On Mon, Jun 10, 2019 at 19:24, Johannes Lundberg <johalun@FreeBSD.org> > wrote: >> On 6/10/19 7:03 PM, Jan Beich wrote: >>> (CC'ing appropriate public list. I don't help privately.) >>> >>> Dale Brazelton <dalebrazelton@outlook.com> writes: >>> >>>> I've managed to get Sway working but am >>>> unable to get any X11 apps to work thru xwayland. For instance if I >>>> start sway and then start firefox from my terminal app (alacritty) >>>> nothing happens. >>> >>> Did you change any port options in x11-wm/sway or one of its >>> dependencies? >>> Did you define LIBGL_DRI3_ENABLE=3D1 in environ(7) to avoid llvmpipe >>> fallback? >>> Does $DISPLAY in alacritty session and Xwayland 1st argument in >>> ps(1) match? >>> Can you show "sway -d" output? IIRC, Sway starts Xwayland on first >>> use. >>> Can you try "firefox --new-instance --profile $(mktemp -dt >>> ffprofile)"? >> Other simple X apps like xclock, or even glxgears that need Xwayland run >> but are not displayed. The window seem to be simply hidden. IIRC there >> was a fix to this but I can't remember what that was. I tried >> enable/disable DRI3 but to no success... > > Xwayland windows not displaying is the good old ioctl permission thing: > > >>> > https://eur04.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithu= b.com%2FFreeBSDDesktop%2Fkms-drm%2Fissues%2F33%23issuecomment-422793245&= ;data=3D02%7C01%7C%7C8d0d2c69c1c54b08b87908d6efc8fc0b%7C84df9e7fe9f640afb43= 5aaaaaaaaaaaa%7C1%7C0%7C636960043831829889&sdata=3DNCuhVs7zzeHl00HpMz9G= nkFVitew2jsM1DmqfteM5sU%3D&reserved=3D0 > <<< > > ^^^ maybe it's time to merge my workaround since no one's found the > root cause ^^^ Looks like this is fixed in Xorg 1.20. I built my xorg-server and xwayland packages from our dev branch here https://eur04.safelinks.protection.outlook.com/?url=3Dhttps%3A%2F%2Fgithub.= com%2FFreeBSDDesktop%2Ffreebsd-ports%2Ftree%2Ffeature%2Fxserver-1.20&da= ta=3D02%7C01%7C%7C8d0d2c69c1c54b08b87908d6efc8fc0b%7C84df9e7fe9f640afb435aa= aaaaaaaaaa%7C1%7C0%7C636960043831829889&sdata=3DB3tydJ2J7N3qUWAO47A9fxZ= FwOOZB%2BLPz%2B4x%2Bp%2FKuOQ%3D&reserved=3D0 and tested myself. Hopefully we can get 1.20 out soon... > >
Want to link to this message? Use this URL: <https://mail-archive.FreeBSD.org/cgi/mid.cgi?MWHPR19MB1533F831FF9399393762104FA7EF0>