After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 778961 - Unable to unlock blanked screen from touchscreen
Unable to unlock blanked screen from touchscreen
Status: RESOLVED NOTABUG
Product: gnome-shell
Classification: Core
Component: lock-screen
3.22.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2017-02-20 15:35 UTC by John Candlish
Modified: 2020-12-10 18:09 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
xorg logfile (29.30 KB, text/x-log)
2017-02-20 15:35 UTC, John Candlish
  Details
Add touch screen input switch (2.68 KB, patch)
2018-04-08 07:27 UTC, xiaoguang wang
none Details | Review
Add touch screen input switch (2.22 KB, patch)
2018-04-08 09:11 UTC, xiaoguang wang
none Details | Review

Description John Candlish 2017-02-20 15:35:07 UTC
Created attachment 346269 [details]
xorg logfile

'evtest' from a remote terminal shows that the touchscreen is sensitive but the session requires input from an attached mouse or keyboard to wake the screen.

This is Debian Stretch // The touchscreen devices is an eGalax.



The machine is configured not to suspend or hibernate. It is only waking the lockscreen from DPMS.

I can only wake the monitor by touching a key on the keyboard or mouse. I can see touch events of the touchscreen using the evtest utility from a remote console while the monitor is in DPMS sleep, but those touch events do nothing.

Touch events never wake the monitor from DPMS sleep.

If I wake the monitor from sleep then I can swipe away the clock screen and login just using the touchscreen.
Comment 1 Serge Gavrilov 2018-01-26 16:18:52 UTC
I confirm the problem. Gnome 3.24, x.org, lenovo X1 yoga 2nd gen.
Comment 2 Serge Gavrilov 2018-01-26 16:19:07 UTC
I confirm the problem. Gnome 3.24, x.org, lenovo X1 yoga 2nd gen.
Comment 3 Linus Larsson 2018-03-06 15:46:48 UTC
Seeing the exact same thing, also using eGalax.
'evtest' show events but screen stays off.
Gnome 3.20, Xorg
Comment 4 Bastien Nocera 2018-03-29 14:17:23 UTC
That's as expected. The touchscreen will be disabled when it's turned off. It's expected that at least one button will be available on the device to wake it up.

This is implemented in mutter for Wayland:
https://bugzilla.gnome.org/show_bug.cgi?id=739397
and in gnome-settings-daemon's power plugin for X11 though we want to move it to mutter as well:
https://bugzilla.gnome.org/show_bug.cgi?id=742598

Closing as not being a bug as it's working as designed.
Comment 5 Hans Petter Jansson 2018-03-29 17:56:43 UTC
Presumably input deactivation is due to the power consumed by the input mechanism itself?

I can see it being a good policy in some scenarios but not others. If it's a mobile device with an exposed screen, you definitely want to suppress wakeup on touch events, but if it's a stationary/plugged-in device, or a device with lots of battery capacity, it may make sense to allow wakeup on touch. And I guess in some cases there may be no other way to do it.
Comment 6 xiaoguang wang 2018-04-08 07:27:24 UTC
Created attachment 370648 [details] [review]
Add touch screen input switch

It makes sense to add a switch to let user have a chance to enable touch screen input when screen is off.
The default value of switch is to disable touch screen input, user can change this value to enable touch screen input.
Comment 7 Florian Müllner 2018-04-08 09:11:21 UTC
You are unlikely to get feedback for a gnome-settings-daemon patch on a closed gnome-shell bug. I suggest you file a merge request on gitlab.gnome.org/GNOME/gnome-settings-daemon/merge_requests instead.
Comment 8 xiaoguang wang 2018-04-08 09:11:43 UTC
Created attachment 370650 [details] [review]
Add touch screen input switch
Comment 9 f.viktor.t 2020-12-10 18:06:11 UTC
(In reply to Bastien Nocera from comment #4)
> It's expected that at least one button will be available on the device to
> wake it up.

What kind of expectation is that? In a great amount of cases touch screens are used for exactly that: to substitute keyboards and mouses. Just think of all-in-one pcs or touchscreen terminals with on-screen keyboards etc. This is just how they work all around the world (and how everyone expects them to work): the user steps in front of the screen, touches it to turn it on, then starts working on it.
Why would you want to block such a trivial use case? I'm sorry it's really beyond me why you'd ever want to design a system that works like that.
Comment 10 Bastien Nocera 2020-12-10 18:09:39 UTC
(In reply to f.viktor.t from comment #9)
> (In reply to Bastien Nocera from comment #4)
> > It's expected that at least one button will be available on the device to
> > wake it up.
> 
> What kind of expectation is that? In a great amount of cases touch screens
> are used for exactly that: to substitute keyboards and mouses. Just think of
> all-in-one pcs or touchscreen terminals with on-screen keyboards etc. This
> is just how they work all around the world (and how everyone expects them to
> work): the user steps in front of the screen, touches it to turn it on, then
> starts working on it.
> Why would you want to block such a trivial use case? I'm sorry it's really
> beyond me why you'd ever want to design a system that works like that.

Why don't you file a new issue instead of yelling at a 2 year old bug? You better change your tone if you expect people to listen though.