111–120 of 130 posts
Recently gave up on Wayland (for the moment) due to the inability to screen share most applications on Google Meet. I realise this isn't really Wayland's fault, but that doesn't really solve my problem.
I can share screen with pipewire on Google Meet. It's not perfect, because you can select specific windows, but it works.
Recently gave up on Wayland (for the moment) due to the inability to screen share most applications on Google Meet. I realise this isn't really Wayland's fault, but that doesn't really solve my problem.
Agreed, this is where I'm at as well. In general, I actually found sway to be wonderful, but it's not worth the hassle of switching over anytime I have a meeting where I could possibly need to screen share.
Earlier quoted context omitted.
I was researching the issue and noticed wlr-screencapture. I was hoping to see it at https://github.com/wayland-project/wayland-protocols too, but no luck. Thanks for the lead on xfg-desktop-portal. It is fascinating watching the near decade-long journey as Wayland tackles screenshots.
Whats fascinating to me is that I had NO idea there was some battle of some sorts in the "screenshot biosphere" TBH I use GreenShot exclusively as it is seamless and does every thing I Need [0] [0] https://i.imgur.com/x0oMzb6.png And I can do things like this [1] https://i.imgur.com/ZtR60qw.png Nested fucking screenshots. All I have to do is hit prtscrn each iteration I want to capture
- Wayland team: "Out of scope, lol" (security, keeping it as generic as possible)
- Gnome: "Works for us" (dbus APIs specific to Gnome")
- wlroots: Developing extensions to the Wayland protocol and attempting to get them into Wayland proper and adopted by others
- KDE: Mostly going the KDE way where it makes sense, but open to wlr persuasion (they will implement layer-shell, but keep their own ways for some other things)
- Freedesktop group (I'm the least familiar with this one): Promoting some stuff meant for Flatpak, but not really showing much initiative beyond that
This fragmentation is one of the reasons Wayland adoption is slow. Users expect things to work across desktops as they used to on X and developers aren't always clear about compatibility either. Many people seem to think that Wayland is just another display server (it's not, it's a protocol!) with all of the old functionality and are frustrated when they find out it is not.
The fragmentation will probably exist for quite a while. Pipewire will probably take over the screen sharing space and KDE and wlroots will share more protocols (Gnome gonna Gnome, of course), but there are just many things that are compositor family- or even compositor specific, like an xkill-equivalent, which I still miss dearly.
Earlier quoted context omitted.
I was researching the issue and noticed wlr-screencapture. I was hoping to see it at https://github.com/wayland-project/wayland-protocols too, but no luck. Thanks for the lead on xfg-desktop-portal. It is fascinating watching the near decade-long journey as Wayland tackles screenshots.
By fascinating you mean depressing, right? If Wayland has taken this long to get a basic feature like screenshots what other features does it not support?
Wayland doesn't actually support screenshots, it's all extensions.
Earlier quoted context omitted.
Major distros have been shipping wayland as the default backend for almost five years! I mean, yes, it's a lot of work. But it was wildly premature, and the community support for this stuff has been nothing short of a disaster of apathy and ignorance. Which is to say: what you say is true, but there's no excuse for breaking screenshots (!) for half a decade in the name of "progress". (And I say that as someone who ge…
Really only Fedora has shipped Wayland by default for five years, and they do this with a lot of other tech as well (GNOME 3 and Cgroups v2 to name some more). If there is no user demand, nobody wants to do the work of supporting new technology, which is why Fedora releases things before they are ready. Anyone using Fedora should know this.
I mean, no one was surprised in 2016 when Wayland landed that there would be bumps in the road. It's 2021 now!
Earlier quoted context omitted.
Reading grim’s README, it looks like a terminal tool, while flameshot is a GUI tool. You mean flameshot should just wrap grim on wayland?
grim can write the image to stdout. GUI like [1] can read images from stdin. You can make a script that pipes one to the other and bind that in your compositor. [1]: https://github.com/jtheoof/swappy
If you're looking for a screenshot tool for macOS, I cannot recommend CleanShot X highly enough. It in the league of its own, with scroll capture, gifs, even changing your desktop in the screenshot, but not "in reality". I'm really impressed.
Yes. A thousand times. At our small company we trialed Jumpshare, CloudApp and a bunch of other stuff for both video and screenshots. Cleanshot was by far the best, and costs the least. Unlike most tools which are SaaSified and require a monthly subscription, CleanShot still offers a one-off license. It's a steal. The only one at our company not using Cleanshot is a developer on Linux. I think he's using Flameshot.
I just want to remark upon how strange it is Mac users are just so nonchalantly paying for bits and bobs because their OS doesn't do things they need it to do.
I spent some time getting my Linux setup _just so_ and feel like I gave macOS a good go when I tried it for 11 months as a daily driver, but I just couldn't take it.
Find a little niggling problem that bothers you just a little bit? Here's a program that fixes it, but it's $5.
Repeat ad nauseam.
Earlier quoted context omitted.
it kinda is. the whole wayland ecosystem is slowling taking shape month after month. and given the radical change that wayland is, most thing have to be re-implemented using radically different tooling, libraries and approaches, which is very similar to re-inventing.
question for those out of the loop - what is Wayland? how is it related to Flameshot? it is mentioned but not explained in the post.