After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 675529 - Visual garbage/unresponsiveness when scrolling via Spacebar
Visual garbage/unresponsiveness when scrolling via Spacebar
Status: RESOLVED DUPLICATE of bug 674051
Product: GIMP
Classification: Other
Component: User Interface
2.8.0
Other Windows
: Normal normal
: ---
Assigned To: GIMP Bugs
GIMP Bugs
Depends on:
Blocks:
 
 
Reported: 2012-05-05 19:41 UTC by strata_ranger
Modified: 2012-05-06 02:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Graphical artifacts/slow responsiveness encountered when Spacebar+mousing around an image's edges (89.56 KB, image/png)
2012-05-05 19:41 UTC, strata_ranger
Details

Description strata_ranger 2012-05-05 19:41:13 UTC
Created attachment 213523 [details]
Graphical artifacts/slow responsiveness encountered when Spacebar+mousing around an image's edges

Let me know if this is related to bug #674051.

Steps to reproduce:

1 - Create any new image of a convenient size.
2 - Hold Spacebar to activate scrolling mode and begin moving the mouse in various directions, scrolling both on and off the edges of the image.
3 - GIMP starts showing graphical artifacts and GUI responsiveness becomes very sluggish.

I haven't actually experienced any crashes yet (GIMP seems to recover in a second with no problems), but the slow responsiveness is definitely an issue.

This behavior does NOT seem to occur when scrolling via mousewheel, or when scrolling fully within the image edges - only when scrolling around the image edges (which happens to me a lot because that's the only context where mousewheel scrolling alone won't work).
Comment 1 Michael Schumacher 2012-05-05 23:50:24 UTC
Does this happen with 2.8.0 as well?
Comment 2 strata_ranger 2012-05-06 02:08:40 UTC
Yes, still present in 2.8.0.  It only occurs when panning quickly - e.g. before the current refresh actually completes.

(And on closer examination, I think this really is duplicating #674051)
Comment 3 strata_ranger 2012-05-06 02:09:28 UTC

*** This bug has been marked as a duplicate of bug 674051 ***