Your message dated Mon, 13 Nov 2017 11:26:04 +0000
with message-id <20171113112604.sp7zyzo5z5alu...@perpetual.pseudorandom.co.uk>
and subject line Re: Bug#792199: libgtk-3-0: Scroll down behaviour incorrect
has caused the Debian Bug report #792199,
regarding libgtk-3-0: Scroll down behaviour incorrect
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
792199: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=792199
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Package: libgtk-3-0
Version: 3.16.5-1
Severity: normal
* What led up to the situation?
Apparently use of applications which use GTK3, e.g. Nautilus
* What exactly did you do (or not do) that was effective (or
ineffective)?
Click below thumb in vertical scrollbar or move mouse scroll wheel downward
* What was the outcome of this action?
Window immediately displayed end of content, thumb moved to bottom of scrollbar
No corresponding problem in upward direction
* What outcome did you expect instead?
Limited downward movement of window content
-- System Information:
Debian Release: stretch/sid
APT prefers unstable
APT policy: (500, 'unstable'), (500, 'testing')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 4.0.0-2-amd64 (SMP w/2 CPU cores)
Locale: LANG=en_GB.UTF-8, LC_CTYPE=en_GB.UTF-8 (charmap=UTF-8)
Shell: /bin/sh linked to /bin/dash
Init: systemd (via /run/systemd/system)
Versions of packages libgtk-3-0 depends on:
ii libatk-bridge2.0-0 2.16.0-1
ii libatk1.0-0 2.16.0-2
ii libc6 2.19-19
ii libcairo-gobject2 1.14.2-2
ii libcairo2 1.14.2-2
ii libcolord2 1.2.1-1+b2
ii libcups2 2.0.3-6
ii libepoxy0 1.2-1
ii libfontconfig1 2.11.0-6.3
ii libfreetype6 2.5.2-4
ii libgdk-pixbuf2.0-0 2.31.4-2
ii libglib2.0-0 2.44.1-1.1
ii libgtk-3-common 3.16.5-1
ii libjson-glib-1.0-0 1.0.4-1
ii libpango-1.0-0 1.36.8-3
ii libpangocairo-1.0-0 1.36.8-3
ii libpangoft2-1.0-0 1.36.8-3
ii librest-0.7-0 0.7.93-1
ii libsoup2.4-1 2.50.0-2
ii libwayland-client0 1.8.1-1
ii libwayland-cursor0 1.8.1-1
ii libwayland-egl1-mesa [libwayland-egl1] 10.5.9-2
ii libx11-6 2:1.6.3-1
ii libxcomposite1 1:0.4.4-1
ii libxcursor1 1:1.1.14-1+b1
ii libxdamage1 1:1.1.4-2+b1
ii libxext6 2:1.3.3-1
ii libxfixes3 1:5.0.1-2+b2
ii libxi6 2:1.7.4-1+b2
ii libxinerama1 2:1.1.3-1+b1
ii libxkbcommon0 0.5.0-1
ii libxml2 2.9.2+dfsg1-3
ii libxrandr2 2:1.4.2-1+b1
ii shared-mime-info 1.3-1
Versions of packages libgtk-3-0 recommends:
ii hicolor-icon-theme 0.13-1
ii libgtk-3-bin 3.16.5-1
Versions of packages libgtk-3-0 suggests:
ii gvfs 1.24.1-2+b2
ii librsvg2-common 2.40.9-2
-- no debconf information
--- End Message ---
--- Begin Message ---
Version: 3.22.11-1
On Mon, 30 Oct 2017 at 19:21:20 +0000, Simon McVittie wrote:
> This is believed to have been fixed in later GTK+ 3.16.x releases, so
> should be fixed in Debian 9 'stretch', the current stable release.
This seems to work as intended in stable.
smcv
--- End Message ---
