Bug 1048516 - Touchscreen does not work after update
Summary: Touchscreen does not work after update
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: xorg-x11-drv-wacom
Version: 20
Hardware: x86_64
OS: Linux
unspecified
urgent
Target Milestone: ---
Assignee: Peter Hutterer
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-01-04 20:09 UTC by a.kassiteridis
Modified: 2015-06-29 14:10 UTC (History)
7 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-29 14:10:27 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
Diagnostic output fresh install/post-upgrade (20.08 KB, application/x-bzip)
2014-01-15 10:59 UTC, Peter Ludikovsky
no flags Details

Description a.kassiteridis 2014-01-04 20:09:31 UTC
Description of problem:
After the last update of packages (3 of January evening CET), after wake-up (resume after sleep) the touchscreen + wacom do not work. They are not even displayed under settings/wacom. I am not sure about the component/package.

Laptop model: Lenovo Thinkpad x201 tablet i7 with multitouch+wacom.

Version-Release number of selected component (if applicable):


How reproducible:
Simply make the system sleep and then wake it up again.

Steps to Reproduce:
1. Sleep
2. Resume
3. no touch nor digitizer

Actual results:


Expected results:


Additional info:
Until this update everything has been working perfectly (fedora 18, 19 and now 20).

Comment 1 Peter Hutterer 2014-01-06 06:35:54 UTC
please attach the evemu-describe output from your device, /proc/bus/input/devices and your xorg.log and the yum history of that update

Comment 2 nineff 2014-01-14 17:54:27 UTC


Hi!

I have the same hardware and the same problem. Unfortunately, I don't know if the problem existed since the fresh install of Fedora 20 or if an update broke it. However, here are the other requested outputs:

lshw (after initial start (device working as intended)):
http://pastebin.com/aXccnTQN

evemu-describe  (after initial start (device working as intended)):
http://pastebin.com/hhjmrqzN

evemu-describe (after sleep and wakeup):
http://pastebin.com/Rw9FCgUD

/proc/bus/input/devices (after initial start (device working as intended)):
http://pastebin.com/9zkj1jJe

/proc/bus/input/devices (after sleep and wakeup):
http://pastebin.com/b1Tb9vBX

xorg.log:
http://pastebin.com/ELZkvj9s

Please let me know, if you need any other logs/information.
regards, Nikolai Neff

Comment 3 Peter Ludikovsky 2014-01-15 08:00:34 UTC
Similar error using an Lenovo X200 Tablet. Pen input worked fine right after a fresh install, not working after installing updates as of 2014-01-15.

Currently re-installing in order to create appropriate diffs.

Also, somewhat similar problem (I think) in Bug 1046912 (https://bugzilla.redhat.com/show_bug.cgi?id=1046912)

Comment 4 Peter Ludikovsky 2014-01-15 10:59:18 UTC
Created attachment 850438 [details]
Diagnostic output fresh install/post-upgrade

Contents of pre were taken right after a fresh install of Fedora 20 x86_64 (XFCE Desktop)
Contents of post were taken after an update of all packages as available on 2014-01-15
Additional packages installed:
* deltarpm
* yum-plugins-fastestmirror
* yum-plugins-fs-snapshot
* evemu
* lshw

Comment 5 Peter Ludikovsky 2014-01-15 14:28:20 UTC
Downgrade of xorg-x11-drv-wacom from 0.23-2 to 0.23-1 has the pen functional again.

Comment 6 Peter Hutterer 2014-01-17 01:11:20 UTC

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

Comment 7 Peter Hutterer 2014-01-17 02:58:20 UTC
I may have been to quick closing this as duplicate. Fix for the suspend/resume issue coming up in a second.

Comment 8 a.kassiteridis 2014-01-18 18:49:14 UTC
I do not think this is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=1048516 !!!

the steps to reproduce are not the same and also the wacom model. I am talking here also about touch (multitouch with finger)!!!.

(In reply to Peter Hutterer from comment #7)
> I may have been to quick closing this as duplicate. Fix for the
> suspend/resume issue coming up in a second.

Comment 9 nineff 2014-01-23 09:22:21 UTC
I did test this with xorg-x11-drv-wacom-0.23.0-4.fc20 from updates-testing and it seems to have fixed the issue for me. It only takes about 3 to 5 seconds after waking up before the touch and stylus input react, which is fine with me.

Comment 10 a.kassiteridis 2014-01-30 16:34:12 UTC
Will someone ever fix this bug?

Comment 11 Peter Hutterer 2014-01-30 23:04:10 UTC
it's fixed. xorg-x11-drv-wacom-0.23.0-4.fc20. please let me know what the remaining issue is.

Note that this is the suspend/resume bug, the other bug is different and this one was mistakenly closed as duplicate.

Comment 12 a.kassiteridis 2014-01-31 07:50:58 UTC
Yes I know that this is the resume bug. I installed -4 an there is a lag of 5 sec. Could you fix it? thank you

Comment 13 Peter Hutterer 2014-02-05 05:48:48 UTC
Is there anything in the journal explaining why it is delayed? This could just be the device or the serial port initialization taking its time.

systemctl status wacom-inputattach

Comment 14 rendsvig 2014-12-12 22:18:42 UTC
I seem to be experienceing a similar problem on Fedora 21, on a installation from two days ago. It's a fresh install, but I've been updating as updates came.

Comment 15 rendsvig 2014-12-12 22:25:12 UTC
My apologies for the additional comment: I'm on a ThinkPad X1 Carbon 2Gen.

Comment 16 Jonathan Reeve 2014-12-14 18:48:12 UTC
I'm having this same problem on my Lenovo Yoga 2 11" convertible laptop. I can manually reenable the touchscreen with `xinput enable 10` (since `10` is the ID of my touchscreen), but doing this manually on every wake is annoying.

Comment 17 Peter Hutterer 2014-12-22 05:15:39 UTC
the disabled touchscreen is a gnome bug, see bug 1173849

Comment 18 Fedora End Of Life 2015-05-29 10:19:58 UTC
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.

Comment 19 Fedora End Of Life 2015-06-29 14:10:27 UTC
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.


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