800% freeze number when zooming in/out of image

[grofaty]

One strange thing is happening with zoom number in Pinta 1.6 on Ubuntu 14.04.
1. Open Pinta.
2. New from toolbar and select 100 x 100.
3. In zoom toolbar there is 100% zoom displayed. This is as expected because small image can clearly fit the screen. Click 10-times on zoom "+" button next to the zoom number. Everything works fine in my case zoom number finally gets to 800%.
4. Click on "+" button next to zoom number one more time. Image enlarges as expected, but number still stays at 800%. I can still click on zoom button an image few more times and image enlarges every time (I can see this because ruler at right site of screen changes every time).
5. Now what ever I do with zooming clicking on "-" or "+" button and number still stays at 800%.
6. Strange enough. Close down image and there is still "800%" present. New image what ever size and this "800%" zoom number is still there independently of image size displayed on canvas.

Problem is only in displaying number 800%. Additionally when clicked inside zoom input box and typing any number. This typed in number is not displayed(there is 800% displayed all the time) but it is clearly visible that change takes effect, e.g typing in number 1 and image gets very small, pressing additional 0 (to get 10%) and image gets much larger, pressing additional 0 (to get 100%) and image is in 100% state, etc.

All other zooming works fine. So pressing "-", "+" button, selecting number from "zoom selection drop-down number from toolbar" works fine. Zoom icon from Tools panel also works fine, also working fine <CTRL> with "+" or "-" button, <CTRL> with "mouse scroller"... every zoom feature works fine, except freezing 800% number.

[grofaty (grofaty)]

I have now installed Pinta 1.7.0.218 development build from http://pinta-project.com/builds and magically problem disappeared. I still have both versions installed (1.6 and 1.7.0.218) and I can switch between them and it is clear 1.6 has the problem and problem does not appear in 1.7.0.218. It looks some change in code that fixed the problem (intentionally or unintentionally).

This bug report should probably set to "fixed", to indicate in "release log" that bug was fixed.

[Deleted User (user5527-deactivatedaccount)]

I can confirm this bug doesn't appear for me either on the master branch with Linux. This should be closed.