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.
🧑💻 NetBSD On The State & Future Of X.Org/X11
➥ @phoronix
「 The bad news is that to have applications running we require access to a larger open source ecosystem, and that ecosystem has a lot of churn and is easily distracted by shiny new squirrels. The process of upstreaming stuff to X.Org is an ongoing process, but it's likely we'll run into things that will never be suitable for upstream 」
Yesterday, I dusted off an old keyboard and I wanted to figure out how to set the programmable buttons. I found a Medium article with a Venn diagram of tools that worked for X11 and Wayland. If you don't know, those are display servers, which draw graphics on your screen. Well, technically display protocols, but who's counting? Here's my question: Why the EVERLOVING FUCK is my DISPLAY SERVER handling my FUCKING KEYBOARD? #linux#wayland#xorg#x11
I have been using #Wayland most of the time, on all my computers, for the past year or two. It has been a pleasant ride for the most part except my increasing need for screen recording lately. This part has been a pain because software did not catch-up, yet. I will be switching to #X11 again, to get a better feeling on what Wayland powers I might miss-out on by doing so...
Having Wayland in Ubuntu VM (22.04) and wanting to slim it down a bit, if apt remove xorg, seeing as only use Wayland (and xwayland) would it still be breaking or should it work ok?
Hopefully, this is a less embarrassing post than, "How do you log into Windows without a Microsoft account?!"
On #Debian 12 (#KDE, #XOrg), my #TuxedoComputers laptop with a German keyboard is having issues with a single character. The "^" symbol, the primary character on its upper-left key, just doesn't like to be detected. On the same physical key, the "°" is immediately input into any text box when Shift+[key] is pressed, but it takes two strikes of the same key without shift to input the "^". This behavior along with this issue not being present in other distros shows it's not a hardware issue, and all other keys are behaving properly
Has anyone else had this issue or have an idea of how to fix it? I can't find anything on StackOverflow, Reddit, or the Debian forums.
Seit Donnerstag Nachmittag verbreitet mein Ex-Arbeitgeber die Ente, dass #KDE#Plasma 6 nur im #Wayland-Modus startet[1]. Mindestens seit Freitag früh gibt es einen Forenbeitrag, der das richtig stellt[2]; ein zweiter folgte drei Stunden später[3].
Bedauerlich, das alles, denn so setzen sich Faktenfehler in den Köpfen deren fest, die diese Forenbeiträge nicht gesehen haben.
#X11#Xorg is almost 40 years old. #wayland almost 15. And I still need to read thought-pieces that argue against adopting the latter with the same gate-keeping arguments.
The amount of effort put into whining together with the lack of effort put into maintaining Xorg (or any relevant software for that matter) is astounding and agonizingly agitating.
"If you are not part of the solution, you are part of the problem. Quit being a part of the problem!" - John McClane (slightly paraphrased)
6-month update in #tilingwm; I've been using #Hyprland quite happily and have absolutely no regrets. The display scaling, touchpad gestures, and clean animations make the UX a joy to use.
The only issues I have are with software that doesn't jive with #Wayland (mainly Steam, Electron apps, and the Nvidia driver). For those use cases, I can switch to a #GNOME desktop on #xorg
I've been exclusively using #Wayland for over 6 months now. It's fine. Everything works including games and video conferencing. At this point unless there's a #Xorg window manager you really love, or you're a masochist who buys GPUs without open drivers, I'm officially calling it better.
"In 2024 [foo] will switch to #Wayland and remove #Xorg …"
Yeah, hmm ok, so how do I run that $25YearsOldApp I need?
And no, I won't go fix Xorg or Wayland, I already spent years cleaning up the X11 mess in Conky (for an hypothetical Haiku port I've yet to start) just so someone else can add Wayland support… I've done my share already.
@aral#Wayland or #Xorg? Wayland would be my prime suspect if you are using that?
I often have quirky screen resolution issues when swapping between monitors although not directly Gnome Settings crapping out, also I'm not on Fedora... Swapped back to X recently (after trying to run some old game) and things a tad more stable..
Interesting. The Nested desktop mode on the #SteamDeck has been super useful, but cannot be remoted into via #AnyDesk and the like, cos it's in #Wayland rather than #X11/#Xorg. In that case, the Deck will still require the actual Desktop mode which still does run on X11.
Watching every video promoting switching from #Xorg to #Wayland gets me moving with a plan, later only to face multiple hurdles of medium to high complexity.
I mean I've moved #distros, and switched major tools and configs, but nothing has been as intimidating as this one. Realizing how much of my setup is indirectly #Xorg-dependent, it reminds me of my move out of #SystemD in favor of #Runit.
Fast-forwarding to a week (and 73 git commits) later, I'm impressed with #Wayland and can live without #Xorg with the least gaps in my setup. In fact, I did get several extra features with the newer tools.