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 585493 - GtkTreeView scrolling test suite should enforce default theme and font.
GtkTreeView scrolling test suite should enforce default theme and font.
Status: RESOLVED OBSOLETE
Product: gtk+
Classification: Platform
Component: Widget: GtkTreeView
2.16.x
Other Linux
: Normal normal
: ---
Assigned To: gtktreeview-bugs
gtktreeview-bugs
Depends on:
Blocks:
 
 
Reported: 2009-06-11 21:27 UTC by Gilles Dartiguelongue
Modified: 2018-02-10 03:34 UTC
See Also:
GNOME target: ---
GNOME version: 2.25/2.26


Attachments
treeview-scrolling-rapport-anomalie.txt (7.60 KB, text/plain)
2009-06-11 21:28 UTC, Gilles Dartiguelongue
Details

Description Gilles Dartiguelongue 2009-06-11 21:27:39 UTC
Summary says it all:

  /treeview/scrolling/before-constant-path-999-align-0.0:              OK
  /treeview/scrolling/before-constant-path-0-align-0.5:                OK
  /treeview/scrolling/before-constant-path-2-align-0.5:                OK
  /treeview/scrolling/before-constant-path-5-align-0.5:                **
ERROR:treeview-scrolling.c:404:test_position: assertion failed: (test_position_with_align (tree_view, pos, rect.y, row_start, rect.height, row_align))


attaching bug-buddy report in a moment.
Comment 1 Gilles Dartiguelongue 2009-06-11 21:28:24 UTC
Created attachment 136367 [details]
treeview-scrolling-rapport-anomalie.txt
Comment 2 Kristian Rietveld 2009-07-30 12:41:05 UTC
It does succeed for me.  I suspect that the scrolling tests are very sensitive to theming sensitive.  My development branch of GTK+ runs the default (boring) theme.

The test should be changed to actually enforce usage of the default theme and font so that it passes on all configurations.  Changing the subject to say so.
Comment 3 Matthias Clasen 2018-02-10 03:34:51 UTC
We're moving to gitlab! As part of this move, we are closing bugs that haven't seen activity in more than 5 years. If this issue is still imporant to you and
still relevant with GTK+ 3.22 or master, please consider creating a gitlab issue
for it.