Closed UnixLudi0 closed 6 months ago
apparently grimblast does produce a file format that satty can't read. I am a bit surprised, but lets have a look.. can you send me a sample?
grimblast copy screen - > outputfile
I just had a look at the source code of grimblast... you are using it wrong.
The help for copy
states: "Copy the screenshot data into the clipboard.". That is not what you want! You want to use save
: " "Save the screenshot to a regular file or '-' to pipe to STDOUT.". So your fixed command is:
grimblast save - | satty -f -
Nice 0 byte size That's still not work
grimblast save area - | satty --filename -
it works without problems for me
Interesting, I'm getting the following with that:
$ grimblast save area - | satty --filename -
[destroyed object]: error 0: Unsupported format
failed to screenshoot all outputs
Error: Unrecognized image file format
Error: Unrecognized image file format
Looks more like a grim / grimblast issue:
$ grim -g "$(slurp -o -r -c '#ff0000ff')" -
[destroyed object]: error 0: Unsupported format
failed to screenshoot all outputs
$ grim
[destroyed object]: error 0: Unsupported format
failed to screenshoot all outputs
Edit: https://github.com/hyprwm/Hyprland/issues/4735 Turning off 10-bit color fixes the issue for me
looks like .. maybe we can support them but opening an issue there - or better - fixing it?
As I know grimblast using grim and slurp, so I don't know why this happen: Maybe I'm doing something wrong?