Bug 1159662
| Summary: | touchscreen miscalibrated when using additional monitor | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Stefan Seefeld <stefan> | ||||
| Component: | plasma-desktop | Assignee: | KDE SIG <kde-sig> | ||||
| Status: | CLOSED EOL | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 24 | CC: | greg.b.redhat, hdegoede, jgrulich, jreznik, kde-sig, kevin, ltinkl, mbriza, me, ovasik, peter.hutterer, rdieter, smparrish, stefan, than | ||||
| Target Milestone: | --- | Keywords: | Reopened, Triaged | ||||
| Target Release: | --- | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2017-08-08 11:49:06 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
|
Description
Stefan Seefeld
2014-11-02 21:30:57 UTC
run xinput list-props on the touchscreen device please and attach the output here. what desktop environment are you using? any special configuration files that we should be aware of? Created attachment 953364 [details]
output of `xinput list-props 13`
Please find attached the requested output.
I'm running KDE, and I'm not aware of any special configuration.
(This is a Precision 3800 with a display resolution of 3200x1800. The external monitor is using 1920x1200.)
This is a KDE problem. By default, absolute devices such as touchscreens map across all monitors in X. it's up to the desktop environment to set the correct mapping for each touchscreen. Not sure what component in KDE is really responsible for that, reassigning to kdesettings in the hope that's correct enough. sorry guys. If KDE doesn't currently do this, here's a manual workaround: https://wiki.archlinux.org/index.php/Calibrating_Touchscreen xinput in F20 and newer also provides the xinput map-to-output function that makes setting the matrix a lot easier (just check the man page). This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '20'. 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 20 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. I can confirm that this issue is still present with Fedora 21 KDE. The workaround Peter linked to does work, however. Someone with permission will need to update the Version on this bug id from 20 to 21. And it's still present in Fedora 22, too, FWIW. triaging to plasma-desktop (where kcm_touchpad lives). This probably ought to get filed upstream @ bugs.kde.org, preferably someone with the affected hardware. Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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 is still present on Fedora 25 KDE. I use a shell script to work around the problem. This message is a reminder that Fedora 24 is nearing its end of life. Approximately 2 (two) weeks from now Fedora will stop maintaining and issuing updates for Fedora 24. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '24'. 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 24 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 24 changed to end-of-life (EOL) status on 2017-08-08. Fedora 24 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. |