Fedora 35 - Problems with Wayland + NVIDIA GPU
-
Today I just upgraded both my desktop and my Dell Inspiron Laptop to Fedora 35 from 34.
Vivaldi on the laptop (Intel I5 with Intel Uhd 620 graphics + dedicated AMD Radeon 530) + Wayland runs completely normal.
When I open Vivaldi on my desktop (Ryzen 5 5600 x + RTX 3070 (NVIDIA 495.44) ) with Wayland I just get a black window. Chrome behaves even weirder, but Firefox just starts so I presume that's a Chromium issue.
I found this thread: https://forum.vivaldi.net/topic/24429/wayland-support/2
[edit: Just tried the workaround to start Vivaldi through the terminal command but to no avail, just returns errors ...)
I this still an issue? Is Vivaldi using XWayland on my laptop und not native wayland? Is this a NVIDIA issue? Shall I just stay with XORG since I don't use any touch gestures on my desktop anyway?
-
wow, another nvidia waylander (i’m not one of them though).
[edit: Just tried the workaround to start Vivaldi through the terminal command but to no avail, just returns errors ...)
would be good to know what command you tried & what the output was.
Is Vivaldi using XWayland on my laptop und not native wayland?
check with xeyes or something… (if xeyes reacts on cursor movement over vivaldi, it’s xwl). if it works in gnome, that is.
Is this a NVIDIA issue?
Shall I just stay with XORG since I don't use any touch gestures on my desktop anyway?
you should definitely check if vivaldi works with plain xorg (i.e. not xwl).
-
welp, since she didn’t copy-paste the post from the duplicate thread, i’ll do it for her (in the hope she won’t mind).
@guigirl said in Fedora 35 - Problems with Wayland + NVIDIA GPU?:
Another data-point fyi fwiw:
Spoiler
Otoh, when i relaunch V as a full-W app [
fedora-35 $ vivaldi-snapshot --enable-features=UseOzonePlatform --ozone-platform=wayland], not Xwayland as above with the default launcher, it all goes pear-shaped:Spoiler
As you can tell, in my experiment there's no nvidia gpu [being merely a VM], so afaict that implies the problem is V vs F35W, not V vs nvidia...?
-
@potmeklecbohdan Thank you very much. I was so cranky last night at my foolishness in naively falling for a spammer in that duplicated thread that i left the pc & forgot about completing the circle.
-
Slightly off-topic: I just spent a few hours trying to switch from Manjaro cinnamon (X11) to gnome wayland. It almost works, but only almost...
With Vivaldi the place I got stuck is the settings window (showing settings in a separate window). The browser overall seems to work, but when I try to open the settings nothing happens or the whole browser freezes.
If I run the browser in a terminal the amount of error messages printed is pretty staggering. When it freezes the GPU process evidently locks up. (I'm not posting detailed error messages 'cause no point, really.) The only concrete piece of info I have is that for best success I have to launch it with
--enable-features=UseOzonePlatform --ozone-platform=wayland --use-cmd-decoder=validating --use-gl=eglThe reason I wanted to try Wayland is that after a day of browsing Vivaldi uses over 10GB of RAM, the GPU process over 1.5GB, and the whole machine becomes essentially unusable. I was hoping that perhaps it behaves better under Wayland...
-
@vvsurfr I’m on Gnome Wayland and Vivaldi never uses this many resources. But this shouldn’t happen on X11 either. How many tabs have you got open?
Anyway, on Wayland I would advise you to run Vivaldi as standard XWayland app. Even for Chrome Wayland support is experimental and Vivaldi is a different beast altogether (the UI has little to do with Chrome). To my knowledge the Vivaldi team hasn’t looked into it so far and therefore you simply shouldn’t use the flags to run Vivaldi natively. Some people do with varying degrees of success, but I wouldn’t recommend it. There is nothing wrong with the XWayland approach and Vivaldi just works.
-
@luetage said in Fedora 35 - Problems with Wayland + NVIDIA GPU:
standard XWayland
what’s that? it’s either ‘standard’, or xwl.
anyway, i’ve had full success running v wayland-native. the only problem is that sometimes a white rect pops up somewhere, but it never stays long.
-
@potmeklecbohdan Running Vivaldi on Wayland the standard is to do it as an XWayland app. Why are we talking in circles? You shouldn’t encourage users to run experimental Chrome flags.
-
@luetage At the risk of unruly division, & acknowledging slight OT given OP asks about GNOME, fwiw my V-Snappie also runs pretty well in Plasma Wayland as a full Wayland app [ie, using Ozone et al]. That said, it still does have a few less papercuts as an Xwayland app, ie, it's pretty darn close now, but not yet fully "there", IMO.
-
@guigirl You are using KDE and idk what potmeklecbohdan is on right now, probably herbstluftwm or something. None of these environments is comparable and the flag isn’t a cure, it will just add more complications on top of what you’re already suffering from.
-
@luetage said in Fedora 35 - Problems with Wayland + NVIDIA GPU:
@vvsurfr I’m on Gnome Wayland and Vivaldi never uses this many resources. But this shouldn’t happen on X11 either. How many tabs have you got open?
@luetage said in Fedora 35 - Problems with Wayland + NVIDIA GPU:
@potmeklecbohdan Running Vivaldi on Wayland the standard is to do it as an XWayland app. Why are we talking in circles? You shouldn’t encourage users to run experimental Chrome flags.
Well, my reason for trying V under Wayland native was because it's horrible under Xorg (using Cinnamon). Thus trying XWayland seemed pointless to me.
I've had V running for ~24 hours now.
ps ax | egrep -c vivaldi-binreturns 63, so that's about how many tabs I must have open. The GPU process is 1.4GB:
That makes it "nicely sluggish". Summing the RSS column of all the vivaldi-bin processes yields ~9GB, so I'm well on track to filling up the 16GB of my box at which point I get to reboot.If running V in experimental mode under W had improved this crappy situation then that would have been great. Alas it ain't so...
-
Ppafflick moved this topic from Vivaldi for Linux on
