Area selection cursor is shown in final screenshot

[diniamo]

As you can see in the screenshot, the cursor I selected the area with is shown. I didn't pass --cursor.

[fufexan]

Can you post the full command you've used to take the screenshot? Also, are you using NVidia/have the WLR_NO_HARDWARE_CURSORS=1 variable set?

[diniamo]

Yes, I use nvidia, no I don't have it set, but it doesn't seem to make a difference if I do.

bind = $ctrl, Print, exec, ~/.local/bin/grimblast --notify --freeze copy area

And I also made a small modification in grimblast where slurp is called:

slurp -c ed8796 -b 00000000 -s 00000000 -B 00000000

[fufexan]

Sounds like a nvidia issue, as I don't see the cursor when running the same command.

As can be seen, my hyprpicker is built from a commit in 2023-10-05, so check if yours might be out of date.

[diniamo]

I have the latest/same commit.

[kRHYME7]

We found out that grimblast captures hyprpicker cursor. Should we request a feature on hyprpicker to make cursor transparent? Or should we implement a separate package for freezing?

[fufexan]

I haven't seen that, mind showing an example? Maybe record a video of it happening?

[kRHYME7]

Sorry for the very late response.
Using Arch package

❯ paru -Q grimblast
grimblast-git r66.bfd3e0e-1

Here is my env also if this could cause something.

❯ cat ~/.config/hypr/userprefs.conf | grep 'env'
env = GDK_SCALE,1
env = WLR_NO_HARDWARE_CURSORS,1
env = WLR_EGL_NO_MODIFIERS,1
env = XDG_CURRENT_DESKTOP,Hyprland
env = XDG_SESSION_TYPE,wayland
env = XDG_SESSION_DESKTOP,Hyprland
env = GDK_BACKEND,wayland,x11
env = QT_QPA_PLATFORM,wayland
env = SDL_VIDEODRIVER,wayland
env = CLUTTER_BACKEND,wayland
env = QT_AUTO_SCREEN_SCALE_FACTOR,2
env = QT_WAYLAND_DISABLE_WINDOWDECORATION,1
❯ cat ~/.config/hypr/hyprland.conf | grep 'env'
exec-once = dbus-update-activation-environment --systemd WAYLAND_DISPLAY XDG_CURRENT_DESKTOP # for XDPH
exec-once = dbus-update-activation-environment --systemd --all # for XDPH
exec-once = systemctl --user import-environment WAYLAND_DISPLAY XDG_CURRENT_DESKTOP # for XDPH
# Some default env vars.
env = XDG_CURRENT_DESKTOP,Hyprland
env = XDG_SESSION_TYPE,wayland
env = XDG_SESSION_DESKTOP,Hyprland
env = GDK_BACKEND,wayland
env = QT_QPA_PLATFORM,wayland
env = QT_QPA_PLATFORMTHEME,qt5ct
env = QT_WAYLAND_DISABLE_WINDOWDECORATION,1
env = QT_AUTO_SCREEN_SCALE_FACTOR,1
env = MOZ_ENABLE_WAYLAND,1

231112_15h45m08s_recording.mp4

Thanks 🙏

[fufexan]

My guess is env = WLR_NO_HARDWARE_CURSORS,1 is causing the cursor to keep showing.

[diniamo]

Even in non-nvidia environments, there are issues without that variable, but this should be fixable in the screenshot stack's code, right?

[fufexan]

Not sure what "screenshot stack" refers to here, but it's likely a bug with either slurp or hyprpicker.

[diniamo]

It refers to grim, slurp, and hyprpicker.

[vaxerski]

none of these are the culprit, it's hyprland's fault. FWIW, same will happen on any wlroots compositor. We could get around it, but it would be inefficient.

[waddyhussain]

Had this issue for a while, but only just found out about the workaround of removing --freeze (or uninstalling hyprpicker if you don't use it). Had to look through one of the other threads to find it, so posting here in case anyone comes across this issue while searching.

[diniamo]

Removing freeze makes it even worse for me, as now both the cursor and the box I used to select the area are present in the screenshot.

[Ilirski]

Not sure if it's related, but I have to double click in order to finish selecting area when doingenv GRIMBLAST_EDITOR=gimp grimblast --notify --freeze edit area

Video_2024-01-16_15-06-26.mp4

Removing --freeze makes it open editor on click as expected.

[PacificViking]

I am having the same error with WLR_NO_HARDWARE_CURSORS=1 on Hyprland/Nix with both grim and grimblast.

[carschandler]

Also have this error on Hyprland/NixOS/nVidia with WLR_NO_HARDWARE_CURSORS=1

[leon-erd]

For me omitting the --freeze option solves the problem of the cursor being in the image (but I'm also not using nvidia
/WLR_NO_HARDWARE_CURSORS=1).
Regarding the area selection box being visible in the image: I realized that the problem was due to the screenshot being taken before the closing layer animation of the selection was finished.
Disabling the animations for the selection in hyprland with:

layerrule=noanim, hyprpicker
layerrule=noanim, selection

Solved that for me! Maybe it helps someone :)

[diniamo]

WLR_NO_HARDWARE_CURSORS=1 should be removed by everyone at this point, it's been fixed in git for a while, and the latest stable release has the patch too.

That also means we can solve this issue I guess.

[roastedcheese]

getting this again on -git and without WLR_NO_HARDWARE_CURSORS=1

[diniamo]

Same, I forgot to report

[vaxerski]

git ignores the env, it uses cursor:no_hardware_cursors instead

[roastedcheese]

don't have that set either

[diniamo]

For anyone with this issue, cursor:allow_dumb_copy = true seems to fix it after the aq rewrite. I don't know if it has any downsides, I haven't noticed the hitch the hl wiki mentions.

[kRHYME7]

Is this device dependent?

no_hardware_cursors = true

no_hardware_cursors = false

[diniamo]

You should have no_hardware_cursors = false

[m2neral]

I tried everything on this page and it still doesn't work with or without --freeze. I'm on nvidia.