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 777995 - Scrollbars always drawn at leftmost/uppermost spot
Scrollbars always drawn at leftmost/uppermost spot
Status: RESOLVED OBSOLETE
Product: Gnumeric
Classification: Applications
Component: GUI
1.12.x
Other Mac OS
: Normal normal
: ---
Assigned To: Jody Goldberg
Jody Goldberg
Depends on:
Blocks:
 
 
Reported: 2017-01-31 17:54 UTC by mike_nahas
Modified: 2018-05-22 14:26 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description mike_nahas 2017-01-31 17:54:05 UTC
Loaded large CSV (16000 rows, 105 columns) and scrollbars worked in odd ways.

The scrollbar cursors were always drawn at the leftmost or topmost spot.  But if I clicked in the middle of the scrollbar's track, the display area would scroll in the direction of the click, but the scrollbar cursor itself would stay put.  Likewise if I tried to drag the scrollbar cursor - the display area would scroll but the cursor would stay put.  So, it feels like the scroll bar is not being drawn in the right spot.

Running version 1.12.33, which was compiled with homebrew.
OSX version 10.10.5
XQuartz 2.7.11 (xorg-server 1.18.4)



output from "brew doctor" below:

alonso:~ mike$ brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: The filesystem on / appears to be case-sensitive.
The default macOS filesystem is case-insensitive. Please report any apparent problems.

Warning: Unbrewed dylibs were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected dylibs:
  /usr/local/lib/libtcl8.6.dylib
  /usr/local/lib/libtk8.6.dylib

Warning: Unbrewed header files were found in /usr/local/include.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected header files:
  /usr/local/include/fakemysql.h
  /usr/local/include/fakepq.h
  /usr/local/include/fakesql.h
  /usr/local/include/itcl.h
  /usr/local/include/itcl2TclOO.h
  /usr/local/include/itclDecls.h
  /usr/local/include/itclInt.h
  /usr/local/include/itclIntDecls.h
  /usr/local/include/itclMigrate2TclCore.h
  /usr/local/include/itclTclIntStubsFcn.h
  /usr/local/include/mysqlStubs.h
  /usr/local/include/odbcStubs.h
  /usr/local/include/pqStubs.h
  /usr/local/include/tcl.h
  /usr/local/include/tclDecls.h
  /usr/local/include/tclOO.h
  /usr/local/include/tclOODecls.h
  /usr/local/include/tclPlatDecls.h
  /usr/local/include/tclThread.h
  /usr/local/include/tclTomMath.h
  /usr/local/include/tclTomMathDecls.h
  /usr/local/include/tdbc.h
  /usr/local/include/tdbcDecls.h
  /usr/local/include/tdbcInt.h
  /usr/local/include/tk.h
  /usr/local/include/tkDecls.h
  /usr/local/include/tkPlatDecls.h

Warning: Unbrewed .pc files were found in /usr/local/lib/pkgconfig.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected .pc files:
  /usr/local/lib/pkgconfig/tcl.pc
  /usr/local/lib/pkgconfig/tk.pc

Warning: Unbrewed static libraries were found in /usr/local/lib.
If you didn't put them there on purpose they could cause problems when
building Homebrew formulae, and may need to be deleted.

Unexpected static libraries:
  /usr/local/lib/libtclstub8.6.a
  /usr/local/lib/libtkstub8.6.a
Comment 1 Morten Welinder 2017-01-31 18:15:08 UTC
On MacOS you are pretty much on your own.
Comment 2 Jean Bréfort 2017-02-02 08:38:07 UTC
I'm seeing that too with gtk+-3.22.7 on linux. Not sure if it is a new Gtk+ bug or a new feature.
Comment 3 Jean Bréfort 2017-02-02 08:44:59 UTC
Might be Gtk+ bug #765410 actually.
Comment 4 Morten Welinder 2017-02-03 20:44:10 UTC
> Might be Gtk+ bug #765410 actually.

Agreed.

> Not sure if it is a new Gtk+ bug or a new feature.

For Gtk+, the distinction is not clear to me anymore.
Comment 5 GNOME Infrastructure Team 2018-05-22 14:26:55 UTC
-- GitLab Migration Automatic Message --

This bug has been migrated to GNOME's GitLab instance and has been closed from further activity.

You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnumeric/issues/309.