top 96 comments

sorted by: hot top controversial new old
[–] 134 points 23 hours ago (40 children)

As a person who doesn’t really give a shit. I’ve even forgotten that I’m on Wayland. Everything I need works and that’s all that matters to me. Y’all can keep your wars to yourselves

  • source
  • hideshow 40 child comments
  • [–] 13 points 19 hours ago (8 children)

    I'm not an obstructionist but having been forced in to Wayland by plasma 6.8 it is frustrating that orcaslicer just crashes unless I tell it to run in xwayland and desk flow requires being on unstable to work with my clipboard and discord canary just shares audio from my whole desktop instead of from just my game and AGHHH I just want my things to work! So frustrating

  • source
  • parent
  • hideshow 8 child comments
  • [–] 11 points 18 hours ago (6 children)

    Both orcaslicer and discord audio sharing work properly for me on Wayland. Are you sure Wayland is the issue?

  • source
  • parent
  • hideshow 6 child comments
  • [–] 7 points 18 hours ago

    It's usually not as simple as is Wayland the issue or not in my experience. Wayland and the wm/DE and the application all have to get along and it gets along better with some than others. For a variety of reasons. I had an issue with gtk on niri where specific applications would not open up and I had to do a bunch of tweaking. It did eventually work, but it really should have just worked automatically. Wayland was getting instructions from the app that it didn't know what to do with and instead of it trying to use xwayland instead it was just failing. A lot of the problems come from the fact that X11 is OLD and because its OLD it has taken the time to work out so many random little potential issues. Wayland is new enough that sometimes it just runs into stuff that it hasn't been tweaked to work around yet. We're in the polishing phase now tho so these will start to get worked out I think. It'll just take time. X11 does need replacing as its convoluted as fuck but there's a reason some people swear by it, and that is largely for this reason. It's just got a lot of niche functionality that takes decades of dev time to fully flesh out.

  • source
  • parent
  • [–] 2 points 11 hours ago (3 children)

    The only variable I changed in testing was switching between the x11 and Wayland versions of plasma while I still could. Discord no longer prompts to provide an audio source, desktop will but the screen share won't work once I actually start it. Orca crashes the moment I hit slice unless I add an environment variable to make it use x11 compatibility mode.

  • source
  • parent
  • hideshow 3 child comments
  • [–] 0 points 8 hours ago (2 children)

    That's very strange, they both work OOTB for me on Fedora with Plasma

  • source
  • parent
  • hideshow 2 child comments
  • [–] 2 points 8 hours ago*

    They're actually talking about this in the blog post they released this week. https://discord.com/blog/discord-linux-a-year-of-upgrades Push-to-Talk etc. on Wayland

    Global keybinds on Wayland were a long-standing pain point. Wayland (rightly) doesn't let apps listen to your keyboard in the background. Instead, it provides a GlobalShortcuts API, but the implementation can be a little tricky. The spec says a shortcut looks like "z", but KDE expects "CTRL+z", so Discord figures out which desktop you're on and speaks its dialect (send the wrong one and the portal session can fall over entirely). And since every bind request can pop up an approval dialog, we only ask again when your keybinds actually change, instead of nagging you every time Discord starts. Now, features like push-to-talk work on Linux, even when Discord isn't focused. What's Next: More Control of Sound Sharing

    We’ve covered a lot of Linux improvements, but there’s more to do before we reach parity with the other desktop platforms. That means changing to the Wayland infrastructure itself. We use xdg-desktop-portal for screenshare, but that doesn’t provide a handle to capture app audio. Linux users have to choose between sharing audio for their whole desktop or sharing no audio at all. That’s not an experience we can accept long term, so we’re building per-app audio sharing on Wayland and giving it to the Linux community.

    We’ve once again teamed up with Igalia to implement per-app audio sharing in xdg-desktop-portal, letting you pick exactly which app's audio is shared. We’re even implementing it on GNOME and KDE ourselves to get it to users faster. This will take some time to reach critical mass across Linux desktops, but it’s a long-term investment to make a great Linux screenshare experience for both Discord and all screensharing apps. Stay tuned!

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

    I'm not saying audio doesn't work, I'm saying it doesn't narrow down to just the application I'm sharing, this is a known regression with the discord client to the best of my knowledge, and as far as I know the orcaslicer crash is a mesa issue affecting just Wayland for whatever reason

  • source
  • parent
  • [–] 6 points 8 hours ago (5 children)
  • [–] 1 point 6 hours ago (4 children)

    More power to you, friend. I honestly will never understand all the wars and politics in software, but it is what it is I guess.

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

    Yeah, no need to make a religion out of sofware. With the exception of our lord and savior Emacs

  • source
  • parent
  • hideshow 3 child comments
  • [–] 1 point 3 hours ago* (2 children)

    I’m going to tell you a secret and please don’t tell anyone:

    Tap for spoilerI don’t know what emacs does, and I’ve never cared to even look it up.

  • source
  • parent
  • hideshow 2 child comments
  • [–] 1 point 1 hour ago (1 child)

    It's a text editor with a lisp interpreter built in. The lisp interpreter means it can do basically anything from file management, to IRC, to email, to git. There are a bunch of addons and a virtuous interaction between good text editing and using the functionality to do other things. So if you improve say spell checking you magically get better and more ergonomic spell checking not only in your text editor but on IRC and email etc.

    Lisp is very very malleable and relatively easy to use so it has a fairly massive ecosystem compared to its relatively tiny userbase. It's design and conservation of functionality for 30 years that you could have made a tiny workflow improvement 20 years ago and still benefit from it because your little tweak remains compatible with modern day emacs with little to no effort. Emacs users often disproportionately value it because over the years their environment has years of such little improvements particular to their usage.

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

    AAAAAGHHH! MY EYES!! WHAT HAVE YOU DONE?! I had spent YEARS blissfully ignorant of what Emacs does and you just destroyed all that in a single comment! MY BRAIN IS BURNING! I DIDN’T CONSENT TO THIS KNOWLEDGE! I WAS HAPPY NOT KNOWING! 😭

  • source
  • parent
  • [–] 8 points 17 hours ago

    A lot of people just use Windows and everything they need works. And a lot of people like to customize things and use non-standard tools (quite common among Linux users, actually). It's a bit silly to say "my setup works, I don't know what people are complaining about". Well, different people have different setups.

  • source
  • parent
  • [–] 17 points 21 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 15 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 2 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
  • [–] 2 points 13 hours ago (1 child)

    I don't even know what I'm using. Whatever is default on Mint. It just works, I don't want to think about my tools, I just want them to work. And, Mint does, for me.

  • source
  • parent
  • hideshow 1 child comment
  • [–] 64 points 1 day ago (8 children)

    I know how LongtimeUser4 feels. His use case is ludicrous, sure, but xkcd's ideas don't come out of nothing.

    I am dreading trying to rewrite my scripts that currently rely on xdotool and wmctrl. When last I looked into it, the equivalents didn't cover the features I use, and the rationale from Wayland seems to be "why would you want to do that, old man?"

  • source
  • hideshow 8 child comments
  • [–] 38 points 1 day ago (2 children)

    I was the old person for the longest time but then I learned how ridiculously insecure the clipboard system in x11 is and I was suddenly like "oh would you look at the time, it's wayland o' clock already"

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

    Any program running in the x session can read every keystroke, record your whole screen, and take a copy of everything put onto the clipboard at any time. It's been mostly fine in practice in the past but more people are on linux now and it's generally a bigger target than it used to be

  • source
  • parent
  • [–] 6 points 23 hours ago* (1 child)

    What features do you use? I was able to replicate just about everything I do with ydotool. It's admittedly goofy to setup, but once you understand it, it works fine.

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

    ydotool was still in its infancy when I last looked and I haven't wanted to look again because I suspected that the situation would not have changed.

    So anyway, I've just woken up and am too dopey to care, so I went and looked. ydotool does not do what I want.

    My scripts move, resize, change the title of, and sometimes even ask a window to close (wmctrl -c).

    As best as I can tell, I have to hope that my DE provides something that will do some of what I want, or else write generic code that figures out where a window is on screen and makes exactly the right mouse movements and clicks to resize a window or close it, which is highly non-trivial. And changing a window title would appear to be impossible.

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

    Thanks to this wayland debacle, I accepted that as an X11 user I'm now retro. So I totally embraced this attitude. I don't care about how awesome Wayland will one day be. I'm happy with all my old scripts running trustworthy xdotool and wmctrl.

    Once I allowed myself this paradigm shift, I became happy. I've attained digital Ataraxia.

  • source
  • parent
  • [–] 25 points 20 hours ago (4 children)

    What is the origin of this meme? Why do they want to kill this poor man who presumably lives there and just mowed the lawn?

  • source
  • hideshow 4 child comments
  • [–] 43 points 19 hours ago (3 children)
  • [–] 35 points 14 hours ago (2 children)

    The edit looks less edited than the original.

  • source
  • parent
  • hideshow 2 child comments
  • I'm ok with this.

  • source
  • [–] 18 points 1 day ago* (last edited 1 day ago) (1 child)

    in my mind wayland is a separate thing with a lot of overlap with x11

    i still use x because it seems you cant vnc into wayland. rustdesk makes me click "share screen" on wayland. steam makes me click "share screen". if i was at that pc, i woukd just use that pc. i am remoting because im away.

    i use x because there is no wayland doesnt have an android client i can use with termux to do full linux stuff on my phone when im away from home.

    x will not be obsolete until wayland is a 1:1 replacement. there are still very valid use cases for x and it makes me sad to see everyone kicking it to the curb

    dont get me wrong, i use wayland on my pc and laptop, but x still has a place on my computers.

  • source
  • hideshow 1 child comment
  • [–] 17 points 22 hours ago (8 children)

    im newbie to linux, and im using linux mint xfce, and i dont understand the meme hehe

  • source
  • hideshow 8 child comments
  • [–] 5 points 22 hours ago (3 children)

    Me too brother, me too. The command line is scary, but powerful, only if you know the correct incantations. You look those up in the tome labeled "Google"

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

    i only use sudo apt update && sudo apt upgrade, and reboot lol, even when i turn off my laptop i use the mouse

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

    This is completely fine. No need to use the terminal if you feel more comfortable using the mouse. I would only recommend to substitute upgrade for full-upgrade in your command. This really installs all available updates even if it requires to install new dependencies.

  • source
  • parent
  • [–] 16 points 9 hours ago (4 children)

    I love and use Wayland and KDE but MAN my best remote tool still hates wayland.

  • source
  • hideshow 4 child comments
  • [–] 6 points 8 hours ago

    Yup. RustDesk for me. When prompted on the PC I tried giving access to all screens imstead of one, now it can never "'get display info". That plus issues with Chromium and CEF made me go back to X11 and alter the setup

  • source
  • parent
  • [–] -4 points 8 hours ago (2 children)

    Wayland still lacking adoption and functionality for basic and essential needs after more 15 years and with such budgets, really speaks volumes about it's architecture and decisions.

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

    VMware Player still can’t copy and paste properly between the two machines on Wayland. How on earth is that affected by the desktop compositor?

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

    One problem here lies within the architecture of wayland that it forces every DE/WM to implement their own compositing and many other things. So more and more fragmentation and harder for both WM developers and app developers.

  • source
  • parent
  • [–] 42 points 20 hours ago (9 children)

    Wayland is so smooth. When I go to my friends house and use mint I'm instantly reminded how shit x11. Screentearing on the desktop, cmon what year is this.

  • source
  • hideshow 9 child comments
  • [–] 12 points 19 hours ago (3 children)

    I thought Cinnamon finally added Wayland support now? Anyway I had the same experience. Using Mint is how I realized 90% of distro recommenders on reddit and Lemmy have 0 fucking clue what they're talking about

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

    They added experimental support and i think they made it mostly functional in the upcoming release but dont quote me on that last bit

  • source
  • parent
  • hideshow 1 child comment
  • [–] 5 points 16 hours ago (1 child)

    Wayland is so smooth

    My plasma desktop is very noticeably slower and choppier with Wayland. The most visible example is when I switch workspaces and instead of the animation taking a fraction of a second it takes a second or two. It honestly feels like my laptop (which isn't that old) was aged a decade by simply switching to Wayland.

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

    I moved from X to Wayland when Fedora dumped X, and the first weeks were a pretty unstable experience (mainly because the Nvidia drivers still had some issues after implementing explicit sync), while performance never was an issue. Nowadays all of those problems are solved. Desktop streaming works fine with both pipewire and through whatever Sunshine uses, game FPS are comparable to Windows with some variation depending on title, and my desktop experience is buttery smooth.

  • source
  • parent
  • [–] 9 points 14 hours ago (2 children)

    If you're getting screen tearing, it's not X11's fault. It's the graphics manufacturers putting speed over stability.

    I had an old Nvidia card that I never had a problem with under X11. The moment I upgraded to an AMD card, screen tearing, screen tearing everywhere.

    To fix, you generally need to slap a small config file into /etc/X11/xorg.conf.d that tells the graphics driver that slow and steady wins the race.

    The AMD solution literally contains the line Option "TearFree" "true". Ridiculous.

    Link to one of many sites providing the full solutions: https://linuxjunkies.org/guides/fix-screen-tearing-on-linux

  • source
  • parent
  • hideshow 2 child comments
  • [–] 4 points 11 hours ago

    If you’re getting screen tearing, it’s not X11’s fault. It’s the graphics manufacturers putting speed over stability.

    This is the central part of why wayland adoption has been difficult. With X11, the idea is "the buck stops here", with wayland it's "this is out of scope."

    Now, in terms of managing a cleaner project, which is wayland's goal, that's fair.

    However, in the practicalities of seamless adoption and not breaking shit, it's not being the "drop in replacement and new standard" it's hoping to be.

  • source
  • parent
  • [–] 14 points 14 hours ago* (1 child)

    Now that it at least supports my multiscreen, multi UI scale setup, it feels like Wayland is what all DE's want to be. It's so smooth and fast, and can always impose it's will on all the windows. What do you mean this window won't minimize and always stays on top?? WAYLAND SMASH. There I fixed it.

    It feels very luxurious and decadent to have a DE that is so frocking good and reliable.

  • source
  • hideshow 1 child comment
  • [–] 21 points 1 day ago (4 children)

    I still haven't cracked remote applications with Wayland and that's a deal-breaker. I use ssh -Y hundreds of times each day.

  • source
  • hideshow 4 child comments
  • [–] 6 points 23 hours ago (1 child)

    I've had some success with waypipe but it's not easy. I was able to open a chromium window on a remote machine using waypipe --no-gpu ssh user@remote 'chromium --ozone-platform=wayland'

    Both the host and remote machines were running Arch.

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

    Yeah, I've been exploring waypipe too. Most of my X11 use is inside a Docker container, so I run an ssh -Y session to a remote host that's running Docker and launch a container which starts a X11 application that runs over the session into my workstation.

    At the moment I haven't figured out how to use waypipe in that environment, since as I understand it, it expects to be installed at both ends, when I really want it across the equivalent of a bastion host, ie. A calls B which calls C, with waypipe installed on A and C, with A being a workstation and C being a container running on B.

  • source
  • parent
  • [–] 10 points 16 hours ago (6 children)

    I love the benefits of Wayland (display scaling, negative coordinates, hdr) but wish it had anything remotely as useful as xrandr (I have a 768x1024 16:9 plasma tv).

  • source
  • hideshow 6 child comments
  • [–] 6 points 14 hours ago (3 children)
  • [–] 3 points 10 hours ago* (2 children)

    I'll give it a shot, but I doubt it has a way to do seperate horizontal and vertical scaling, or rotate the screen 17.5° as a joke

  • source
  • parent
  • hideshow 2 child comments
  • load more comments
    view more: next ›