Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

black image on gnome wayland #67

Open
lesmana opened this issue Oct 28, 2016 · 11 comments
Open

black image on gnome wayland #67

lesmana opened this issue Oct 28, 2016 · 11 comments

Comments

@lesmana
Copy link

lesmana commented Oct 28, 2016

maim used to work fine on my system. I use arch linux. I updated my system and now have gnome 3.22. gnome 3.22 uses wayland by default. Since that update maim produces black images. the images have the same resolution as my screen. 1280x800.

Please confirm whether this is a problem with wayland or just a problem on my system.

$ maim --version
maim v3.4.47

Copyright (C) 2014 Dalton Nell, Maim Contributors
(https://github.com/naelstrof/maim/graphs/contributors)
$ uname -a
Linux lestop 4.8.4-1-ARCH #1 SMP PREEMPT Sat Oct 22 18:26:57 CEST 2016 x86_64 GNU/Linux
$ gnome-shell --version
GNOME Shell 3.22.1

Please tell me what more information do you need.

@lesmana
Copy link
Author

lesmana commented Nov 4, 2016

this "bug" is shared with other screenshot tools like scrot and import from imagemagick.

please follow my (mis)adventures with the screenshot tools in this arch linux forum thread: https://bbs.archlinux.org/viewtopic.php?pid=1662309

@naelstrof
Copy link
Owner

Maim simply doesn't support wayland.

It's due for a re-write, but until I have time for it you'll be better off submitting bug reports to the wayland team since imlib2's X11 calls aren't being translated properly.

@CamilleScholtz
Copy link
Contributor

CamilleScholtz commented Nov 4, 2016

Also wayland is a protocol. The compositors, GNOME in this case implement calls like screenshotting themselves. "supporting wayland" means means independently supporting GNOME, KDE, sway, enlightenment, etc.

@lesmana
Copy link
Author

lesmana commented Nov 10, 2016

I reported the bug to the wayland developers

https://bugs.freedesktop.org/show_bug.cgi?id=98672

@CamilleScholtz
Copy link
Contributor

CamilleScholtz commented Nov 10, 2016

Yeah wayland is unusable for modular deskop usage by design in the name of """"security"""" sadly, now you just need to exploit the compositor.

@MrSorcus
Copy link

On sway it's has trouble too.
Black image always and broken with -i argument
laptop% maim -i $(xdotool getactivewindow)
Your windowmanager claims not to support _NET_ACTIVE_WINDOW, so the attempt to query the active window aborted.
xdo_get_active_window reported an error
maim: option requires an argument -- 'i'

@naelstrof
Copy link
Owner

I mean that's actually xdotool not working. X tools probably won't work on Wayland, but I don't think maim will either. Neither xdotool or maim are made with wayland in mind.
I plan to add support for wayland soon, but it'd require a re-write and I simply don't have enough time.

@hmnd
Copy link

hmnd commented Mar 10, 2018

Any update on this? @naelstrof

@naelstrof
Copy link
Owner

Wayland doesn't support 3rd party screenshot apps and currently doesn't plan to. It's too secure and would require Wayland to be re thought a bit.
Probably isn't going to happen anytime soon. Sorry.

@victorz
Copy link

victorz commented Nov 20, 2021

Wayland doesn't support 3rd party screenshot apps and currently doesn't plan to. It's too secure and would require Wayland to be re thought a bit. Probably isn't going to happen anytime soon. Sorry.

I use grim in combination with slurp in order to get screenshots on Wayland (I use sway as my WM).

My script that I trigger:

#!/bin/bash

SCREENSHOTS_DIR=$(xdg-user-dir PICTURES)/screenshots
[[ ! -d "$SCREENSHOTS_DIR" ]] && mkdir -p "$SCREENSHOTS_DIR"

slurp | grim -g - "$SCREENSHOTS_DIR"/$(date +%F_%T).png

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

7 participants
@victorz @lesmana @naelstrof @CamilleScholtz @hmnd @MrSorcus and others