pixelize to smal

[juckendesAuge]

Hello,
pixelize does not work for me.
The pixels are just too small. After that you can still read/see it.
Is there a way to set the pixel size?
Otherwise I do not understand that this does not work.

`
cat /etc/fedora-release
Fedora release 33 (Thirty Three)

uname -a
Linux localhost.localdomain 5.12.6-200.fc33.x86_64 #1 SMP Sat May 22 20:43:23 UTC 2021 x86_64 x86_64 x86_64 GNU/Linux

dnf info shutter
Letzte Prüfung auf abgelaufene Metadaten: vor 0:37:51 am Mo 31 Mai 2021 19:31:22 CEST.
Installierte Pakete
Name : shutter
Version : 0.94.3
Release : 5.fc33
Architecture : noarch
Size : 16 M
Quelle : shutter-0.94.3-5.fc33.src.rpm
Repository : @System
Aus Paketque : fedora
Summary : GTK+2-based screenshot application written in Perl
URL : http://shutter-project.org
Lizenz : GPLv3+
Description : Shutter is a GTK+ 2.x based screenshot application written in
: Perl. Shutter covers all features of common command line tools
: like scrot or import and adds reasonable new features combined
: with a comfortable GUI using the GTK+ 2.x framework.
`

Thanks a lot

With kind regards

[Photon89]

Looks like a duplicate of #226 There is another tool to hide private parts of the image, just below the plxelize tool.

[juckendesAuge]

Thank you very much.
I have look for this Bug, but i havent found it.

[juckendesAuge]

Looks like a duplicate of #226 There is another tool to hide private parts of the image, just below the plxelize tool.

Hello again,

I just tested it on two different images
and recorded the desktop with simplescreenrecorder. On one screenshot it works fine.
Not with the photo I took with my smartphone.
I have also cropped the image via shutter, so that it is as small as possible from the resolution. Because I thought that the pixelize function has a certain pixel size and it is therefore visible on images with high resolution. However, then even for the cropped image, the font was not pixelized enough.
The reference to the other bug alludes to the fact that this only happens when you get into the border areas. For me it is also the same in the middle of the image. Please have a look at the video.

shutter_pixelize-2021-06-01_10.20.07.mp4

Or you can watch it on Youtube. I have uploaded this video as not listed:
Pixelize Problem

Many greetings

juck.

Translated with www.DeepL.com/Translator (free version)

[DarthGandalf]

I've noticed that you zoomed the second picture out to make it fit on screen first. My guess is that the pixelize tool uses certain number of pixels regardless of zoom level.

Aha, https://github.com/shutter-project/shutter/blob/master/share/shutter/resources/modules/Shutter/Draw/DrawingTool.pm#L2477-L2494 suggests that it just scales the image down 10x and then back. So if the resolution is big enough, 10x is not enough to hide anything

[DarthGandalf]

Until this is fixed, you can use another tool ("censor"?) which replaces the parts of image with black/white pattern instead.

[juckendesAuge]

I've noticed that you zoomed the second picture out to make it fit on screen first. My guess is that the pixelize tool uses certain number of pixels regardless of zoom level.

Aha, https://github.com/shutter-project/shutter/blob/master/share/shutter/resources/modules/Shutter/Draw/DrawingTool.pm#L2477-L2494 suggests that it just scales the image down 10x and then back. So if the resolution is big enough, 10x is not enough to hide anything

Hello,
i have test it. It don't works with pixelize in the zoom.

shutter_pixelize_zoom_level-2021-06-01_11.08.11.mp4

But i have convert the 4000x3000 resolution to 800 with the program convert.
The 800 resolution works fine with pixelize.

shutter_pixelize_resolution_2-2021-06-01_10.56.47.mp4

yes, i can use a black and white pattern. But that does not look so good.

Thank you very much for help.

Edit:
Hello again,
I have just tested censor.
I'll stick with pixelizing though and converting the images to a smaller resolution beforehand, now that I know.

Thanks a lot

[Photon89]

Another report about a similar issue: #218

[limitedAtonement]

Another report about a similar issue: #218

Thank you, @Photon89, but I think that's unrelated. Even if #218 were fixed and data weren't leaked through pixelize anymore, this resolution-dependent issue would still be present.