Ask Your Question
1

How can I get my touch screen to work after waking from suspend?

asked 2014-11-28 10:53:37 -0500

jon.reeve gravatar image

After a recent update, my touch screen no longer works after waking from suspend. How can I get it working again?

edit retag flag offensive close merge delete

Comments

Have you tried using "alt+f2" and running "r"? Resume from suspend often gives me weird issues and this fixes most of them (though I don't have a touch screen). I realise that this is not a solution - the solution is to roll back whatever change broke things...

jcuenod gravatar imagejcuenod ( 2014-11-28 13:16:12 -0500 )edit

That doesn't seem to have any effect on the touch screen. It just makes my screen go black for a few seconds.

jon.reeve gravatar imagejon.reeve ( 2014-12-05 09:11:24 -0500 )edit

There is a ticket on a similar issue from earlier in the year, at which point it seems to have been fixed. I'm experiencing a similar problem.

humanplayer2 gravatar imagehumanplayer2 ( 2014-12-12 16:18:04 -0500 )edit

@humanplayer2, thanks for the link, but it doesn't look like it's been fixed.

jon.reeve gravatar imagejon.reeve ( 2014-12-14 12:48:14 -0500 )edit

1 Answer

Sort by » oldest newest most voted
1

answered 2014-12-21 05:59:34 -0500

humanplayer2 gravatar image

The following works on a Lenovo ThinkPad X1 Carbon Gen2 and a Lenovo Yoga 2.

Open a terminal and type xinput. It will return a list of you input devices, like

rasmus@x1carbon:~$ xinput
⎡ Virtual core pointer                          id=2    [master pointer  (3)]
⎜   ↳ Virtual core XTEST pointer                id=4    [slave  pointer  (2)]
⎜   ↳ SynPS/2 Synaptics TouchPad                id=10   [slave  pointer  (2)]
⎜   ↳ TPPS/2 IBM TrackPoint                     id=14   [slave  pointer  (2)]
⎜   ↳ ELAN Touchscreen                          id=12   [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)]
    ↳ Sleep Button                              id=8    [slave  keyboard (3)]
    ↳ AT Translated Set 2 keyboard              id=9    [slave  keyboard (3)]
    ↳ ThinkPad Extra Buttons                    id=11   [slave  keyboard (3)]
    ↳ Integrated Camera                         id=13   [slave  keyboard (3)]

Find your touchscreen in the list and make a note of it's ID. In the my case it's 12.

To re-enable your touchscreen, then run xinput enable 12, using the ID you just found instead of 12.

edit flag offensive delete link more

Comments

Great, thanks. But how can I get fedora to do that automatically, without having to run any commands manually?

jon.reeve gravatar imagejon.reeve ( 2014-12-24 11:41:26 -0500 )edit

Ok, it looks like it's gnome-settings-daemon 3.14.2 that's the problem. But how can I downgrade that package to 3.14.1?

jon.reeve gravatar imagejon.reeve ( 2015-01-02 13:24:46 -0500 )edit

Question Tools

2 followers

Stats

Asked: 2014-11-28 10:53:37 -0500

Seen: 1,855 times

Last updated: Dec 21 '14