With X, any program can capture the entire screen. The Wayland protocol does not allow this, so each DE must implement it separately. You’re using KDE’s screenshot feature, not Wayland’s, and other screenshot tools may not work if they don’t support KDE’s custom protocol for screen capture.
Does it suck? KDE also has screenshotting implemented. It makes sense that your window manager should manage your windows, which includes being in charge of what can see what. Letting any app screenshot your entire monitor is not secure.
Only those that must interact with non-standard Wayland protocols, such as screen capture tools (like OBS), clipboard managers, WM utilities like xdotool… Other programs such as email clients or text editors are unaffected.
However, this is a non-issue as far as most users are concerned. There are only a handful of implementations (basically, GNOME, KDE, and wlroots which is used by most Wayland WMs) and most modern programs which require specific support to work are all compatible.
I will be forced to, but x11 is no longer being developed, so its not very secure to do so
additionally, Wayland is going to be default on kde, and Im not sure if that means that it’ll be default for me too if I update
not to mention that with it default on KDE, I’ll be running into more and more bugs that just, will not be fixed, because “use Wayland” will be the new response to bug reports (GNOME actively does this with a critical GTK4/libadwaita bug)
the point is, Wayland is being rushed and was never ready for default
additionally, Wayland is going to be default on kde, and Im not sure if that means that it’ll be default for me too if I update
So when it’s the default, you just pick X11 from the drop-down, like I do for Wayland today.
not to mention that with it default on KDE, I’ll be running into more and more bugs that just, will not be fixed, because “use Wayland” will be the new response
Speculation. Gnome devs are notoriously stubborn, I don’t see that being true for KDE.
the point is, Wayland is being rushed and was never ready for default
15 years is not a rush, and for most people it’s ready. Making it the default will serve as a push to get developers to make their applications support it.
Most applications get their Wayland support from the toolkit they are written in. Qt ( KDE ) and GTK ( GNOME ) apps are going to work in any Wayland compositor.
Some applications do “desktop” related things like try to take screenshots to set global hot keys. Wayland, strictly speaking, does not allow this. This becomes the job of the “compositor” ( Window Manager ) and so, if an application wants to do those things, it has to know how to talk to the compositor.
Increasingly, the desktop environments and compositors are aligning on how to surface some of these capabilities to applications in a common way.
With X, any program can capture the entire screen. The Wayland protocol does not allow this, so each DE must implement it separately. You’re using KDE’s screenshot feature, not Wayland’s, and other screenshot tools may not work if they don’t support KDE’s custom protocol for screen capture.
wait so you’re telling me I’m gonna be forced to use spectacle on wayland if I use KDE?
You will have to use a KDE compatible screenshot tool.
sighh, that sucks
does this go for pretty much all programs, like say an email client too? or is there a limit to this?
Does it suck? KDE also has screenshotting implemented. It makes sense that your window manager should manage your windows, which includes being in charge of what can see what. Letting any app screenshot your entire monitor is not secure.
Only those that must interact with non-standard Wayland protocols, such as screen capture tools (like OBS), clipboard managers, WM utilities like xdotool… Other programs such as email clients or text editors are unaffected.
However, this is a non-issue as far as most users are concerned. There are only a handful of implementations (basically, GNOME, KDE, and wlroots which is used by most Wayland WMs) and most modern programs which require specific support to work are all compatible.
still frustrating as all hell, these programs just worked on x11
also Synergy/Barrier/etc dont work yet and would need “non standard” protocols. Pretty critical for me
I am an enduser and I just expect things to work, but one of the most critical things of my setup wont
You do realize you’re allowed to still use X11, right?
I will be forced to, but x11 is no longer being developed, so its not very secure to do so
additionally, Wayland is going to be default on kde, and Im not sure if that means that it’ll be default for me too if I update
not to mention that with it default on KDE, I’ll be running into more and more bugs that just, will not be fixed, because “use Wayland” will be the new response to bug reports (GNOME actively does this with a critical GTK4/libadwaita bug)
the point is, Wayland is being rushed and was never ready for default
Says who?
So when it’s the default, you just pick X11 from the drop-down, like I do for Wayland today.
Speculation. Gnome devs are notoriously stubborn, I don’t see that being true for KDE.
15 years is not a rush, and for most people it’s ready. Making it the default will serve as a push to get developers to make their applications support it.
Most applications get their Wayland support from the toolkit they are written in. Qt ( KDE ) and GTK ( GNOME ) apps are going to work in any Wayland compositor.
Some applications do “desktop” related things like try to take screenshots to set global hot keys. Wayland, strictly speaking, does not allow this. This becomes the job of the “compositor” ( Window Manager ) and so, if an application wants to do those things, it has to know how to talk to the compositor.
Increasingly, the desktop environments and compositors are aligning on how to surface some of these capabilities to applications in a common way.