5 ms·

Funny thing: I was on sway full time for over a year, nearly 2 actually. I went so far as to uninstall i3 (not XWayland, nor X for obvious reasons) Since a few

Funny thing: I was on sway full time for over a year, nearly 2 actually. I went so far as to uninstall i3 (not XWayland, nor X for obvious reasons) Since a few months I noticed weird (complete) freezes/crashes on my pc, while gaming... it's not the youngest so I thought it may come to end of life. Out of curiosity I reinstalled i3 a couple of days ago and used it (only) for gaming. No crash since. I assume it's either a bug in Mesa (AMDGpu) or somewhere in the wayland stack... sway hasn't had an update since November, so... I dunno, I haven't taken the time to investigate. While working I still use sway, because I've customized it to my needs, but for Gaming/Streaming I now switch to i3 again. Nice sideeffect: I can finally play some games again that wouldn't even launch on Sway or were unplayable, like e.g. Natural Selection 2 which turned to a black screen when I switched workspaces (e.g. from one monitor to another) to e.g. tune down the music or scroll down a page while being dead. Feels funny, but more annoying :/

_bin_ 6y ago
While I respect Drew's right to keep Nvidia hardware unsupported, doing so cuts out a huge chunk of Linux video game players users. I therefore find it unsurprising that video games have a number of issues that day-to-day use cases don't. Even though this is AMD, lack of Nvidia support keeps Xorg as the default for video games, and this means worse AMD support too.
- OtomotO 6y ago
  Personally I don't see how supporting the proprietary nvidia drivers would help my situation as I am using Mesa (and Noveau is supported afaik (?!)) but I assume there is a kernel of truth in there that a lot of people cannot/won't even consider sway because they are on proprietary nvidia stacks. - I wrote before the edit -
- ubercow13 6y ago
  The main thing up to now keeping Xorg the default for video games was nVidia's lack of Xwayland acceleration support, which made gaming on Wayland largely impossible regardless of wlroots.
  - toggleton 6y ago
    And if i uunderstand it right is xwayland acceleration in work for the 470 Driver Release https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/587#note_799560 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...
- kaba0 6y ago
  It’s not like a decision based on he doesn’t like nvidia — they would pretty much have to rewrite the whole rendering pipeline for a completely separate model. It simply won’t happen unless the kernel guys can do something and bring nvidia prop drivers to behave well with the kernel abstraction wlroots (and thus sway) sits on top, or someone(s) reimplement the whole thing yet again (and then maintain basically two codebases with twice the bugs)
