News for hackers. Stuff that matters.
Re:Understanding the working of X11 from the ground up (2017) by crispinb on Sunday September 22, 2019 @05:26AM (#21040446)
> The screenshot tool is just flat out not present when running under Wayland due to the above issue.

That's odd - it's present (and functioning) in my Firefox (69.0.1) running on Gnome-on-wayland

Firefox is generally quite crashy, however, which I'm guessing is Wayland-related

Re:Understanding the working of X11 from the ground up (2017) by gmueckl on Sunday September 22, 2019 @10:01AM (#21041393)
So Firefox supports screenshots when running on the Gnome compositor, but not running on sway? Looks like we're heading into interesting times where applications are getting tied to certain DEs with little to no cross-compatibility.
Re:Understanding the working of X11 from the ground up (2017) by MayeulC on Monday September 23, 2019 @05:36PM (#21053986)
IDK. Sway is my daily driver. I just checked Firefox, and the screenshot tool works as expected (including clipboard). So unless GP is talking about capturing non-Firefox windows with that tool, I do not have that issue.

This Firefox instance is running on native Wayland. The only issue I have with it is sometimes the coordinates for the context menu are wrong.

But yeah, there might be compat issues, if some protocols are required for stuff. But Wayland itself is the baseline: you'll always be able to draw windows and interact with them.

What's left to extra protocols isn't guaranteed to work: control of the compositor with a client, for instance (color correction, virtual keyboard, screenshots, window placement, screen geometry, window decorations, etc.) is completely up to the compositor (and the protocols it can speak with the client). So is other stuff, like graphics tablet input (with pressure sensitivity, tile, etc), minimizing windows, window miniatures as used for KDE's taskbar as well, I think.

But then, it's not like everything worked flawlessly everywhere on X either :) And as long as the baseline is solid, we can build on it.

Re:Understanding the working of X11 from the ground up (2017) by jchw on Tuesday September 24, 2019 @04:07PM (#21064068)
I may have done something wrong. I am not highly knowledgable here. For example, I just learned of Pipewire.

That said, the problem occurred for me when using the NixOS package firefox-wayland. It is possibly better to use upstream firefox with Wayland, but I have not tried; I am just running firefox on Xwayland for now.

Re:Understanding the working of X11 from the ground up (2017) by MayeulC on Thursday September 26, 2019 @08:24AM (#21080245)
I don't know how the Firefox package is built on NixOS, but I just run the one from Arch Linux with the following environment variables:

    MOZ_WEBRENDER=1 MOZ_USE_XINPUT2=1 GDK_BACKEND=wayland
Re:Understanding the working of X11 from the ground up (2017) by zapzupnz on Sunday September 22, 2019 @05:22PM (#21044048)
> interesting times where applications are getting tied to certain DEs with little to no cross-compatibility

What's old is new, apparently.