Ubuntu 19.04 - tablet pc won't wake with pen or device buttons (unless keyboard attached)

[Chris Guiver]

Ubuntu 19.04 QA-TEST on tablet.pc (wacom pen)
motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)

The test went really well, but I noticed I couldn't wake it if left alone and screen dims & thus locks using tablet buttons or pen (& its button).

This is [most] likely device specific & is very MINOR.

It woke perfectly when keyboard/stand was attached, but not with the device's arrow keys, button, or any on screen mouse movement (using pen, including pen button). If the device dimmed screen with onscreen keyboard no longer visible, and I couldn't wake it.

The result was you had to connect keyboard/stand in order to wake device... The track-pad on the keyboard/stand woke machine too, but that required keyboard to be attached.

ProblemType: Bug
DistroRelease: Ubuntu 19.04
Package: gnome-power-manager 3.30.0-2
ProcVersionSignature: Ubuntu 4.18.0-11.12-generic 4.18.12
Uname: Linux 4.18.0-11-generic x86_64
ApportVersion: 2.20.10-0ubuntu19
Architecture: amd64
CasperVersion: 1.402
CurrentDesktop: ubuntu:GNOME
Date: Wed Feb 20 07:00:51 2019
LiveMediaBuild: Ubuntu 19.04 "Disco Dingo" - Alpha amd64 (20190203)
ProcEnviron:
 TERM=xterm-256color
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: gnome-power-manager
UpgradeStatus: No upgrade log present (probably fresh install)

[Ubuntu QA Website (ubuntuqa)]

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1816702

[Chris Guiver (guiverc)]

I'll have to re-test this; just did a Lubuntu 19.10 (daily) QA-test on the j3400 mentioned, and it was woken using power-button and only wacom-pen was required to resume session.

[Sebastien Bacher (seb128)]

The waking up is probably lower level, gnome-power-manager also isn't a service but just an UI showing power usage statistics nowadays

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1816702

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Chris Guiver (guiverc)]

> If due to the nature of the issue you have encountered, you are unable to run this command,
> please add a comment stating that fact and change the bug status to 'Confirmed'.
It was a 'live' QA-test (19.04 daily) so I cannot add information on that run.

[Kai-Heng Feng (kaihengfeng)]

Is this a regression?

[Chris Guiver (guiverc)]

My comment #3 is in error, on the QA-test I wrote

"...suspended system, waited, woke with power button, screensaver was visible which I could wake with wacom pen & streaming news continued (with sound)."

I misread this report which is not about wake-from-suspend; thus comment #3 is invalid.
Sorry for my mistake. (I've already started 19.10 Ubuntu zsync, and will test for this function using the 19.10 Lubuntu again).

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1816702

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Chris Guiver (guiverc)]

Ubuntu 19.10 QA-test
motion computing j3400 (c2d-u9400, 4gb, intel mobile 4 series)
-- notes from qa-test comments
screensaver has kicked in four times now, and both times I could stroke-up with pen & session resumed (not requiring keyboard).
--
I don't think I can change status to "fix-released" or "invalid" as bug was for 19.04 (it'd require me to download & test 19.04). It's not an issue in 19.10 anyway.

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:

apport-collect 1816702

and then change the status of the bug to 'Confirmed'.

If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.

This change has been made by an automated script, maintained by the Ubuntu Kernel Team.

[Chris Guiver (guiverc)]

Marking invalid - i cannot re-create on j3400 using released 19.04, nor daily 19.10

I have now booted the released 19.04 with both keyboard-stand connected, plus it as a 'tablet' only, and with power-blanking set to 1 minute (to allow more testing in less time), I can use the pen to wake or unlock device. Whatever caused the initial problem on 19.04 daily has gone.