8 ms·
Wayland is pretty good
- saint_yossarian 3y agoLast time I tried Wayland I still had these issues: - Windows can't position themselves, this is seriously annoying for apps with lots of utility windows. - Apps can't change the display refresh rate, which means I can't watch movies on my TV without stutter. - GNOME sometimes crashes for me on Wayland, taking the whole session with it. I also can't restart Mutter to reload extensions, which makes developing them (to work around Wayland shortcomings, ironically) a pain in the butt.
- kiririn 3y agoDoes it have hardware cursor support yet? My last experience was unusable for mouse-centric use, like treacle compared to Windows or X11. Windows has proven you can have all these nice things in a low latency environment
- lulitao1997 3y agoKDE, wlroots's hardware cursor are broken right now https://bugs.kde.org/show_bug.cgi?id=452117 https://bugs.kde.org/show_bug.cgi?id=452117 https://github.com/swaywm/sway/issues/4763 https://github.com/swaywm/sway/issues/4763 sad to see another linux api design failure
- colordrops 3y agoYou must have something wrong with your setup. I'm not seeing any issues with the cursor on my two older laptops.
- kiririn 3y agoYou probably won’t notice it on a laptop display, especially not if using the touchpad
- colordrops 3y agoI've got 2 4k screens attached to my laptop.
- kaba0 3y agoThere is nothing to notice as it is FUD.
- worthless-trash 3y agoYou've just started me down a rabbit hole of reading, I'm so confused now that there is even the idea of a 'hardware cursor' of an idea so clearly implemented in software.
- kiririn 3y agoThe cursor has to be rendered outside the normal graphics pipeline to feel responsive. To match it you would need to render the desktop at 2x or so the mouse polling rate (like 2000 fps or so for a good mouse)
- whizzter 3y ago1: Mouse polling rate needs to be higher than rendering rate and and NOT the other way around. The higher the better because it guarantees that there is less of a delay between the latest sample from the mouse and the time the mouse cursor is rendered. (There are plenty of articles about how to minimize latency for fighting games by going from triple to double buffering and sampling just at the start of the "double" rendering phase) 2: Hardware cursors of old were akin to sprite hardware on consoles, here the hardware did compositing (or pre-compositing) operations on a per-line basis just before sending the frame contents to the display. On platforms like the C64 you only had 8 sprites in hardware but if you tuned your code to race the display processor you could have more by updating the sprite positions to lines below (so still limited to 8 per line but non-overlapped it was possible to have more). 3: Looking at WDDM there seems to be 2 ways cursors could be handled, either Windows uses overlays under the hood for the cursor (if overlays support operations like alpha-blending automatically) or the compositor pre-empts the GPU when it's time for an display update, modern GPU's are fast enough that compositing operations should be able to finish quickly enough to meet frame-times but if done off-screen for safety it could be producing an extra frame of latency. Regardless the GPUs should be fast enough today to make it happen whenever needed even if not using the classic ways.
- kiririn 3y agoRight but say the mouse is a constant 1000hz. To get the most recent sample on the screen as quickly as possible you either need the entire rendering pipeline to run ridiculously fast (the 2000 fps example), render just in time before vsync with impossible accuracy, or bypass as many clocks and buffers as possible and blit the cursor with hardware magic. There’s a reason it’s still done this way after so many years of advancement
- hackernudes 3y agoEach implementation of Wayland is its own beast (called a "compositor"). Sure there is a libwayland they all share, but all the implementation details are up to the compositor. The idea of a cursor being hardware or software is not a fundamental part of Wayland as far as I can tell. Hardware cursors are supported in wlroots.
- Jasper_ 3y agoAll Wayland compositors I am aware of use KMS planes to push a hardware cursor plane. It should work fine.
- kaba0 3y agoLiterally every major compositor had it since forever.
- blinkingled 3y agoX11 is mostly stable though. With Wayland on Fedora/GNOME or KDE a crash or two once in a while is still pretty much something you expect. Hopefully it gets better in less than 20 years :)
- colordrops 3y agoWayland can't crash, it's a protocol. That's like saying "http" crashed. Chrome or Firefox can crash, but not http. Gnome and KDE are Wayland implementations. I'm using SwayWM which uses wlroots as its Wayland implementation and it's solid as a rock.
- augusto-moura 3y agoYou either understood the point and purposely ignored it or just missed it completely. The parent reply clearly means support for wayland, not the protocol. Being pendantic about the definition doesn't help the discussion at all. It is the type of response you would get on the red website
- anyfoo 3y agoI agree, but I'm curious what the "red website" is? I thought maybe reddit or lobste.rs, but they seem more blue to me. Unless because their logos/favicons are red? Seriously not trying to be annoying, generally curious.
- augusto-moura 3y agoI don't know if you mean blue as in politics, but I mean the literal color red. And well, red is on its name :p The orange website and the red website are popular slang that you hear around here from time to time
- anyfoo 3y agoI meant the literal color, too! I guess the new website does have some reddish elements. The old one was entirely blue [1], and I'm pretty sure "reddit" is just a play on "read it". Ah, full circle, back to being uselessly pedantic. :) But I was really curious, didn't know "red website" was slang for it (well familiar with "orange website"). [1] https://old.reddit.com https://old.reddit.com
- aidenn0 3y agoAnd once I upgrade from my 1050Ti, I might be able to use Wayland without it crashing...
- tomalaci 3y agoProblem is always with software having good support for these "newer" protocols. Most just seem to test and develop against X11. In general, it would be great to have more first-class support for Linux from many major software developers (in my opinion, Valve is a pretty good leader in this area). Linux always feels like second class citizen that you need go in manually tweak and fix something to make it work (thankfully, there is plenty of info to do it but it is still a hassle).
- spdy 3y agoJust went through a sway install and its on the right path but still needs alot of work. Alot of digging is needed to get nvidia accelerating / mouse cursor to work and performance is not comparable to X11 atm from my experience.
- OtomotO 3y agoThis is on nvidia or as I say "nie wieder" for "never again" I haven't bought an nvidia powered device since 2007 and am using amd exclusively since 2011. No regrets. Open source drivers rock!
- pawelduda 3y agoI used sway for a bit back in 2019 on a dated laptop with Nvidia card, I was actually impressed how performant it was compared to Gnome. I remember tiling browser windows + complex apps, some terminals and DotA2 while waiting for matchmaking so IMO I was throwing a lot at it, but things kept working and running smoothly, it would react instantly to any tiling hotkeys, fullscreen toggle, no matter how much I was messing with it. On Windows programs would become unresponsive after 1/10 of such treatment. There was one dealbreaker though; random rare crashes which would reset my workspace that I couldn't narrow down to anything. This + not being in the mood to write my own DE from scratch (configs) made me ditch it. But it is tempting to go back to it once in a while given how much time had passed - if it was available for Mac, I would very very likely reconsider, otherwise it just adds more fragmentation between Mac/Linux. And btw DotA2 had more FPS than on Windows :)
- kaba0 3y agoSway supports anything the kernel supports. The kernel supports any video card that implements their APIs. Nvidia doesn’t do the latter, so blame them.
- ary 3y agoRelated: https://news.ycombinator.com/item?id=35935979 https://news.ycombinator.com/item?id=35935979 https://social.treehouse.systems/@marcan/110354541574112092 https://social.treehouse.systems/@marcan/110354541574112092
- colonwqbang 3y agoThings that I can't get to work on Wayland: * Getting the display scale just right. I have a 3k by 2k laptop screen. 1x is too small and 2x is too big. * Getting the mouse cursor to be drawn at a consistent size. Now the size varies when you move it across windows which is unacceptable. Am I missing something? Both of these seem like basic issues that someone must have figured out a solution to.
- Schnouki 3y agoI use 1.5x on my Framework 13 laptop (2256x1504) and it works perfectly :) Way better than Xorg, especially when using multiple displays with different scales or fractional scales. For the mouse cursor, I had the same issue with Xwayland windows until I explicitly setup a cursor theme. Now that works too... and I suspect it was also because of that display scale thing.
- andrewmackrodt 3y agoAre you using any electron based apps? I find them to be much blurrier when using fractional scaling versus Xorg so I'm running my monitors at native rather than my preferred scale of 125% (2K 16" and 4K 27" displays). IIRC, vs code supported some extra arguments (--enable-features=UseOzonePlatform,WaylandWindowDecorations --ozone-platform=wayland) but this didn't work universally across electron applications and caused very noticeable input lag in others such as Discord.
- TheCycoONE 3y agoYes xwayland just renders the application in the original size and scales it leading to a very blurry experience. Using only native apps avoids it so I find it a little hard to knock wayland instead of say electron or X. This is the issue: https://gitlab.freedesktop.org/xorg/xserver/-/issues/1318 https://gitlab.freedesktop.org/xorg/xserver/-/issues/1318
- galkk 3y agoWayland is supposed to have fractional scaling now. I think wdisplays lets you configure it. #1 was was never solved by X11 properly, and I'm forced either have large fonts on 27" 2K and ok fonts on 4K 32" or ok fonts on 27" and small on 32", because I'm limited by one Xft.dpi
- timetraveller26 3y agoI keep hearing that, but personally I will migrate until something like Awesome WM is available on Wayland.
- OtomotO 3y agoOn wayland since 2018, exclusively since early 2020. Only problem left is: no browser docks in obs due to cef upstream.
- jakedata 3y agoYes, Wayland is pretty good. https://www.niche.com/places-to-live/wayland-middlesex-ma/rankings/ https://www.niche.com/places-to-live/wayland-middlesex-ma/ra... Unfortunately the whole Linux display thing has rather confounded searches about the town. Any open source contributors who live here are probably mildly annoyed. Why don't then name projects the way Amazon sellers name products, with a semi-random agglomeration of letters instead of taking a perfectly sensible name that is already in use. Would you call your display driver brooklyn?
- arcanemachiner 3y agoI propose a committee that allocates sets of random letters on a first-come-first-serve basis. That way, we will not suffer the undue burden of having multiple names for things. The name of this committee shall be 'mvphjguq'. Not only is the name unlikely to collide with any existing place names, it is nigh unpronounceable! And because it is only 8 letters long, it is easy to remember, while also having a 1 in 26^8 chance of having a collision with another randomly generated value (although we can check for collisions before dispensing new names).
- jakedata 3y agoAre you serious or doubling down on my -3 so far sarcasm? Hacker News hates sarcasm.
- arcanemachiner 3y agoNot serious, but you definitely out-sarcasm'ed me.
- fifteen1506 3y agoWe used to have cool names like gaim or something. Then stupid trademarks started going after names whose substrings matched the trademark and no-one wanting to avoid a heartattack chose again original names.
- zzdzz 3y ago
- mikepavone 3y agoThe core of Wayland does seem to be pretty good, but I think adoption has been hurt by a tendency to push things out of the core protocol and the lack of a unified implementation between major desktop environments. Screenshots and screen capture got pushed out to dbus protocols and are quite limited in some ways compared to what you could do with X (good for sandboxing, but I think rather unfortunate for the non-sandboxed case). Window decorations are a huge mess because GNOME/Mutter don't support server side decorations at all, but non-GTK apps don't necessarily know how to draw their own. Even VRR support is kind of a mess because it's up to the individual compositors to implement it and one of the most commonly used ones (Mutter, used in GNOME) doesn't support it.
- nsajko 3y agoOne of the big issues with Wayland is the (intentional) fragmentation. Each "Wayland compositor" is really its own window system, with its own peculiarities. This forces applications that would have been trivial to implement on X to either limit support to only a single "compositor", or suffer explosion of compositor-interfacing code. Apart from that, Wayland is very opinionated, it's basically intended to cater to 70% of users, while flipping off the rest.
- kartoshechka 3y agothe dumbest decision was to push keyboard layout handling to compositor, and if you happen to be multilingual, you're locked into mainstream DEs. while all the cool stuff like newm, cardboard, hikari is destined to avoid any meaningful adoption unless authors reinvent a monstrous wheel that is keyboard layouts
- mkozlows 3y agoI've been using Wayland (on Fedora) for a while, and it's been fine. No crashes, no weird performance problems. I wouldn't even know it's not X... ... EXCEPT THAT it doesn't support color management (or at least, Chrome doesn't support it under Wayland, I'm never clear where exactly the problem lies), so my wide color gamut monitor goes fluorescent in Wayland, while staying properly subdued in X. There, I've now fulfilled the contractual obligation to gripe about Wayland in every post about it.
- orbital-decay 3y agoEvery time I want to try it I see complaints about color management, and it raises all red flags I have with me. Is it really true? How can something so basic and vital be neglected?
- nsajko 3y agoYeah, it's crazy how Wayland is being pushed as a replacement for X.
- andrewaylett 3y agoThe people who wrote and worked on X for many years decided to write and work on Wayland instead. No-one's forcing you to switch, but conversely no-one's forcing the folk who used to work on X development to keep doing that. I did see one of the long-standing developers wondering whether it would have been better-received if they'd called it X12 :P.
- djbusby 3y agoWell, X is definitely showing its age and some week-spots. I think we need something. And given how huge X is - in both features and users - it's gonna be really hard. And, it seems only Wayland is making any progress - even if slow. The other options are slower or non-existent.
- nsajko 3y ago
- sylware 3y agoThe second the steam client drops its 32bit legacy code and finally has a wayland backend, I start to code my wayland compositor (probably based on the drm/vulkan one from valve deck). That said, be careful, one of the big mistakes from x11 was those bazillions of libs with their quite not stable ABI/API to deal with, the wlroots lib from this article _must_ stay private/static for a wayland program!
- sylware 3y agovalve deck is c++, mine may be plain and simple C (c99), or maybe full x86_64 assembly.
- Animats 3y agoIf only Wayland worked on NVidia GPUs.[1][2][3] [1] https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929 https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/1968929 [2] https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020249 https://bugs.launchpad.net/ubuntu/+source/gdm3/+bug/2020249 [3] https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-wayland https://bugs.launchpad.net/ubuntu/+bugs?field.tag=nvidia-way...
- moelf 3y agouse newer Nvidia driver helps https://wiki.archlinux.org/title/Wayland https://wiki.archlinux.org/title/Wayland
- Animats 3y agoI just "upgraded" from NVidia driver 525 to 530. Now I have programs that use Vulkan crashing with segmentation faults. Legacy OpenGL still works. Filed two bug reports. Back to Xorg.
- Animats 3y agoTurns out that Ubuntu 22.04.2 LTS has a library out of sync.[1] No Wayland use of Vulkan on LTS until mid-2024. Apparently fixed in Ubuntu 22.10. Back to Xorg for now. [1] https://github.com/NVIDIA/egl-wayland/issues/80 https://github.com/NVIDIA/egl-wayland/issues/80
- neurostimulant 3y agoThe recently released nvidia 535 supposed to fix many wayland issues. Probably need to wait until it trickles down to your distro. https://www.phoronix.com/news/NVIDIA-535.54.03-Linux-Driver https://www.phoronix.com/news/NVIDIA-535.54.03-Linux-Driver
- Animats 3y agoSearch with Google for "NVidia 525 driver not installing Ubuntu" for the sorry tale of NVidia 525 vs. Ubuntu and Mint. There's a dependency problem and the install fails. There is much discussion of workarounds. If you try this using the "additional drivers" GUI program, you get a dialog box with a big X and an "OK" button, but no message. If you want to run Wayland on NVidia hardware, you need to be heavily into Linux system administration.
- stephendause 3y ago> Primarily, what I’ve learned is that Wayland is actually really well-designed. The writing is on the wall for X, and Wayland really is the future. Hmm. The first sentence does not imply the second is true. I wonder what it would take to see widespread adoption of a new windowing system. Quite a lot, I would imagine.
- nsajko 3y agoTo add insult to injury, the first sentence is false.
- Jasper_ 3y agoI certainly have some complaints with Wayland's design, but I'm curious what you would remark as dealbreakers here. As someone intimately familiar with both X11 and Wayland (and used to maintain stacks for both), Wayland is a real improvement along many axes.
- a1369209993 3y ago> but I'm curious what you would remark as dealbreakers here. I'm not sure how to properly and (edit: semi-)concisely explain the problem except by example: How do I translate[0]: $ ssh -Y raspberry-pi-on-null-model-cable ~/bin/my-x11-c-program to Wayland, when executed from a non-ARM machine running a X server (respectively Wayland server) with a unknown compositor[2], without `my-wayland-c-program` loading any compositor-specific code or resources (and preferably being statically linked[1], although statically linking xlib is admittedly also a pain in the ass[3]). Things that are the responsibilty of the window manager, such as the title bar, close window button, and alt-space menu, need to work correctly on any compositor that supports them, without the application running any code related to those things. If it was just having to run everything on the same machine, wayland would have to have conspicuously significant advantages (of which it has roughly none) to be worth the loss in functionality. Adding on per-compositor special-casing - especially when the suggested 'fix' is apparently for me to link per-compositor shitware into my applications to allegedly abstract away that special casing - means Wayland needs to die in a fire. 0: Regarding ssh -Y: yes, the lack of security-distrust between two pieces of hardware right in front of me, that I nominally trust and control, is intentional. 1: ie `file my-wayland-c-program` prints (emphasis added): ELF 32-bit LSB executable, ARM, version 1 (SYSV), [*]statically linked, stripped[*] 2: "unknown" as in the application doesn't know, and isn't going to find out, because it doesn't matter unless the application is `wl-print-compositor-name` or similar.
- noAnswer 3y agoWe do support for a commercial Linux desktop program that gets primarily run on Windows clients. We use VcXsrv (a X-Server for Windows) for that. I'm wondering, is it/will it be possible to forward a Wayland program like you can a X11 program? Or will we have to go back to NX/X2Go/VNC/RDP solutions and login to a whole desktop environment?
- johnny22 3y agowaypipe maybe?
- noAnswer 3y agoThanks for the tip. So maybe in combination with WSLg it is possible. Not as easy as a X-Server for Windows but still.
- zerocrates 3y agoThis is running in WSL? Microsoft has some wayland stuff already for WSL, though I think internally there's RDP involved: https://github.com/microsoft/wslg https://github.com/microsoft/wslg
- noAnswer 3y agoIt's not running in WSL. It runs on a central server and the clients use plink(putty/ssh) X(VcXsrv) forwarding.
- zerocrates 3y agoAh. Yeah then I guess you're in the land of either waypipe or RDP/VNC/etc.
- akvadrako 3y agoParsec is way better than VNC/NX/X11/etc. You aren't going to get better than streaming compressed video with any modern toolkit, since the rendering happens in the app and it's just about moving pixels going over the network.
- notactiuser2 3y agoExcept for the fact that every program isn't built for it.
- snailmailman 3y agoLast time I tried wayland, only a month or two ago, i ran into multiple bugs that led me to switch back to xserver. Discord screen share did not work at all. I guess the official app doesn’t support wayland. The workarounds are “use a web browser instead” or “risk a ban with an alternate discord client”. Which led me to problem 2: screen share did not work in Firefox either. Tried a whole bunch of workarounds but couldn’t get it to work. Either wouldn’t see a display, or Firefox would crash. Nothing worked. I think I recently saw something in the Firefox patch notes about wayland screenshare, so maybe I’ll give it another go in another few months.
- eqvinox 3y agoI had the same problem with screen share not working in Firefox. It simply gave an empty list of things to pick from to share. After, idk, half a year or so, I gave it a fifth(?) try, it still didn't work, and I googled the problem once more. Lo' and behold: you have to install xdg-desktop-portal to get screen share functionality. I installed it, and it worked. Now there's 2 problems with this: 1. the UX is F'ing punching out the bottom of the barrel. There is no hint, no error message, no breadcrumb to tell you what's going on. You just get an empty list of sharing choices and are left completely befuddled. Cool. 2. xdg-desktop-portal, first hit when you look it up, starts its description with "A portal frontend service for Flatpak and possibly other desktop containment frameworks." What the F does that have to do with screen sharing? (Apparent answer: …sandboxing/access control?) If you dig more, you do get told that it does screen sharing, but with a first hit noodling on about "Flatpak" … "desktop containment" why would you even be inclined to dig deeper? The irony of an UI project being this oblivious about dealing with users is… well.
- nurettin 3y agoxdg-desktop-* just goes 100% cpu. It's the first process I kill after booting Fedora. I'd appreciate if xorg folks implemented whatever hippie nonsense millennials want so that we can go back to 20 years ago when everything worked fine.
- 3y ago
- deleted 3y ago[deleted]
- deleted 3y ago[deleted]
- i-use-nixos-btw 3y agoWayland as a concept is pretty good. But I would strongly urge anyone from switching to it unless you have nostalgia about the bug-ridden nature of the 2010-era Linux Desktop. I’m still using it, by the way, with Hyprland, but I think I’ll be switching back to X11/i3 soon. Here’s a taste of my experience thus far. Electron apps are a mess. This isn’t (all) wayland’s fault but for issue lists like https://github.com/electron/electron/issues?q=is%3Aissue+is%3Aopen+wayland https://github.com/electron/electron/issues?q=is%3Aissue+is%... to exist, proponents of wayland would find it in their best interest to tackle the problems given the large number of applications that use electron. Screen sharing doesn’t work. All the old fixes are to be ignored - it has regressed. Again. Font sizes are screwy. VSCode simply doesn’t work. The handy slack shortcuts like ctrl+shift+space for mute that work anywhere only work when slack is focused on Wayland. If you have multiple monitors of different scaling factors, moving a window from one to the other results in it becoming unbearably blurry. wl-clipboard and vim with clipboard=unnamedplus (the only reasonable clipboard) simply don’t work well together, and have a history of bugs going back for FOUR YEARS. At the moment, holding down x or d for repeated deletes is INSANELY slow. As in, I’m used to it working at my repeat rate of ~60 deletes per second and it barely does 3. Every now and then, my cursor becomes huge. Every now and then, it becomes tiny. No idea why, and I’m afraid to ask. Basically, it’s not a comfortable experience.
- kaba0 3y ago> bug-ridden nature of the 2010-era Linux Desktop So where is the non-bug-ridden version from any year? I would like to try. While you are at it, I would also be interested in any GUI, other OS DE, whatever that is bug-free because I have yet to see one.
- i-use-nixos-btw 3y agoThere’s a subtlety here. Something can still have a few bugs without being bug ridden. It’s the difference between a puddle and a flood. X11 with i3, the setup I’ve used for years, is not bug ridden. There are quirks, but nothing fundamental, nothing that makes it a bad user experience. Wayland, on the other hand, has been a dreadful experience. Some of the most fundamental things, like cursor rendering, window rendering, multiple monitors, clipboard, all have problems doing the basics. To be clear, this is what I actually expected. My disappointment is that people have been preaching about Wayland for years, pushing a stronger and stronger line that it is fantastic, has great support, and is ready to switch to now. That just isn’t the case.
- hackeraccount 3y agoI use it but screen sharing is still a bear. I can't get it to work with Slack at all - (this is on the flatpak release of Slack 4.32.127) It's good enough though that I'm just kind of working around it - always hoping that some update to Sway or Flatpak or some tweak with Flatseal will fix the issue. Hasn't yet though.