| Summary: | The screen is not well calibrated | ||
|---|---|---|---|
| Product: | Mageia | Reporter: | Bernard SIAUD <liste> |
| Component: | RPM Packages | Assignee: | Thierry Vignaud <thierry.vignaud> |
| Status: | RESOLVED WONTFIX | QA Contact: | |
| Severity: | normal | ||
| Priority: | Normal | CC: | marja11, sfietkonstantin |
| Version: | 1 | ||
| Target Milestone: | --- | ||
| Hardware: | i586 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Source RPM: | x11-driver-input-evtouch | CVE: | |
| Status comment: | |||
|
Description
Bernard SIAUD
2011-05-19 21:36:33 CEST
I rename your bug report to be clearer. What graphics driver are you using (Nouveau / Nvidia, Ati / Mesa / Fglrx, Intel ?) Here it's OK CC:
(none) =>
sfietkonstantin
Ahmad Samir
2011-07-02 04:16:48 CEST
Assignee:
bugsquad =>
tmb
Ahmad Samir
2011-07-02 04:19:38 CEST
Assignee:
tmb =>
bugsquad FWIW, xinput_calibrator is in Cauldron, it looks like Ubuntu (among other distros) are switching to it. I don't have a touch screen so I couldn't test it myself... I have a chipset intel with a eGalax TouchScreen. For calibrate : xinput set-prop 9 "Coordinate Transformation Matrix" 1.05 0 -0.03 0 1.07 -0.05 0 0 1 Rotation right : xrandr --output LVDS1 --rotate right xinput set-prop 12 "Evdev Axes Swap" 1 xinput set-prop 12 "Evdev Axis Inversion" 0 1 xinput set-prop 12 "Coordinate Transformation Matrix" 1.085 0 -0.06 0 1.05 -0.02 0 0 1 rotation left xrandr --output LVDS1 --rotate left xinput set-prop 12 "Evdev Axes Swap" 1 xinput set-prop 12 "Evdev Axis Inversion" 1 0 xinput set-prop 12 "Coordinate Transformation Matrix" 1.085 0 -0.02 0 1.05 -0.03 0 0 1 The problem is that the number after set-prop is not always the same. I can find it with xinput list : xinput list â¡ Virtual core pointer id=2 [master pointer (3)] â â³ Virtual core XTEST pointer id=4 [slave pointer (2)] â â³ eGalax Inc. USB TouchController id=9 [slave pointer (2)] â â³ eGalax Inc. USB TouchController id=10 [slave pointer (2)] â â³ Primax Kensington SlimBlade Presenter Media Mouse id=13 [slave pointer (2)] ⣠Virtual core keyboard id=3 [master keyboard (2)] â³ Virtual core XTEST keyboard id=5 [slave keyboard (3)] â³ Power Button id=6 [slave keyboard (3)] â³ Video Bus id=7 [slave keyboard (3)] â³ Power Button id=8 [slave keyboard (3)] â³ USB 2.0 Camera id=11 [slave keyboard (3)] â³ AT Translated Set 2 keyboard id=12 [slave keyboard (3)] â³ LITEON Technology USB Multimedia Keyboard id=14 [slave keyboard (3)] With this output the number is 9 xinput_calibrator is very good ! Now, I have no problem. Assigning to maintainer now that our maintainer's database has an entry for this package. Please assign back to bugsquad@mageia.org in case of a mistake from me. Version set to 1 as the bug was pre-Mageia 1. Version:
Cauldron =>
1 pinging. because nothing happened to this report since more than 3 months ago, and it still has the status NEW @ Thierry Please set status to ASSIGNED if you think this bug was assigned correctly. If for work flow reasons you can't do that, then please put OK on the whiteboard instead. CC:
(none) =>
marja11 (In reply to comment #4) > xinput_calibrator is very good ! Now, I have no problem. Unfortunately, it wasn't in Mdv 2010.2, so it can't be imported into Mageia 1 :( We have it in mga2 Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. 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 Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 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 Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. 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 Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad Mageia 1 changed to end-of-life (EOL) status on ''1st December''. Mageia 1 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 Mageia please feel free to click on "Version" change it against that version of Mageia and reopen this bug. Thank you for reporting this bug and we are sorry it could not be fixed. -- Mageia Bugsquad Status:
NEW =>
RESOLVED |