OtomotO 6y ago
Another frustrating experience was OBS. It would crash quite often due to a bug in qtwayland that someone from the community fixed (can't find the ticket right now) - had to do with too many events queuing up if it was in background and re-focused. If you read this kind stranger: Thank you so much for this fix! One thing that doesn't work to this date for me is custom browser docks, which means if you stream and want to interact with your viewers, you need to have a browser open as well :/
boudin 6y ago
I have similar issues, those seems to be related to the xwayland implementation of wlroots/sway. I do not have those issues with Gnome on wayland. Looking at the master branch of the project, it seems that it should get better with the next version.
- OtomotO 6y ago
  That's great to hear. I wish they would release more often. I tried to build sway-git twice during the last 2 weeks. Just from the AUR, because I was feeling lazy after work. It failed twice and I just reverted back to sway 1.5.x because I couldn't bother to learn yet another build-tool and dive into C again. (Yes, I am one of those developers)
MayeulC 6y ago
Eeh, I did play NS2 some time ago without a black screen. Some games seem to have a focus issue when launched trough proton, though. I do have lockups on Risk of Rain 2, Deep Rock Galactic and a few others: https://gitlab.freedesktop.org/mesa/mesa/-/issues/864 https://gitlab.freedesktop.org/mesa/mesa/-/issues/864 I thought of using another installation, with and without flatpak, but hadn't thought of launching outside of sway, since the crash issue after a while. I'll try lxqt, which I'm currently falling back to for VR (waiting for https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/49 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m... ). Symptoms are: a black screen, and nothing responds. No SysRq, no network. Nothings gets written to the logs. I tried leveraging pstore without success. My GPU is an AMD R9 Fury, which I thought was defective (bought refurbished).
- MayeulC 6y ago
  OK, re-tested, it also happens on LXQT, so no wayland-related. I still have to test that GPU in another computer to be sure, and also try AMDVLK, though that seems relatively complex with the steam flatpak.

_bin_ 6y ago

While I respect Drew's right to keep Nvidia hardware unsupported, doing so cuts out a huge chunk of Linux video game players users. I therefore find it unsurprising that video games have a number of issues that day-to-day use cases don't. Even though this is AMD, lack of Nvidia support keeps Xorg as the default for video games, and this means worse AMD support too.

OtomotO 6y ago
Personally I don't see how supporting the proprietary nvidia drivers would help my situation as I am using Mesa (and Noveau is supported afaik (?!)) but I assume there is a kernel of truth in there that a lot of people cannot/won't even consider sway because they are on proprietary nvidia stacks. - I wrote before the edit -
ubercow13 6y ago
The main thing up to now keeping Xorg the default for video games was nVidia's lack of Xwayland acceleration support, which made gaming on Wayland largely impossible regardless of wlroots.
- toggleton 6y ago
  And if i uunderstand it right is xwayland acceleration in work for the 470 Driver Release https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests/587#note_799560 https://gitlab.freedesktop.org/xorg/xserver/-/merge_requests...
kaba0 6y ago
It’s not like a decision based on he doesn’t like nvidia — they would pretty much have to rewrite the whole rendering pipeline for a completely separate model. It simply won’t happen unless the kernel guys can do something and bring nvidia prop drivers to behave well with the kernel abstraction wlroots (and thus sway) sits on top, or someone(s) reimplement the whole thing yet again (and then maintain basically two codebases with twice the bugs)

OtomotO 6y ago

Another frustrating experience was OBS. It would crash quite often due to a bug in qtwayland that someone from the community fixed (can't find the ticket right now) - had to do with too many events queuing up if it was in background and re-focused. If you read this kind stranger: Thank you so much for this fix! One thing that doesn't work to this date for me is custom browser docks, which means if you stream and want to interact with your viewers, you need to have a browser open as well :/

boudin 6y ago

I have similar issues, those seems to be related to the xwayland implementation of wlroots/sway. I do not have those issues with Gnome on wayland. Looking at the master branch of the project, it seems that it should get better with the next version.

OtomotO 6y ago
That's great to hear. I wish they would release more often. I tried to build sway-git twice during the last 2 weeks. Just from the AUR, because I was feeling lazy after work. It failed twice and I just reverted back to sway 1.5.x because I couldn't bother to learn yet another build-tool and dive into C again. (Yes, I am one of those developers)

MayeulC 6y ago

Eeh, I did play NS2 some time ago without a black screen. Some games seem to have a focus issue when launched trough proton, though. I do have lockups on Risk of Rain 2, Deep Rock Galactic and a few others: https://gitlab.freedesktop.org/mesa/mesa/-/issues/864 https://gitlab.freedesktop.org/mesa/mesa/-/issues/864 I thought of using another installation, with and without flatpak, but hadn't thought of launching outside of sway, since the crash issue after a while. I'll try lxqt, which I'm currently falling back to for VR (waiting for https://gitlab.freedesktop.org/wayland/wayland-protocols/-/merge_requests/49 https://gitlab.freedesktop.org/wayland/wayland-protocols/-/m... ). Symptoms are: a black screen, and nothing responds. No SysRq, no network. Nothings gets written to the logs. I tried leveraging pstore without success. My GPU is an AMD R9 Fury, which I thought was defective (bought refurbished).

MayeulC 6y ago
OK, re-tested, it also happens on LXQT, so no wayland-related. I still have to test that GPU in another computer to be sure, and also try AMDVLK, though that seems relatively complex with the steam flatpak.