5 ms·

Firefox Wayland is still kind of iffy when I have the Nvidia driver enabled on either of my AMD CPU/Nvidia GPU machines. Sometimes it doesn't launch, among othe

Firefox Wayland is still kind of iffy when I have the Nvidia driver enabled on either of my AMD CPU/Nvidia GPU machines. Sometimes it doesn't launch, among other unreproducable things. Of course it works perfectly if I disable the Nvidia driver. It also works fine in XWayland, but then rendering (to my eyes) looks choppier.

whalesalad 3y ago
Firefox is one of the few apps that works flawlessly for me in Wayland (w/o xwayland). Slack is almost there, but not perfect. My cursor becomes like 1/10th the size in Slack .. but the crisp rendering is worth it. Dragging a PNG file into it never works though, so I always need to upload via the little + button. Spotify is 100% flawless, to my surprise. Even works flawlessly with the whole device handoff thing between iPhone, my Macbook, etc. vscode renders much better with wayland, like the latency difference is pretty significant. but... I use Toshy to get macos keybindings on Linux and those fail to work when vscode is booted in wayland mode ... so I am still suffering with xwayland. If I do not think about it, I don't mind lol. If I go back to native and see how much better rendering is, I feel sad.
- brucethemoose2 3y ago
  Chromium and Electron are the big kickers for me. All GPU acceleration is (silently) broken in true native Wayland when Nvidia is active. It mostly looks fine until I stress the UI, and I can see significantly more CPU being used. In fact, I only really know its busted in VSCode because it spits out the same errors in the console as Chromium (where I can check about:gpu and see that everything is off).
  - bootsmann 3y ago
    Same here, but for me using launch options to force chromium apps to use wayland with ozone has fixed most of the issues. Pretty convinced its the combination of NVIDIA/XWayland/Electron that is particularly cursed.
- omnimus 3y ago
  I need wayland for correct 200% scaling on one screen. Firefox seems to work without issues. VSCode worked for some time until some update. I have no idea what changed :(. Also its so weird that i have to launch it with some flags but they also show as errors... How to enable VSCode wayland is mystery to me.
  - whalesalad 3y ago
    Afaik you edit your .desktop file and pass flags to tell it to use ozone. --enable-features=UseOzonePlatform --ozone-platform=wayland

whalesalad 3y ago

Firefox is one of the few apps that works flawlessly for me in Wayland (w/o xwayland). Slack is almost there, but not perfect. My cursor becomes like 1/10th the size in Slack .. but the crisp rendering is worth it. Dragging a PNG file into it never works though, so I always need to upload via the little + button. Spotify is 100% flawless, to my surprise. Even works flawlessly with the whole device handoff thing between iPhone, my Macbook, etc. vscode renders much better with wayland, like the latency difference is pretty significant. but... I use Toshy to get macos keybindings on Linux and those fail to work when vscode is booted in wayland mode ... so I am still suffering with xwayland. If I do not think about it, I don't mind lol. If I go back to native and see how much better rendering is, I feel sad.

brucethemoose2 3y ago
Chromium and Electron are the big kickers for me. All GPU acceleration is (silently) broken in true native Wayland when Nvidia is active. It mostly looks fine until I stress the UI, and I can see significantly more CPU being used. In fact, I only really know its busted in VSCode because it spits out the same errors in the console as Chromium (where I can check about:gpu and see that everything is off).
- bootsmann 3y ago
  Same here, but for me using launch options to force chromium apps to use wayland with ozone has fixed most of the issues. Pretty convinced its the combination of NVIDIA/XWayland/Electron that is particularly cursed.
omnimus 3y ago
I need wayland for correct 200% scaling on one screen. Firefox seems to work without issues. VSCode worked for some time until some update. I have no idea what changed :(. Also its so weird that i have to launch it with some flags but they also show as errors... How to enable VSCode wayland is mystery to me.
- whalesalad 3y ago
  Afaik you edit your .desktop file and pass flags to tell it to use ozone. --enable-features=UseOzonePlatform --ozone-platform=wayland