Bug 2811 - Wacom driver not working for Thinkpad X220 Tablet
Summary: Wacom driver not working for Thinkpad X220 Tablet
Status: RESOLVED WONTFIX
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 1
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: Thomas Backlund
QA Contact:
URL: https://forums.mageia.org/en/viewtopi...
Whiteboard:
Keywords: PATCH
Depends on:
Blocks:
 
Reported: 2011-09-22 20:32 CEST by Wim Coulier
Modified: 2012-12-02 14:32 CET (History)
5 users (show)

See Also:
Source RPM: kernel
CVE:
Status comment:


Attachments

Description Wim Coulier 2011-09-22 20:32:04 CEST
The Wacom driver does not work for a Thinkpad X220 Tablet PC. Apparently a patch is required, see
https://bbs.archlinux.org/viewtopic.php?id=119332
and
https://bugzilla.redhat.com/show_bug.cgi?id=708307

Without this, running Mageia on this Tablet PC reduces its functionality to that of a standard laptop.
Manuel Hiebel 2011-09-24 01:04:01 CEST

CC: (none) => thierry.vignaud, tmb

Manuel Hiebel 2011-09-24 01:04:13 CEST

Keywords: (none) => PATCH

Comment 1 Thierry Vignaud 2011-09-24 21:14:11 CEST
Wrong package

Assignee: bugsquad => tmb
Source RPM: (none) => kernel

Comment 2 Thomas Backlund 2011-09-25 11:10:04 CEST
There is now a 2.6.38.8-5.1.mga to test at:

http://tmb.mine.nu/Mageia/1/bugs/2811/
http://tmb2.mine.nu/Mageia/1/bugs/2811/
Comment 3 Wim Coulier 2011-09-25 21:40:02 CEST
I tested that new kernel and had only partial success. When the package is installed, there is touch feedback, but the pointer goes to fast compared to the finger, so that it ends up at another spot then the finger. A double click on th screen seems to have the effect of a left mouse button. No pen input is possible at all.
When I tried to configure the touchscreen in << KDE System Settings / Input Devices / Graphic Tablet >> the x-server crashed and I got back at the login screen. From this moment on, I was not able anymore to login (each time a crash of the x-server before log-in completes). Fortunately with the unpatched kernel I can still log in. I can still log in into the patched kernel as guest, but then also, each time I try to configure the wacom touch screen, the x-server crashes.

So it is going into the right direction, but it does not work yet.
Comment 4 Thomas Backlund 2011-09-25 22:27:54 CEST
You need support in the x11 driver too...

I have just submitted: x11-driver-input-wacom-0.10.11-3.1.mga1

to core/updates_testing wich adds support for the tablet with id E6.

Please test it out and let me know if it helps.
Comment 5 Wim Coulier 2011-09-27 20:16:46 CEST
I installed the x11-driver-input-wacom-0.10.11-3.1.mga1. That did not make any difference. Still not able to log in with my normal user. If I log in as xguest and try to configure the touchscreen, the same thing happens:the x-server crashes and I get back at the loginscreen.

Anything I can do to help figure out what goes wrong?
Comment 6 Wim Coulier 2011-10-08 08:50:56 CEST
Is there any information I can provide that may help to tackle the problem?
Comment 7 Wim Coulier 2011-12-28 11:29:42 CET
Partial success! I reinstalled Mageia and installed your x11-driver-input-wacom-0.10.11-3.1.mga1 again this time with the latest kernel (2.6.38.8). Now it does work and I am able to configure the touchscreen in << KDE System Settings / Input Devices / Graphic Tablet >>. So that package is good (don't know how my previous install got screwed). 
However my touchscreen is still not yet really useful: 
* the input does not rotate with the screen, leading to the pointer going to a point mirrored vs. the center instead of where you point (type of mirroring being dependent on the rotation angle).
* stylus input works completely, but touch input does not allow me to select anything (double tap does not do anything), so impossible to scroll a scrollbar for instance. This makes touch input more or less useless, so only stylus input really works.
* there is no on screen keyboard appearing when I go in a text field
Comment 8 Marja Van Waes 2012-04-26 22:11:57 CEST
Pinging, because nothing has happened with this report for more than 3 months, it still has the status NEW or REOPENED.

@ Thomas

Please set status to ASSIGNED if you think this bug was assigned correctly.

CC: (none) => marja11

Valdemar Boersting 2012-05-27 11:06:28 CEST

CC: (none) => valdemar

Comment 9 Marja Van Waes 2012-07-06 15:05:09 CEST
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
Comment 10 Samuel Verschelde 2012-08-26 14:43:29 CEST
Thomas (tmb), what about this package in updates_testing, is it still work in progress or must we remove it?

CC: (none) => qa-bugs

Comment 11 Manuel Hiebel 2012-11-05 16:53:03 CET
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
Comment 12 Manuel Hiebel 2012-12-02 14:32:27 CET
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
Resolution: (none) => WONTFIX


Note You need to log in before you can comment on or make changes to this bug.