Created attachment 617602 [details] System Info Hi, I found a problem for the current release of weston (8.0.0). When I run weston-launch the screen is completely black but at the same time I see the mouse pointer. There are no problems to run through the X server.
Created attachment 617604 [details] Xorg Log
Created attachment 617606 [details] dmesg log
Created attachment 617610 [details] weston-launch log
I have the same problem. I tracked it down to mesa with the nouveau driver. Downgrading mesa to 18.3.6 weston works again. Another workaround is to tell weston not to use graphic acceleration (weston --use-pixman). Note also that versions of weston prior to 7 work with the present mesa version (19.3.5).
Is there a ticket upstream?
Sorry but this is almost certainly a driver issue and archiesix backs that up. Please try their suggestion and otherwise file a bug upstream.
My tests showed that there were no problems with the sway window manager for weston (8.0.0). The problem only appears when I run weston-launch in VT mode. I find it difficult to determine the cause, since there was no such problem for the previous version of weston.
Created attachment 618714 [details] equery u mesa
(In reply to vite from comment #7) > My tests showed that there were no problems with the sway window manager for > weston (8.0.0). The problem only appears when I run weston-launch in VT > mode. I find it difficult to determine the cause, since there was no such > problem for the previous version of weston. Okay but I only package Weston. This stuff is complex and mostly beyond my understanding. An issue like this would still be an upstream issue. There's been a lot of commits to master since so try 9999 to see if that helps. If it does, we can try and identify the relevant patch.
(In reply to James Le Cuirot from comment #9) > (In reply to vite from comment #7) > > My tests showed that there were no problems with the sway window manager for > > weston (8.0.0). The problem only appears when I run weston-launch in VT > > mode. I find it difficult to determine the cause, since there was no such > > problem for the previous version of weston. > > Okay but I only package Weston. This stuff is complex and mostly beyond my > understanding. An issue like this would still be an upstream issue. There's > been a lot of commits to master since so try 9999 to see if that helps. If > it does, we can try and identify the relevant patch. Unfortunately, the weston-9999 version also does not work correctly.
I have just tried it myself (I usually only test within X) and it's fine here but I have a Radeon card. I can't help much if I can't reproduce it. Do you know how to use git bisect? You can use that to build snapshots of Weston between 7.0.0 and 8.0.0. It's pretty easy to use, I actually used that before I ever used git for anything else. You wouldn't have to build it manually as you could still set EGIT_COMMIT against weston-9999 to fetch the commits that git bisect reports.
(In reply to James Le Cuirot from comment #11) > I have just tried it myself (I usually only test within X) and it's fine > here but I have a Radeon card. I can't help much if I can't reproduce it. > > Do you know how to use git bisect? You can use that to build snapshots of > Weston between 7.0.0 and 8.0.0. It's pretty easy to use, I actually used > that before I ever used git for anything else. You wouldn't have to build it > manually as you could still set EGIT_COMMIT against weston-9999 to fetch the > commits that git bisect reports. Thanks for the help, I opened a issue to the weston repository. https://gitlab.freedesktop.org/wayland/weston/issues/380
Created attachment 619030 [details] equery u weston
Apparently it now works with recent kernel versions.
