Below I will describe the technical perspective.

(Disclaimer: the description below does not necessarily represent our company's opinion of what constitutes a "software issue". If the issue you're seeing is affecting your use of our products and a suitable workaround cannot be found, please consider opening a support case.)

Pixel dimension changes are expected in deskewing, because rotating a rectangle by a few degrees will cause the corners of that rectangle to edge out a little bit. To avoid losing those pixels, the output image will have its width and height slightly increased to accommodate all original pixels. However, a change in DPI is not expected from deskewing.

The symptom described by Miruna is a separate issue, and that issue affects all image-modifying operations. Basically, the low-level library we use in Laserfiche handles the DPI values in floating-point, because several image formats (such as PNG and BMP) adopted image resolution units that would translate into non-integer-valued DPI values. However, the mid-level libraries were written to treat DPI values as integer-only. As a result, non-integer DPI values were truncated (as opposed to getting rounded to the nearest integer), which results in DPI values getting decreased by one for each image-modifying operation.