[SOLVED] Command line utility to take screenshots KDE Wayland

flatmoll · 2024-08-26 19:41:39

Grim says:

compositor doesn't support wlr-screencopy-unstable-v1

Scrot, maim and similar only work on Xorg.
Ksnip refuses to work. Flameshot outputs bad quality images.
Generally I would prefer something command line only rather than these two.
Spectacle brings 360 MB of dependencies - too much for a screenshot tool?

Do you know any other tool (maybe on AUR) or solution to grim?
Thank you.

Last edited by flatmoll (2024-08-27 13:06:03)

Trilby · 2024-08-26 19:48:57

Grim only works with wlroots compositors, so there is no "solution" for using it with KDE anymore than there is a solution to use scrot or maim - they also work with a different protocol than KDE.

You'd need a tool that uses a KDE protocol, and as I don't believe KDE even has a public protocol for this feature, there could not be any third party tools to do it. You'll need to use whatever tools KDE provides itself which appears to just be spectacle.

seth · 2024-08-26 19:56:00

https://invent.kde.org/plasma/kwin/-/bl … type=heads ?

flatmoll · 2024-08-26 20:44:06

seth wrote:

https://invent.kde.org/plasma/kwin/-/bl … type=heads ?

I see the source, but what do I do?

1. Wait for the update that will bring this plugin?
2. Download from this source and build kwin on my laptop?
3. Somehow enable it?
4. It was just a reply to the previous message.

seth · 2024-08-26 21:07:05

If the screenshot effect is enabled you should have access to it anyway

qdbus6 org.kde.KWin.ScreenShot2

Though see https://forum.kde.org/viewtopic.php%3Ff … 76422.html and https://github.com/netblue30/firejail/issues/5127 - seems restricted, so you'll have to write your own screenshot tool, resp. create a .desktop file (in a privileged path) that allows eg. qdbus6 to use the screenshot protocol (what of course completely undermines the restriction)

Welcome to the wonderful world of wayland.

Trilby · 2024-08-26 21:14:33

I stand corrected. There is a KDE-specific public protocol. So it's possible for third-party tools to be written to use that protocol. But if it's new and apparently still not well known, it's less likely that any haven been written. Also - why are they using dbus rather than wayland for that?? *headdesk*

KDE HQ: "Hey, there are two common methods we could use to do this screenshot thing, but both kinda suck. So lets do it yet another completely different way that sucks a lot more." Note I mock because generally speaking I expect better from KDE people. This is the kind of result I'd expect to see from that other big DE.

Last edited by Trilby (2024-08-26 21:18:48)

flatmoll · 2024-08-26 22:22:56

seth wrote:

Welcome to the wonderful world of wayland.

AFAIK grim works with Weston, so it's probably a world of KDE, which otherwise works for me. I would use Xorg + maim, apparently fixing some inconveniences with Wayland, if it hadn't this 5 fps clunky scroll with touchpad and visual glitches with videos on my laptop. It may be iGPU compatibility, yet no shopping lists. Thanks Trilby and seth for your help.

Edit: I searched the effects in settings manager and found Screenshot: helper effect for screenshot tools, which is enabled. There is no more information.

$ qdbus6 org.kde.KWin.ScreenShot2

/
/ColorPicker
/Compositor
/Effects
/FTrace
/KWin
/Layouts
/Plugins
/ScreenSaver
/Scripting
/Scripting/Script0
/Session
/VirtualDesktopManager
/VirtualKeyboard
/WindowsRunner
/component
/component/ActivityManager
/component/KDE_Keyboard_Layout_Switcher
/component/kaccess
/component/kcm_touchpad
/component/kmix
/component/ksmserver
/component/kwin
/component/mediacontrol
/component/org_kde_dolphin_desktop
/component/org_kde_konsole_desktop
/component/org_kde_krunner_desktop
/component/org_kde_kscreen_desktop
/component/org_kde_plasma_emojier_desktop
/component/org_kde_powerdevil
/component/plasmashell
/component/systemsettings_desktop
/kglobalaccel
/org
/org/freedesktop
/org/freedesktop/ScreenSaver
/org/kde
/org/kde/KWin
/org/kde/KWin/BlendChanges
/org/kde/KWin/EIS
/org/kde/KWin/EIS/InputCapture
/org/kde/KWin/EIS/RemoteDesktop
/org/kde/KWin/Effect
/org/kde/KWin/Effect/OutputLocator1
/org/kde/KWin/HighlightWindow
/org/kde/KWin/InputDevice
/org/kde/KWin/InputDevice/event0
/org/kde/KWin/InputDevice/event1
/org/kde/KWin/InputDevice/event10
/org/kde/KWin/InputDevice/event2
/org/kde/KWin/InputDevice/event3
/org/kde/KWin/InputDevice/event4
/org/kde/KWin/InputDevice/event6
/org/kde/KWin/InputDevice/event8
/org/kde/KWin/InputDevice/event9
/org/kde/KWin/NightLight
/org/kde/KWin/ScreenShot2

Last edited by flatmoll (2024-08-26 23:14:16)

seth · 2024-08-27 06:24:00

I meant because of the highly fragmented feature API of the wayland ecosystem to fill in hte gaps of a skeleton protocol - resulting in the most basic stuff being ridiculously hard to come by and everything's incompatible with everything else. 15 years in… (I'm pretty sure when X11 was 15 years old, the first one or two attempts to replace it had already failed…)

"qdbus6 org.kde.KWin.ScreenShot2 /org/kde/KWin/ScreenShot2", but the API uses a QVariantMap which (iirc) mean's you'll have to use https://man.archlinux.org/man/core/dbus/dbus-send.1.en to pass the array and it returns the image on a pipe and I'M not sure any of the diagnostic tools are capable of that

flatmoll · 2024-08-27 13:05:33

I can only imagine what image on a pipe looks like
Sorry for creating that many threads, but maybe I will be able to switch back to X.

seth · 2024-08-27 13:08:19

Do you have an open thread regarding your X11 issues?

flatmoll · 2024-08-27 13:14:33

I am currently writing it.

Trilby · 2024-08-27 13:20:31

flatmoll wrote:

I can only imagine what image on a pipe looks like

An image on a pipe is no image at all. It's also not a pipe either! Treachery I say, that image is just treachery.

For what it's worth, I recently switched back to X11 from wayland. I had some unresolved graphical issues, but I realized running an X11 compositor was sufficient to avoid them (picom in my case). I avoided these compositors like the plague when I originally used X11, but running picom as a background process is definitely the lesser of two evils compared to running a wayland compositor that gets the graphics right but doesn't do anything else I want.

Last edited by Trilby (2024-08-27 13:41:03)

flatmoll · 2024-08-27 13:35:48

You have just answered one of my questions from the 'new' thread, thanks!
The graphical glitch came from the compositor being disabled.
I will put a link.

Arch Linux

#1 2024-08-26 19:41:39

[SOLVED] Command line utility to take screenshots KDE Wayland

#2 2024-08-26 19:48:57

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

#3 2024-08-26 19:56:00

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

#4 2024-08-26 20:44:06

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

#5 2024-08-26 21:07:05

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

#6 2024-08-26 21:14:33

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

#7 2024-08-26 22:22:56

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

#8 2024-08-27 06:24:00

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

#9 2024-08-27 13:05:33

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

#10 2024-08-27 13:08:19

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

#11 2024-08-27 13:14:33

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

#12 2024-08-27 13:20:31

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

#13 2024-08-27 13:35:48

Re: [SOLVED] Command line utility to take screenshots KDE Wayland

Board footer