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 748244 - "Natural" scroll direction is not honored under X
"Natural" scroll direction is not honored under X
Status: RESOLVED DUPLICATE of bug 674716
Product: gtk+
Classification: Platform
Component: Backend: X11
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: meld-maint
meld-maint
Depends on:
Blocks:
 
 
Reported: 2015-04-21 12:09 UTC by Balint Reczey
Modified: 2016-01-30 17:24 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Balint Reczey 2015-04-21 12:09:56 UTC 
From Debian's BTS:

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=783062

Package: meld
Version: 3.12.1-2

I have setup X to use the "natural" scroll direction
(moving the document, not the scroll bar). This works
for all Xwindow clients (firefox, claws, okular, xterm,
emacs, whatever) except for Jessie's meld.

If I use meld on an old remote Wheezy host, then there
is no such problem.

It is *highly* painful to have the old behavior back for
a single app. Please fix

Thanx in advance
Harri
Comment 1 Kai Willadsen 2015-04-21 21:32:54 UTC 
None of the apps listed as working are GTK+ apps, and Meld doesn't do anything that would alter the scroll direction, so I'm almost certain that this is either a GTK+ bug or a setup problem.

Do any GTK+ applications work as expected?

I'd guess that the reason it worked on the Wheezy host is that it was probably running Meld 1.x, which used GTK+ 2 not GTK+ 3.
Comment 2 Balint Reczey 2015-05-05 17:20:10 UTC 
Thanks Kai,
I have checked gedit and it is failing, too.

This seems to be the problem:
https://bbs.archlinux.org/viewtopic.php?id=179667

I'm reassigning the issue to gtk+ here and in Debian's BTS.
Comment 3 Matthias Clasen 2016-01-30 17:24:47 UTC 

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