you are viewing a single comment's thread
view the rest of the comments
[–] 17 points 22 hours ago (20 children)

That's awesome.

50% of what I use doesn't work and I will respond to the Wayland knife with C4.

  • source
  • parent
  • hideshow 20 child comments
  • [–] 43 points 20 hours ago (18 children)

    Could you give some actual examples of the things that don't work? I hear people say this a lot, but then they basically refuse to answer what's not working. There was definitely a lot of wailing pain when it first transitioned, but these days, at least on plasma for me, I haven't found anything that doesn't work anymore. other than of course perhaps just some vague abandoned software that wants to do something crazy with the display

  • source
  • parent
  • hideshow 18 child comments
  • [–] 13 points 20 hours ago (14 children)

    Plasma does solve some problems itself but: screen recording, global hotkeys, clipboard management to name a few. They all have "solutions", it just sucks to be made to jump through hoops sometimes. There's a lot of desirable things in x11 that while crusty worked well, like xrandr and being able to script monitor config. It is niche! But if you used it, it's annoying to be forced off it

    Here is a (biased but decent enough) list https://gist.github.com/probonopd/9feb7c20257af5dd915e3a9f2d1f2277

  • source
  • parent
  • hideshow 14 child comments
  • [–] 16 points 17 hours ago* (7 children)

    What exactly about these three? I’m really curious to understand.

    I never used X knowingly: by the time I’ve started understanding Linux more or so, I’ve been on Wayland already. So, in a way, I can say I never used X, even being on Linux on and off for almost two decades.

    Say, screen recording. It just works for me on Sway (I use wf-recorder) and it just works on Gnome. I have never thought of it as being broken. I could have missed anything though. Not something I use very often.

    What global hotkeys do you mean here? Mine work in all apps. So, I assume they’re global. Or is it something different?

    Not sure about clipboard: it just works too. There’s this ‘middle mouse click’ shit that I hate, as I accidentally paste some unnecessary information into, say, email. Upon scrolling, and accidentally pressing the scroll wheel. I’d love to disable it globally, but it just there, working. I assume that’s a feature for some folks, but I passionately hate it and have no use for.

  • source
  • parent
  • hideshow 7 child comments
  • [–] 13 points 16 hours ago* (4 children)

    Not OP, but wanted to address some questions:

    EDIT: I just realized in the linked gist they're basically complaining Wayland doesn't have "builtin" support for things like keylogging, and generally uses portals for features. Yes, some DEs may choose not to implement specific features, and apparently that's Wayland's fault?

    Screen recording works, I think it's only existing X software that doesn't. In my experience there's still some jank and limitations that might or might not be related to Wayland. After a few days of runtime with periods of sleep mode, screencasting through the portal seems to break until pipewire is restarted. I don't know if there's a way to capture an application and its audio automatically.

    Global hotkeys refer to hotkeys that can be activated while the application isn't focused. Wayland has global hotkeys, but some people don't like the implementation and refuse to use it. OBS, for example, has an unofficial plugin implementing them, but the actual project refuses because they can't display and set hotkeys from their own setting menu, and have no good way to support multiple profiles with separate bindings.

    I also don't know what they mean by clipboard management, but I do know there's some jank. As a weirdly specific example, when playing Minecraft with patched glfw with native Wayland support, pasting into chat doesn't work correctly, it seems to always paste the text that was in the clipboard when the game was opened, and not update when copying things from outside the game (but I think it works when copying something inside the game itself). I don't know if this is an actual Wayland issue, or a case of a broken client implementation, but the lack of software support is still a type of issue.

  • source
  • parent
  • hideshow 4 child comments
  • [–] 5 points 16 hours ago (2 children)

    Yes, some DEs may choose not to implement specific features, and apparently that’s Wayland’s fault?

    Kind of. For a long time a mainstream setup like Gnome on Wayland lacked features because they weren't yet incorporated into Gnome. But more generally, Wayland deliberately didn't implement a bunch of features that X had, or had external things that accomplished. That pushed the responsibility for implementing it onto each and every window manager. Smaller WMs that would have had all of those features for free on X now have a big burden to achieve the same bar on Wayland, and so many don't manage it. That's due to the choices that went into Wayland.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 3 points 11 hours ago (1 child)

    AFAIK all of Wayland is pushed onto the WM, because Wayland is just a set of protocols. It has some libraries, I think official ones, to help with implementing those protocols, but ultimately that's a design choice that also means WMs don't have to have those features, especially relevant for atypical WMs where the concept of windows might not exist, displays might not be two dimensional, input might be neither a mouse nor a keyboard.

    To my understanding, if somebody wants an unusual setup, on Wayland they might need to figure out implementation of protocols for their ideas. On X11, they might not be able to do anything because it enforces certain ideas of how a graphical environment works.

    That's simply not a failure of Wayland, it's a tradeoff they chose, and it seems dishonest when people say things "don't work on Wayland" because the responsibility is deliberately moved to a portal or something.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 9 hours ago

    It is a trade-off they chose yeah, but for people on anything but KDE (really, though hyprland sway and gnome do most too) they've forced them to either catch up or die. I don't know that that's indicative of a great replacement project. For reference, I use Wayland & KDE fine, but if x11 had HDR I'd switch back to my i3 setup.

  • source
  • parent
  • [–] 2 points 16 hours ago

    Regarding the clipboard - there are practically 2 clipboards, i can paste different things based on whether i used ctrl-c/v or selecting text with the mouse and middle-clicking. I often fall into this trap, anf i would prefer it to be unified.

  • source
  • parent
  • [–] 2 points 9 hours ago (1 child)

    I recently noticed, that on Fedora Silverblue with Gnome, middle-click-paste does not work. Not sure, how and why it has beend disabled. I am glad it still works on Debian stable with an older version of Gnome.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 8 hours ago

    Thanks for letting me know! I hope there would be some middle ground for this feature at some point, with reliable ways of disabling / enabling it. Personally, I believe that it doesn’t need to be enabled by default, as average users don’t need it. And those who need it wouldn’t have any issues with enabling it once. (Assuming it’s reliable.) But I don’t mind otherwise, if I could just disable it. For some reason, I couldn’t.

  • source
  • parent
  • [–] 5 points 13 hours ago (5 children)

    I guess those 3 are solved by KDE then. I only know Wayland through KDE and the 3 work perfectly fine for me, I didn't even have to think about them when I used them.

  • source
  • parent
  • hideshow 5 child comments
  • [–] 3 points 9 hours ago (4 children)

    Try copying to your clipboard in vim without a plugin, or try starting to record without a (very shaky) OBS plugin. I'm not saying Wayland broke into my house and burgled me but their decision to create everything as distant APIs means that all the smaller DE/WMs have to implement it in a certain way. KDE does a great job of this, but I now have to choose between using HDR on KDE and having things that used to work fineon something like i3

  • source
  • parent
  • hideshow 4 child comments
  • [–] 2 points 8 hours ago (1 child)

    I feel like it's all made more frustrating to me too because it seems so many of the problems are in service of answering a threat vector I just don't give a shit about.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 2 points 2 hours ago

    Yeah.. it almost makes me wish for an "unsafe mode" where Wayland allows all the things it didn't allow for the sake of security, but given there was a way to run x11 rootless and many people didn't, I'm guessing that would just make everyone use it in that way However, the security stuff feels so hypothetical to me right now. I'm on Wayland purely because it supports HDR, I can't easily cite a single other benefit for myself

  • source
  • parent
  • [–] 1 point 3 hours ago (1 child)

    I can record my wayland session in OBS without any plugins. here it was working fine even in plasma 5

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 3 hours ago

    Sorry, I meant trigger it with a hot key. Thanks to pipewire, the actual screen recording is in a pretty good place now, providing the permission stuff is implemented correctly But because OBS hasn't registered its capacity for hotkeys via Wayland, they don't work globally. I'm sure it's not a crazy addition to the codebase, it just feels like a step back to me

  • source
  • parent
  • [–] 2 points 9 hours ago (1 child)

    Running on older nVidia cards causes visual glitches and memory leaks to the point where not even short remote sessions are usable. I have a Quadro K420 in my home server.

    Replaced KDE with xfce and everything works perfectly again. Too bad they are forcing Wayland now.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 1 point 2 hours ago*

    That sounds like an NVIDIA issue though, not a Wayland one. NVIDIA has never really given a flying shit about how the drivers run for non-corporate customers.

    Also, no one is forcing Wayland, they are just choosing to not maintain X11.

  • source
  • parent
  • [–] 1 point 5 hours ago*

    an issue with Wayland that i have is when i launch a game (Minecraft) from steam, it loses the process and steam doesn't recognize the game as running. because it's not recognized, my steam input settings aren't applied to my controller and I'm stuck in desktop mode.

    the exact same setup worked in older Minecraft versions on Wayland.

  • source
  • parent
  • [–] 1 point 14 hours ago

    I mean, let’s be honest. Most of people online came running with their pitchforks whenever someone said anything good about xorg or forked it. So, I guess most of them got what they deserved. Not you, of course 😂

  • source
  • parent