A question for #Linux#Wayland users. I am running Debian stable with Plasma and my computer was freezing randomly, and very often. Let's say once per day. I was about to start replacing hardware components to find the guilty party, but then I switched from Wayland to X11 and it has been a couple of weeks with not a single freeze. Is it possible that Wayland is this unstable or am I doing something wrong? My GPU is Radeon 6000 if this matters.
I've been trying to make this work for a few days and finally I achieved it, the most basic form of a wayland client using unix sockets, and well in other languages it was not difficult at all, I did it in hare, c, typescript (deno), and in the end I wanted to try with a language that I had never used, Haskell, and I learned many things but I still don't know what a monod is, anyway, here I leave a link to the code for those who are interested: https://gitlab.com/-/snippets/3711372 #haskell#programming#wayland
For the past 10+ years, I was unable to daily-drive the #Wayland version of #GNOME …
…until version 45.2+, where performance improvements landed for my specific usecases.
Since then, for the past 6 months, I've been running 45.x on Wayland.
This week, when I went back to the Xorg/X11 version for 1-2 days, I was surprised to see it now feels unbearable to me from a performance standpoint! Even with animations disabled.
I guess I can't go back after having used a no-delays no-jank version 🤷
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
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.
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.
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!!
A customer of mine is looking for a #Wayland expert to contract, related to frame capture as part of a streaming stack. Let me know if you or someone you know would be a good fit!