ctrl + zooming produces corrupted canvas display

Bug #850310 reported by grofaty
30
This bug affects 5 people
Affects Status Importance Assigned to Milestone
Pinta
Triaged
Medium
Unassigned
Arch Linux
New
Undecided
Unassigned

Bug Description

Pinta 1.0 on Windows XP SP3
1. Create new 800 x 600 image.
2. Press <Ctrl> + mouse wheel down to reduce zoom to 66%.
3. Move mouse to the bottom and point it at the gray area bellow image.
4. Press <Ctrl> + mouse wheel up to increase zoom level. Display gets corrupted (see attachment).

Tags: windows
Revision history for this message
grofaty (grofaty) wrote :
Changed in pinta:
importance: Undecided → Medium
status: New → Triaged
Revision history for this message
Cameron White (cameronwhite91) wrote :

Note: I've only been able to reproduce this on Windows (it works fine on Ubuntu 11.10 for me)

Revision history for this message
grofaty (grofaty) wrote :

Now I have also tested on Ubuntu 11.04 and it also works fine without problem. Lately I have reported some bugs that only appear on Windows and do not appear on Ubuntu. Is there some Gtk# problem or something. Probably it would be nice to have the same Gtk# installed on both operating systems to know if the problem is Pinta problem or some out-of-reach bug. Is there still 2.12.9 Gtk# recommended (officially on pinta-project.org web page)?

Revision history for this message
Cameron White (cameronwhite91) wrote :

The Mono downloads page has GTK# 2.12.10 available for download (http://www.go-mono.com/mono-downloads/download.html)

I'll try that later and see if it solves any of the issues.

tags: added: windows
Revision history for this message
grofaty (grofaty) wrote :

I have installed Gtk# 2.12.10 and the problem remains.

Revision history for this message
Johnathan Morlock (johnathan-morlock) wrote :

+1 for me... thought what I saw was the image being duplicated. Which I suppose is exactly the same thing.

Revision history for this message
grofaty (grofaty) wrote :

