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 789412 - problem with the scrollbar
problem with the scrollbar
Status: RESOLVED FIXED
Product: Gnumeric
Classification: Applications
Component: GUI
1.12.x
Other Linux
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
: 789816 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2017-10-24 14:33 UTC by Frédéric Parrenin
Modified: 2017-11-10 23:11 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
.png screenshot to illustrate the problem (144.14 KB, image/png)
2017-10-24 14:33 UTC, Frédéric Parrenin 		  Details
Proposed patch (895 bytes, patch)
2017-11-10 16:36 UTC, Jean Bréfort 		none Details | Review

Description Frédéric Parrenin 2017-10-24 14:33:29 UTC 
Created attachment 362189 [details]
.png screenshot to illustrate the problem

I am running the stock gnumeric 1.12.32 on debian 9.
Steps to reproduce:
- create a 1000 vertical vector with row number.
- then go to the bottom of the vector using CTRL+DOWN.
- then move the mouse to move the scrollbar to the top
=> the view moves to the top, but the scrollbar stays at the bottom.
See attached screenshot.
Comment 1 Jean Bréfort 2017-10-29 08:23:56 UTC 
I'm seeing that too. I'm unable to understand why it does not work anymore. Loks like a new Gtk+ bug (or feature).
Comment 2 Andreas J. Guelzow 2017-11-04 18:45:20 UTC 
*** Bug 789816 has been marked as a duplicate of this bug. ***
Comment 3 Andreas J. Guelzow 2017-11-04 18:54:36 UTC 
Looking at known GTK bugs, bug #765410 seems to be a candidate to explain this. Considering how long they have been talking about that bug (well over a year) it does not breaking many applications is consider a problem.
Comment 4 Morten Welinder 2017-11-09 02:05:20 UTC 
What version of gtk+ is in use?
Comment 5 Jean Bréfort 2017-11-09 06:36:53 UTC 
3.22.25 for me, but seems any >= 3.20 presents the issue.
Comment 6 Jean Bréfort 2017-11-10 16:36:19 UTC 
Created attachment 363363 [details] [review]
Proposed patch
Comment 7 Morten Welinder 2017-11-10 23:11:49 UTC 
This problem has been fixed in our software repository. The fix will go into the next software release. Once that release is available, you may want to check for a software upgrade provided by your Linux distribution.


Note: "fixed" means that a workaround has been added.  The problem remains
in gtk+ and it is possible that it will show itself elsewhere.