touchscreen do not work after suspend/resume
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
xinput (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
My laptop (Thinkpad X200T with multi-touch screen) installed the 'Trusty' ubuntu 14.04 (64bits), touchscreen works well after cold boot! But after suspend/resume, touchsreen do not response. Execute 'xsetwacom --list' in terminal, there is nothing, both 'wacom touch' and 'wacom stylus' are gone. I must logout and relogin or reboot, the touchscreen can be normal again.
By the way, the same problem happens in the 'Saucy' ubuntu 13.10 (64bits). But in 'Raring' ubuntu 13.04 (64bits), this problem does no exist, touchscreen WORKS WELL after suspend/resume.
This Thinkpad X200T updated the newest BIOS, and keep ubuntu OS up to date.
Please fix this bug, because 14.04 is a very important version for touchscreen devices, and i think 'suspend/resume' function is important too. Thanks!
-------
Feb 4, 2014 update
Oh I'm sorry, I find a new change for this bug that I never noticed before.
I keep Trusty ubuntu up to date(Feb 4, 2014). When the OS's first boot from cold boot, touchscreen works well. Then if suspend/resume for the first time, touchscreen will not response. At this moment, logout and relogin, touchscreen works well again even after suspend/resume.
Simply put, touchscreen do not response only after the first suspend/resume since a cold boot. Once the OS logout and relogin, touchscreen will work well after any suspend/resume. The key point is that the OS must logout and relogin for at least one time.
Always keep 'Trusty' ubuntu OS updated.
that's a strange bug
description: | updated |
description: | updated |
tags: |
added: suspend touchscreen wacom removed: bot-comment |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Thank you for taking the time to report this bug and helping to make Ubuntu better. It seems that your bug report is not filed about a specific source package though, rather it is just filed against Ubuntu in general. It is important that bug reports be filed about source packages so that people interested in the package can find the bugs about it. You can find some hints about determining what package your bug might be about at https:/ /wiki.ubuntu. com/Bugs/ FindRightPackag e. You might also ask for help in the #ubuntu-bugs irc channel on Freenode.
To change the source package that this bug is filed about visit https:/ /bugs.launchpad .net/ubuntu/ +bug/1275416/ +editstatus and add the package name in the text box next to the word Package.
[This is an automated message. I apologize if it reached you inappropriately; please just reply to this message indicating so.]