Bug 788632
| Summary: | all scrolled windows jump up one page after you middle click a link | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Richard W.M. Jones <rjones> |
| Component: | xorg-x11-server | Assignee: | Peter Hutterer <peter.hutterer> |
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 22 | CC: | gecko-bugs-nobody, peter.hutterer, raphael.brandis, rjones, xgl-maint |
| Target Milestone: | --- | Keywords: | Reopened |
| Target Release: | --- | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2015-08-03 09:37:40 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Richard W.M. Jones
2012-02-08 16:36:11 UTC
This happens in the terminal app too, so I guess it's not Firefox. Not sure what to assign this bug to. most likely https://bugs.freedesktop.org/show_bug.cgi?id=45611, not sure of a fix yet. Yes it does look similar to that bug report. I should note that this is a Thinkpad T510 which has two pointer devices; and I am touching the middle button on one device then using the trackpad "middle" on the other device. definitely the same bug then, happens when the phys. device is switched. xorg-x11-server-1.11.99.901-4.20120124.fc17 is available in koji. http://koji.fedoraproject.org/koji/taskinfo?taskID=3779934 (In reply to comment #5) > xorg-x11-server-1.11.99.901-4.20120124.fc17 is available in koji. > > http://koji.fedoraproject.org/koji/taskinfo?taskID=3779934 Thank you. I have installed this and confirmed that it fixes the bug. This bug appears to have been reported against 'rawhide' during the Fedora 19 development cycle. Changing version to '19'. (As we did not run this process for some time, it could affect also pre-Fedora 19 development cycle bugs. We are very sorry. It will help us with cleanup during Fedora 19 End Of Life. Thank you.) More information and reason for this action is here: https://fedoraproject.org/wiki/BugZappers/HouseKeeping/Fedora19 This message is a notice that Fedora 19 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 19. It is Fedora's policy to close all bug reports from releases that are no longer maintained. Approximately 4 (four) weeks from now this bug will be closed as EOL if it remains open with a Fedora 'version' of '19'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 19 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. Fedora 19 changed to end-of-life (EOL) status on 2015-01-06. Fedora 19 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed. This bug was previously fixed, but has reappeared for me since I upgraded to: $ rpm -qa | grep xorg-x11 | sort xorg-x11-apps-7.7-13.fc22.x86_64 xorg-x11-drv-ati-7.5.0-3.fc22.x86_64 xorg-x11-drv-evdev-2.9.2-1.fc22.x86_64 xorg-x11-drv-fbdev-0.4.3-20.fc22.x86_64 xorg-x11-drv-intel-2.99.917-12.20150615.fc22.x86_64 xorg-x11-drv-nouveau-1.0.11-2.fc22.x86_64 xorg-x11-drv-openchrome-0.3.3-14.fc22.x86_64 xorg-x11-drv-qxl-0.1.3-2.fc22.x86_64 xorg-x11-drv-synaptics-1.8.2-2.fc22.x86_64 xorg-x11-drv-vesa-2.3.2-20.fc22.x86_64 xorg-x11-drv-vmmouse-13.0.99-1.fc22.x86_64 xorg-x11-drv-vmware-13.0.2-8.20150211git8f0cf7c.fc22.x86_64 xorg-x11-drv-wacom-0.29.0-2.fc22.x86_64 xorg-x11-fonts-ISO8859-1-100dpi-7.5-14.fc22.noarch xorg-x11-fonts-ISO8859-1-75dpi-7.5-14.fc22.noarch xorg-x11-fonts-misc-7.5-14.fc22.noarch xorg-x11-fonts-Type1-7.5-14.fc22.noarch xorg-x11-font-utils-7.5-28.fc22.x86_64 xorg-x11-proto-devel-7.7-12.fc21.noarch xorg-x11-resutils-7.5-11.fc22.x86_64 xorg-x11-server-common-1.17.2-1.fc22.x86_64 xorg-x11-server-utils-7.7-15.fc22.x86_64 xorg-x11-server-Xorg-1.17.2-1.fc22.x86_64 xorg-x11-server-Xwayland-1.17.2-1.fc22.x86_64 xorg-x11-twm-1.0.9-1.fc22.x86_64 xorg-x11-utils-7.5-19.fc22.x86_64 xorg-x11-xauth-1.0.9-2.fc22.x86_64 xorg-x11-xbitmaps-1.1.1-7.fc21.noarch xorg-x11-xinit-1.3.4-8.fc22.x86_64 xorg-x11-xkb-utils-7.7-13.fc22.x86_64 Richard: most likely in the xorg-x11-server package, do you know the last known working version? From the dnf.log files, it appears the last working version
was xorg-x11-server-common-1.16.2.901-1.fc21.x86_64
FWIW the previous WORKING versions of all xorg packages were:
# grep '^Jul 15.*Cleanup' dnf.rpm.log-20150716 | grep xorg-x11 | sort | awk '{print $6}'
xorg-x11-apps-7.7-12.fc21.x86_64
xorg-x11-utils-7.5-16.fc21.x86_64
xorg-x11-drv-intel-2.99.916-3.20141117.fc21.x86_64
xorg-x11-drv-wacom-0.25.0-2.fc21.x86_64
xorg-x11-drv-openchrome-0.3.3-12.fc21.x86_64
xorg-x11-twm-1:1.0.8-2.fc21.x86_64
xorg-x11-drv-evdev-2.9.0-3.fc21.x86_64
xorg-x11-drv-synaptics-1.8.0-9.fc21.x86_64
xorg-x11-drv-ati-7.5.0-1.fc21.x86_64
xorg-x11-drv-nouveau-1:1.0.11-1.fc21.x86_64
xorg-x11-drv-vmware-13.0.2-5.20140613git82c9b0c.fc21.x86_64
xorg-x11-resutils-7.5-11.fc21.x86_64
xorg-x11-drv-qxl-0.1.2-1.fc21.x86_64
xorg-x11-fonts-Type1-7.5-14.fc21.noarch
xorg-x11-fonts-ISO8859-1-100dpi-7.5-14.fc21.noarch
xorg-x11-fonts-misc-7.5-14.fc21.noarch
xorg-x11-fonts-ISO8859-1-75dpi-7.5-14.fc21.noarch
xorg-x11-xinit-1.3.4-2.fc21.x86_64
xorg-x11-server-utils-7.7-10.fc21.x86_64
xorg-x11-xauth-1:1.0.9-2.fc21.x86_64
xorg-x11-font-utils-1:7.5-25.fc21.x86_64
xorg-x11-drv-fbdev-0.4.3-19.fc21.x86_64
xorg-x11-drv-vesa-2.3.2-19.fc21.x86_64
xorg-x11-drv-vmmouse-13.0.0-13.fc21.x86_64
xorg-x11-server-Xorg-1.16.2.901-1.fc21.x86_64
xorg-x11-server-common-1.16.2.901-1.fc21.x86_64
xorg-x11-xkb-utils-7.7-12.fc21.x86_64
The hardware is a Lenovo X230, which has two separate mouse-like devices: SynPS/2 Synaptics Touchpad TPPS/2 IBM Trackpoint reproducible on my x220 here, introduced between xorg-x11-server-common-1.17.1-11.fc22 and 1.17.2-1.fc22 do you still see this with gtk3-3.16.6-1.fc22.x86_64? Could be a dupe of bug 1245247 Indeed it is fixed by updating gtk3. Thanks. I will close this bug (not mark it as a dupe) since it records the earlier bug which was in the X server. |