Just a quick update. Tested on Pinta 1.2 on Windows sp3 and problem persists (like described in bug report). But tested on
latest development on Ubuntu 11.10 and problem does not appear (like described in #2). So it looks like Windows problem.

Revision history for this message
Cameron White (cameronwhite91) wrote :

Bumping in priority since this is a fairly easy issue to encounter.

Changed in pinta:
importance: Medium → High
Revision history for this message
Jonathan Pobst (jpobst) wrote :

It has something to do with zoom recentering code. If you zoom with mouse on the right side of the image it occurs, but not on the left side of the image. If you minimize to force a full redraw, you can see that the entire canvas is misplaced, it's not just a Invalidate issue.

Revision history for this message
Johnathan Morlock (johnathan-morlock) wrote : Re: [Bug 850310] Re: ctrl + zooming produces corrupted canvas display

Hey Jonathan,

I have Pinta 1.3 installed and so far it seems to be working correctly
now. Thanks for the follow up!

Thank you,
Johnathan

Email: <email address hidden>
Website: http://www.tsgcomputers.net

Linux User ID: 498415

Eph. 3:20-21

On 05/03/2012 11:35 PM, Jonathan Pobst wrote:
> It has something to do with zoom recentering code. If you zoom with
> mouse on the right side of the image it occurs, but not on the left side
> of the image. If you minimize to force a full redraw, you can see that
> the entire canvas is misplaced, it's not just a Invalidate issue.
>

Revision history for this message
grofaty (grofaty) wrote :

I have tested this problem one's more on Pinta 1.3 on Windows XP following bug description (top post) in this thread. Problem still persists. I have also tested this on latest Pinta development on Ubuntu 12.04 and it does not appear. But as stated in #2 and #3 it looks like this is a Windows only problem.

Johnathan Morlock, what is your operating system?

Revision history for this message
grofaty (grofaty) wrote :

Retested on Pinta v1.4 on Windows XP bug remains (see bug description in first post of this bug report).
Also tested in Pinta v1.4 on Ubuntu 12.04 and there is no problem.
So it looks like Windows specific.

P.S. I think we can lower importance of this bug to Medium or Low.

Revision history for this message
Johnathan Morlock (johnathan-morlock) wrote :

Be sure to bring this up to the Google Group.

Thank you,
Johnathan

Email: <email address hidden>
Website: http://www.tsgcomputers.net

Linux User ID: 498415

Eph. 3:20-21

On 09/27/2012 05:34 AM, grofaty wrote:
> Retested on Pinta v1.4 on Windows XP bug remains (see bug description in first post of this bug report).
> Also tested in Pinta v1.4 on Ubuntu 12.04 and there is no problem.
> So it looks like Windows specific.
>
> P.S. I think we can lower importance of this bug to Medium or Low.
>

Revision history for this message
Cameron White (cameronwhite91) wrote :

I'm in favour of leaving this as High priority, since it's a very easy bug to encounter and doesn't look very good

Revision history for this message
grofaty (grofaty) wrote :

I can still reproduce the bug with pinta-1.5-preview-20130518 on Windows XP just like in the bug report.

Revision history for this message
grofaty (grofaty) wrote :

I can still reproduce with Pinta 1.6 prerelease build from source. I tested on Windows 7. Problem is Windows specific, it does not appear on Ubuntu 14.04.

Cameron, can you please do one of the two things: assign milestone to this "high" priority bug or lower the priority of bug. High priority bugs should have milestone defined.

Changed in pinta:
importance: High → Medium
Revision history for this message
sdaau (sd-imi) wrote :
Download full text (4.7 KiB)

On Ubuntu 14.04.3 LTS, and pinta 1.3-3ubuntu0.14.04.2, when I open image, make selection, copy, paste, and move around and zoom in, I get this:

MONO_CAIRO_DEBUG_DISPOSE=1 pinta myfile.png

...

(Pinta:3551): GLib-GObject-WARNING **: Attempt to add property __gtksharp_11_Pinta_Gui_Widgets_CellRendererSurface::surface after class was initialised
Cairo.Pattern is leaking, programmer is missing a call to Dispose
Allocated from:
   at System.Environment.get_StackTrace()
   at Cairo.CairoDebug.OnAllocated(IntPtr obj)
   at Cairo.Pattern..ctor(IntPtr handle, Boolean owned)
   at Cairo.Gradient..ctor(IntPtr handle, Boolean owned)
   at Cairo.LinearGradient..ctor(Double x0, Double y0, Double x1, Double y1)
   at MonoDevelop.Components.Docking.CustomFrame.OnExposeEvent(Gdk.EventExpose evnt)
   at Gtk.Widget.exposeevent_cb(IntPtr widget, IntPtr evnt)
   at Gtk.Container.gtksharp_container_invoke_gtk_callback(IntPtr , IntPtr , IntPtr )
   at Gtk.Container+CallbackInvoker.Invoke(Gtk.Widget w)
   at MonoDevelop.Components.Docking.DockContainer.ForAll(Boolean include_internals, Gtk.Callback callback)
   at Gtk.Container.Forall_cb(IntPtr container, Boolean include_internals, IntPtr cb, IntPtr data)
   at Gtk.Widget.gtksharp_widget_base_expose_event(IntPtr , IntPtr )
   at Gtk.Widget.OnExposeEvent(Gdk.EventExpose evnt)
   at MonoDevelop.Components.Docking.DockContainer.OnExposeEvent(Gdk.EventExpose evnt)
   at Gtk.Widget.exposeevent_cb(IntPtr widget, IntPtr evnt)
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at Pinta.MainClass.Main(System.String[] args)
Cairo.Pattern is leaking, programmer is missing a call to Dispose
Allocated from:
   at System.Environment.get_StackTrace()
   at Cairo.CairoDebug.OnAllocated(IntPtr obj)
   at Cairo.Pattern..ctor(IntPtr handle, Boolean owned)
   at Cairo.Gradient..ctor(IntPtr handle, Boolean owned)
   at Cairo.LinearGradient..ctor(Double x0, Double y0, Double x1, Double y1)
   at MonoDevelop.Components.Docking.CustomFrame.OnExposeEvent(Gdk.EventExpose evnt)
   at Gtk.Widget.exposeevent_cb(IntPtr widget, IntPtr evnt)
   at Gtk.Container.gtksharp_container_invoke_gtk_callback(IntPtr , IntPtr , IntPtr )
   at Gtk.Container+CallbackInvoker.Invoke(Gtk.Widget w)
   at MonoDevelop.Components.Docking.DockContainer.ForAll(Boolean include_internals, Gtk.Callback callback)
   at Gtk.Container.Forall_cb(IntPtr container, Boolean include_internals, IntPtr cb, IntPtr data)
   at Gtk.Widget.gtksharp_widget_base_expose_event(IntPtr , IntPtr )
   at Gtk.Widget.OnExposeEvent(Gdk.EventExpose evnt)
   at MonoDevelop.Components.Docking.DockContainer.OnExposeEvent(Gdk.EventExpose evnt)
   at Gtk.Widget.exposeevent_cb(IntPtr widget, IntPtr evnt)
   at Gtk.Application.gtk_main()
   at Gtk.Application.Run()
   at Pinta.MainClass.Main(System.String[] args)

(Pinta:3551): GLib-CRITICAL **: Source ID 235 was not found when attempting to remove it

(Pinta:3551): GLib-CRITICAL **: Source ID 200 was not found when attempting to remove it

(Pinta:3551): GLib-CRITICAL **: Source ID 149 was not found when attempting to remove it

(Pinta:3551): GLib-CRITICAL **: Source ID 223 was not found when attempting to remove it
...
(Pinta:3551): GLib...

Read more...

Revision history for this message
sdaau (sd-imi) wrote :

forgot to say that as others described in the bug, once I paste and zoom in/out, the display gets corrupted and images/pixels go missing...

Revision history for this message
Roger Peartree (pereiradorogerio) wrote :

Im having this issue on Pinta 1.6, in Manjaro Linux XFCE x64 17.1.6, so, an Arch Linux based distro. After I've finished editing, zooming out produced the horrible result that I show on the screenshot attached to this post. The BIG problem is that the corrupted image gets saved as it is: corrupted. So I don't really like GIMP, and this bug also affects Xubuntu 16.04.4 and Linux Mint 18.3. Pity that after so much work (I'm not a designer, it's not easy for me) I have to delete the resulting file. Getting this bug only for zooming in or out seems pretty bad to me and having the bug marked as "Medium Importance" seems wrong. Uninstalling Pinta anyway because this bug is here since 2015 and nothing was done. It's 2018 I don't think I should expect any changes anytime soon. Many thanks for your time, have a great day.

Revision history for this message
Stdedos (stdedos) wrote :

I am seeing that on Win10 1.7.0.236 zip version

Revision history for this message
Stdedos (stdedos) wrote :

Scrolling fixes it

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.