Grimblast cursor

General
1

Does anyone else have the reticle cursor show up in the saved screenshot image when using grimblast copy area –-freeze? `

image
image307×193 20.7 KB

It’s the reticle cursor used to select the area to screenshot, but I feel like it shouldn’t be visible for the screenshot image itself. I haven’t seen anyone else complain about this, so I’m wondering if there is some weird issue with my setup that could be causing it? And it’s not the frozen cursor either, I can make both show up at the same time if I just select the region the frozen cursor is chilling at:

image
image219×155 9.06 KB

The --cursor flag is supposed to allow showing the cursor in the screenshot, so I assume the default behavior is to hide the cursor(s) right?

--cursor
include the cursors in the screenshot.

2

Test

image
image942×417 47.2 KB
Test 2

image
image1031×745 41.1 KB

Does not seem like I do

image
image864×481 12.6 KB

3

Thanks for the confirmation, I guess there is just something weird about my setup :/ I’ll keep looking into it. If anyone else is having this issue, please lmk

4

And I have this other issue where sometimes after selecting an area, the hyprpicker doesn’t end and I’m stuck unable to click anything and have to go to TTY to kill hyprpicker. This is another thing I haven’t heard anyone complain about before, so I’m wondering if that’s another thing that’s just broken on my system.

5

To have less problems, put the arguments that have dashes first. So:

grimblast --freeze copy area
6

Noted :+1: I think I did hear that somewhere, I can change that in my config. It doesn’t fix the cursor still being visible, but hopefully it fixes the other issue I get every now and then

7

I can reproduce this. Not quite sure how exactly this happens. At least not yet.

8

Aha, this is probably it.

Cursor being included without -c is indeed a known issue with wlroots software cursors.

9

Yep this was it. Since I’m using nvidia, it was recommended to have hardware cursors turned off, but turning it back on with

cursor {
    no_hardware_cursors = 0
}

fixed the cursor not vanishing during screenshots. However this of course invites the issues corresponding with why nvidia users are told to turn it off :frowning: It seems like it’s better than what it used to be though, the only issue I’m seeing is that my cursor vanishes when typing in firefox. Anyway, I’m glad to have finally figured out what the issue is. Hopefully one day either non-hardware cursors fixes this quirk, or nvidia drivers better support hardware cursors.

10

Where exactly did you add that config?

11

In the hyprland config Variables – Hyprland Wiki