It among others brings support for explicit sync. If you wonder what this is and why it's important, check out https://zamundaaa.github.io/wayland/2024/04/05/explicit-sync.html . Long story short: it among others enables better wayland support in Nvidia's drivers.
I'm having a hell of a day with Firefox today (and part of yesterday). Since 126.0 was released many websites make Firefox crash (for example opening images here in Mastodon but also a Grafana dashboard and others). All in Gnome with Wayland and Ubuntu 24.04. Are other people having the same issues? #Firefox#Ubuntu#Wayland#Gnome
@adelgado I've had no problems with #Firefox 126.0 but I'm on #Fedora 40 with #GNOME & #Wayland. IIRC this can happen when you did not close all instances of Firefox $previous_version. Try closing all Firefox windows and also make sure that there are no lingering instances ($ ps ax | grep firefox). Then start Firefox again and see if that helps.
@John_Livingston
Une mise à jour récente ?!?
Il y a peut-être un sujet à propos du passage de certaines distributions Linux (#Ubuntu, #Fedora...) à #Wayland au lieu de #X11 pour le rendu graphique...
Tldr: pass the env variable XDG_SESSION_TYPE=x11 to discord command
This way it's finally possible to open the share screen without it going on a loop forever with asking for you to select a thing to share with the xwaylandvideobridge!
Is anyone following me a #wayland expert? My Chuwi MiniBook X can only do 50Hz, but users on Windows have managed to crank that up to 60 or even 90. I've tried to use this method to do set a custom resolution/refresh rate on wayland:
#wayland on #OpenBSD seems to be pretty damn solid. I ported my #sway configure over after installing a handful of apps and it just damn works. Though I can not find a wayland native terminal emulator in the repos but just getting started here. I just need to compile #waybar and hope it works than I'm all set!
J’en fais peut-être des caisses, mais ma carte graphique qui arrive à faire tourner des jeux comme Dota 2, Black Mesa ou Portal 2, mais qui est trop ancienne pour faire tourner #Wayland, ça me gave fort.
I'd actually prefer a spin built on @YaLTeR's niri compositor (https://github.com/YaLTeR/niri). It's a similarly young project, but it seems much cooler and original.
So I wanted to give Fallout 2 a go on my media center PC. I was messing around with Wine and 32-bit vs 64-bit weirdness until I discovered Fallout 2 Community Edition which simply works on Linux flawlessly. It even supports Wayland if you specify SDL_VIDEO_DRIVER=wayland. I'm amazed at how many of these community driven source ports and reimplementations exist. I should make a website about these. :drgn_flat_happy:
Today I updated to #Fedora#KDE 40 using dnf. After I log into my main user, I get a black screen (and Discord, which opens automatically). I’ve had this issue before. I’m using a Radeon card, so it’s not that Nvidia issue. And most importantly, the desktop does work with a brand new user, which means it’s something in the user configuration. In journalctl, qt.qpa.wayland: Wayland does not support QWindow:requestActivate() is a recurring error. Is this enough info? Thanks.
Nvm, that's the #X11 variable. The relevant variable here is $WAYLAND_DISPLAY, which is set by default to wayland_1. Anybody has any idea? Or can it be that nobody cares about my problems?
Upgrading broke things in some surprising ways. Most (not all) icons are gone in my Plasma panels now. It's a good excuse for me to finally play with #sway and go full #wayland though, which has been excellent 😁. I suspect it's my config that broke as opposed to some flaw in the new release (or maybe both?).
Thanks to everyone on these projects for your hard work. You're making a difference and pushing open source forward!
Oh damn, caught a nasty one. Was trying to use chromium for something but audio was not playing at all, no errors, just clicking play on things like r-a-d.io gave a "fuck you"...
Was checking if it was wayland or something like that that broke it... (And no, it doesn't open in #wayland, transparent window with the beautiful mouse dragging effect on the screen), but it was nothing related to it...
It seems that the problem was the #plasma integration extension that hijacks things and broke!!