This isn’t really driver related. It is the Wayland compositor’s job to properly handle multiple GPUs, which is lacking in some (a very popular, Wayland library that lacks proper multi-GPU support is wlroots) compositors. Vulkan drivers and DRM are already enough to properly handle multiple GPUs. I guess Wayland implementers just haven’t cared enough about the issue, or maybe are figuring out a “perfect” way to address it (a la 3 year long pull request on wayland-protocols repo incoming)
Not saying this is the right thing to do. But it does seem like social media consistently suppresses the spread of “hacked” (whatever their definition of hacked might be) material related to political candidates, regardless of party. The same thing happened with the Hunter Biden laptop stuff, which was pretty much impossible to spread on social media. Although Elon Musk is obviously all in on trying to help Donald Trump win, the decision to suppress this information is not surprising. Meta is also suppressing the links.
Me when I move from cheap spyware to premium spyware.
Doubt it’s a sway problem. You got it to work with waybar in plasma, or just in a terminal? Anyways, my setup is also sway+waybar so I’ll try to use cava later today.
They’re so done with NVIDIA they don’t even have the energy to attack them on a forum anymore
Try increasing the height of the bar to some insane value. Just to make sure it’s not cava being unable to scale down.
The Element X is supposed to be the best client, but I can’t find a way to join rooms within a chat. So for now I use Fluffy to join rooms, then back to Element X for actual usage. Kind of bothersome but I’m sure they’ll figure it out since the original Element app has the ability to join rooms.
I didn't know you could run kodi straight from the tty, sounds cool. And yes, kodi has Wayland support.
Roku’s patent
Running kodi on a cage session sounds like a nice idea. Cage’s whole purpose is to run 1 app maximized.
Wine (which Proton is based on) has had support for Wayland since version 9.0 (about half a year old). Admittedly it’s not even enabled by default, but it works and I’ve played Path Of Exile through wine’s Wayland backend. There’s talks to ship the Wayland driver along X11, but not enabled by default yet, since there’s still some issues before they consider it on par with X11 backend. Proton might take longer, since I don’t think Valve will enable that before they add Wayland support for the Steam client.
Just install wireplumber, plus the pipewire modules for alsa and pulseaudio (pipewire-alsa and pipewire-pulse, respectively). These 3 will run any audio application.
Yes. Wayland protocols take too long to get merged. Actually, a few days ago some people (mostly Valve guys) got tired of it and took action by proposing changes[1, 2, 3, 4]to the way new protocols are handled. Hopefully it gets better. Also, if your compositor is based on wlroots, then you might get support for the new protocol very soon.
The screen capture protocol was merged a month ago. Support will come soon. wayvnc, grim (and by extension grimshot) already have support for it. No compositors have implemented it afaik, but wlroots is very close to it.
That is NVIDIA’s fault. They wanted everyone to use the inferior EGLStreams while knowing GBM is better. Everyone ignored them and moved on, so NVIDIA sucks on Wayland. They did change their mind recently so maybe you’ll get support at some point in the future. Unfortunately there’s nothing to do from the Wayland side to fix this, except for adopting EGLStreams which nobody will do.
There’s no protocol yet that allows apps to observe inputs. They just started working on it so it may be a while.
Steam is not Wayland compatible. The games you are playing are most likely not Wayland compatible. This is not a Wayland issue.