Yes, support for sessions in Plasma.
Disabling mouse acceleration forcibly globally
Does
ssh -X
work with Wayland (either as the sender, receiver, or both) yet?No. But there is Waypipe.
I managed to use Waypipe to open a GUI programa unde another user in the same Wayland display (actually someone else did a script for it, it’s in my profile history), so I guess it is possible to forward it with Waypipe remotely
What I don’t like about Wayland is that many things are specific to individual DEs. Like global shortcuts or taking screenshots. In my app I have two different solutions for taking screenshots in GNOME and KDE using XDG portals. It causes fragmentation.
o wow didn’t know this. such horrible design decision! So if I understood correctly ALL the apps that want to screenshot need to write independent code for each desktop environment??? I was just mostly ignoring Wayland until becoming mature, but now I actively dislike it with passion.
So, if this is true and I understand correctly, it means that if I chose to use Xfce (as I do), I’ll have to hope really hard that zoom, skype, slack, discord… decide to provide support for not only linux,… but XFCE or give up and abandon XFCE? yeah f*** Wayland, they really didn’t think about the open source community when designing their solution. I don’t wat to even think of people that use other smaller desktop managers…
I mean, screen sharing is basic functionality these days, in the interview for my current job I needed to use… I think it was teams. Is not even something you can chose, is bad enough to be exclusive linux user as it is, always wondering if in such cases something will not work.
Honestly, long live Xorg. if deprecated and I have to switch to gnome/kde or lose functionality I might as well switch to windows after 20 something years of not using it.
Screen sharing is fine, handled by Pipewire. OBS is adding (has added?) streaming through Pipewire too. And I’ve had no issues getting screenshots using grim, which isn’t tied to a specific compositor. Not everything is copacetic, but the things you’re talking about are mostly non-issues these days.
Great name, btw
Screen sharing is different thing, there is no fragmentation there.
But in order to take screenshot I had to write different code:
For KDE. It also requires special line in desktop file for security reasons.
Global shortcuts are even worse. It also DE specific and users have to manually register them in DE settings. In order for your application to support this, it should export such functions via the Dbus interface. And all this incompatible with Windows (my app is cross-platform), so I had to provide in-app interface for global shortcuts too that works for Windows and X11 users.
Oh no. Oh no. Way to shoot ourselves in the foot, Wayland.
What prevents you from using org.freedesktop.portal.Screenshot with GNOME and KDE as well? They both support taking screenshots using that method.
Unfortunately, you on GNOME and KDE you don’t have
org.freedesktop.portal.Screenshot
method in/org/freedesktop/portal/desktop
.Not trying to be a menace, but I just tried it out using xdg-portal-test-kde and the screenshot portal definitely works on KDE Plasma 5.27.10. If you are experiencing issues with that, please create a bug report for xdg-desktop-portal-kde so it can be fixed.
Strange, doesn’t work for me, I also run 5.27.10. Will take a look, thanks!
LIAR
Something wayland lacks but Xorg has?
Basic functionality. Anyone that actually thinks Wayland is ready either doesn’t use it or is just straight coping. Maybe it’ll get there, but… honestly, probably not.
Lol… Sounds like someone is on Arch with Nvidia!
Ubuntu Gnome on AMD, actually.
And you’re still having issues? Wow.
I was in the same camp one year ago. I sometimes still use it due to Synergy not working otherwise.
It’s a common occurrence in X11 that I get a full screen “Oops something broke. [Log out]”-screen, except you cannot log out because the screen doesn’t register any inputs.
So, these days: Wayland just works, and X11 (except for some specific software) causes problems. But, I aslo use AMD GPU.
So, what in particular is not ready with Wayland? I hated it two years ago. Now, I have little reason to.
screen recording/sharing, automation, it’s inherant fragmentation because it decided that basic window server functionality should be implemented on the DE, basically every driver but a super small subset of drivers for devices the devs care about which do not include nvidia drivers which are a huge portion of the userbase, the absolutely ridiculous architectural choices that intentionally blocks basic functionality, and furthermore causes a crash to completely freeze your computer which forces restart, a complete failure to understand standard monitor EDID, and a refusal to allow you to set them yourself (to this day my monitor, a bog standard 144hz 1440p LG monitor, is not supported by wayland), no global hotkeys, broken sleep mode, breaks appimages entirely, no redshift, the developers made sweeping design decisions that don’t work and then get pissy and throw temper tantrums in the mailing lists when people point out that they don’t work, heavily moving away from portability and modularity (the devs think nobody uses BSD?!), windows can’t raise themselves or keep themselves raised, or absolutely position themselves, so toolbars/utilities/etc can just go fuck themselves, sudo gets broken and has to pipe passwords everywhere as a workaround which means sudo has increased attack surface on wayland, and color management is non-existent.
And this is just shit I have personally ran into the last time I tried it, which was about 4 months ago.
Ngl, never once had an issue with any of these.
That being said I mainly use screen recording through kms capture with wlroots, which never once has had an issue for me
I don’t know about all of those. Not sure if you downvoted me, in which case you might have the predisposition of not giving a shit. In which case I’d be most happy to oblige.
As for the technical implementations / shortcomings, I… don’t really care about it. The reason I didn’t use Wayland before was because things didn’t work. The reasons why I don’t use X11 now, is because things occasionally stop working. The reason why I still sometimes use X11, is that unless I do so, some specific software doesn’t work. That’s the frame of mind I have, and I don’t have any allegiance or vested interest beyond that. You seem to have that, and that’s great. Caring about the technical details has my respect.
So as for the stuff you mention that is directly user-facing:
- Screen recording used to be a problem, haven’t had that issue recently. OBS records my screens and part of it, just fine.
- Window sharing like you could with X11 with
ssh -X
is amazing, and doesn’t work, but it’s been about 15 years since I used it. - Crashes that completely freeze my computer. Doesn’t happen in Wayland. Happens in X11 (it’s not a kernel panic, but whatever it is, I have to reboot, end result is the same to me).
- Have had no issues with any of the monitors I own.
- Global hotkeys work, and have always worked, for me. If it didn’t, I simply wouldn’t use Wayland, as a lot of my workflows surround tools I have built and trigger with global hotkeys.
- Sleep mode, I don’t use. Is that the same as Hibernation?
- I don’t use a single appimage, but I downloaded one to try now, and it worked fine.
- What is redshift?
- “Windows can’t raise themselves or keep themselves raised”, does this mean to request to be in focus? I’m curious which programs benefit from this.
- sudo is insecure by default in Wayland? How come? I’d be interested to know how it has anything to do with wayland/x11. unless you mean GUI applications executed with sudo, not having access to wayland stuff?
The reason I care about the technical implementation shortcomings is because they don’t go away. They don’t magically fix themselves over time, they snowball, especially when the maintainers refuse to admit they’re shortcomings and insist on doubling down on them.
As time goes on, new functionality and technologies are going to emerge, and you need to be able to fold those, cleanly and reliably, into your codebase. And frankly, wayland’s devs are having trouble getting past and even current technologies implemented cleanly into their codebase, because they’re made architectural decisions that exclude those technologies. This is just going to be more and more of a problem as time goes on, imo.
- Screen recording CAN work… if client devs go out of their way to work around wayland, like OBS did. That is not a long term solution, or even a solution we should be encouraging.
- yes
- personally I have crashes on wayland, none on X11. even when x11 does crash though, you just drop to terminal. Whatever is locking your system up, it might not actually be X11 itself. Wayland, you do actually have to reboot, it’s a standing architectural issue.
- nice
- I’m on ubuntu gnome w/ AMD gpu, and they straight up do not work. You can set a global hotkey for the OS/wayland itself, but there is no way to set a global hotkey for/from a program, e.g. set a key combo for ‘clip last 30 seconds’ like I can in X11. Again, conscious design decision by wayland devs that breaks a lot of use cases. I think there’s some third party plugin for wayland that fixes this, but I shouldn’t need the wayland equivalent of nexusmods to get my window manager working. This ain’t skyrim. :P
- sleep and hibernate are pretty close to the same thing- sleep mode saves your current state to RAM, hibernate stores it to disk. hibernate uses less power draw and recovers cleanly from power loss. These days I think most front-ends call ‘hibernate’ sleep, and don’t actually provide sleep as an option, because it’s imo better. I meant hibernate, and I should have clarified, because linux does actually allow you to pick and choose.
- some appimages work, but it’s because they work around wayland. These days there’s a package you can include in your app image to hep with that iirc, but again that’s kind of dumb.
- redshift is f.lux. Basically, eye strain relief.
- toolbars, utilities, etc. For example, I have a program that adds an overlay to my screen for discord, so when someone talks in discord their avatar pops up on the left side of my primary screen. This not only doesn’t work in wayland, it can never work in wayland, because it intentionally refuses to allow programs to set their own screen position, control whether they appear over other things, or even know where on the screen they are on the screen.
- GUI applications with sudo, yes. Basically, in wayland sudo has to pipe the password arround because it doesn’t support SUDO_ASKPASS, so they work around it by piping it around with a generated shell. This vastly increases the attack surface of sudo: https://github.com/linuxhw/hw-probe-pyqt5-gui/commit/eb2d6e5145fb8571414bda57676084b7f13b94e5#diff-23cb15995f1502beebb38433bfa83204a5f45b376eaf88e2e41a0d8a1cd44722R290
Thanks for the clarifications.
I do hope it improves. I never understood why Wayland became a thing, if it’s fundamentally flawed. But then, on the other hand, it’s strange to not make the improvements in X11, unless that too is fundamentally flawed.
I’ve used Wayland pretty much exclusively for about 2 years. The only problem I’ve had is discord screensharing not working, but I just use OBS’ virtual webcam for that anyway because screensharing always crashed discord for me on X11 anyway.
Heya could you share how you do this trick to screen share ? Would it work on MS Teams?
I think all you need to install is OBS studio and v4l2loopback both of which your distribution probably has packages for. Then you just make a scene, add either the “Screen Capture (PipeWire)” or “Window Capture (PipeWire)” sources to it and click the “Start Virtual Camera” button. Anything that supports a webcam will just see it as another camera on your computer you can use.
deleted by creator
I miss apps supporting global hotkeys. Screen remote support in popular apps.
Using a 3060 on Wayland, Ubuntu LTS. Some performance issues here and there, big problem I discovered is zoom screen sharing pretty much not working.
I login with my x session when I know I’ll need to present something.
Thanks, though it’s not a big enough problem that I worry about it. My couple of games still work fine in either environment.
I look forward to when all of these getting pains are mitigated by time.
I threw my nvidia card in the trash, majority of problems solved
Extreme shortage of desktop environments that support Wayland. I don’t want to use either Gnome or KDE, I’m currently using LXQt with i3wm.
Isn’t sway an decent alternative to i3?
Hyprland is pretty sweet, to be honest.
deleted by creator
If you like i3, sway is a drop in replacement for it that uses wayland. I’m not sure if you could make LXQt work with it but it’s worth a shot
Last time I checked sway did not support everything in my i3 config file. I’ve been testing wayland for the last decade or so, it never managed to deliver on its promises.
sway is a drop in replacement for it that uses wayland
IT IS NOT lmao, sway even complains that my i3 keybinds are wrong, those same keybinds work perfectly on i3.
You cannot, no desktop environment except Gnome and KDE has Wayland support beyond experimental status.
If I was content with running no desktop environment at all, I could already do that on Xorg.
I see people having a good to great experience with NVIDIA on Wayland. I lack that ability, I can never get my PC to run well on Wayland. (using the propriety drivers) hoping the new GSP firmware and the improvements to MESA-Nouveau + NVK fixes my issues. even if their are teething pains. because of how unusable it currently just is for me. course if I had the money, the easiest fix to make Linux usable for me is to buy a AMD GPU. FYI, I have a 2070Super. It is a consistently bad experience on it, with the NVIDIA propriety drivers.
Using Prime Render offloading and an AMD APU also works really well with wayland. Really happy with my Ryzen 5 5600G + Nvidia GPU setup.
I have a weird setup, which is my fault I guess, but it results in me having two keyboards with different languages. And I frequently switch between them in my workflow, so it can be super annoying to manually switch the language every time.
On X I use a combination of two tools to automatically set the language per keyboard, which works even when hotplugging.
On wayland I found no alternative so far, but if you have any ideas, please let me know.
I don’t know about other compositors, but on Hyprland and Sway you can configure things per device (in the config file). I’d give an example here but I’m on my phone right now.
I have a laptop and a desktop with slightly different keyboard layouts, and both machines share the same config file.
Not sure why you have a tool to “set the language”, what would happen if you tried to use both keyboards at once?
I honestly don’t recall the details and can’t check right now. It’s been working like that for years.
I remember the main issues I was having were around yubikey, my usb hub which can switch between two pc’s and hotplugging. So I had to use a second tool which did something on any device plugin.
I think using both keyboards at once worked fine. I didn’t mean system keyboard language.
Not a real solution, but if you were set on using Wayland you could get a qmk keyboard and change the layout in firmware
Can you screenshare with wayland?
yes
Yep, using Pipewire.
slaps forehead Of course! Silly me for not realizing the obviousness of needing to use the audio subsystem to take screenshots.
How am I being downvoted for a questions and this stands haha
Take my upvote kind stranger
For like half a second my brain thought this was a meme comparing the fictional megacorps Zorg Industries from “The Fifth Element” and the Weyland-Yutani Corporation from the “Alien” franchise.
It’s not?
My understanding is that ‘barrier’ doesn’t work in Wayland. That’s a showstopper for me, unfortunately.
Barrier is unmaintained, input-leap is maintained for of it, but with no releases yet. Not sure if it supports wayland better tho.