[Regression] [fixed in Ubuntu 23.04/Linux 6.2.0] Unable to wake laptop using trackpad input

[John Smith]

After upgrade to Ubuntu 22.04,
the dell laptop no longer wakes up using trackpad movement/interaction.

Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e.,
Working On:
Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10.

NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31 )

Just to clarify: Suspend and Resume are working, trackpad is functional before and after suspend,
But,
Trackpad trigger to wakeup from suspend is not working.

----------

$ cat /proc/version_signature > version.log
=> Ubuntu 5.15.0-27.28-generic 5.15.30

-----

$ lsb_release -rd
=>
Description: Ubuntu 22.04 LTS
Release: 22.04

-----

$ apt-cache policy linux-image-generic
=>
linux-image-generic:
  Installed: 5.15.0.27.30
  Candidate: 5.15.0.27.30
  Version table:
 *** 5.15.0.27.30 500
        500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main amd64 Packages
        500 http://mirror2.tuxinator.org/ubuntu jammy-security/main amd64 Packages
        100 /var/lib/dpkg/status
     5.15.0.25.27 500
        500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64 Packages

-----

What I expected to happen:
Laptop wakes-up from suspend on touchpad interaction

-----

What happened:
Laptop did not wakeup from suspend on touchpad interaction.

Laptop woke up on the press of power button.

-----------------------------------------------------------

ProblemType: Bug
DistroRelease: Ubuntu 22.04
Package: linux-image-generic 5.15.0.27.30
ProcVersionSignature: Ubuntu 5.15.0-27.28-generic 5.15.30
Uname: Linux 5.15.0-27-generic x86_64
NonfreeKernelModules: nvidia_modeset nvidia
ApportVersion: 2.20.11-0ubuntu82
Architecture: amd64
AudioDevicesInUse:
 USER PID ACCESS COMMAND
 /dev/snd/controlC0: monkey 5198 F.... wireplumber
 /dev/snd/controlC1: monkey 5198 F.... wireplumber
 /dev/snd/seq: monkey 5195 F.... pipewire
CasperMD5CheckResult: unknown
CurrentDesktop: KDE
Date: Fri May 6 12:40:22 2022
InstallationDate: Installed on 2018-10-25 (1288 days ago)
InstallationMedia: Ubuntu 18.10 "Cosmic Cuttlefish" - Release amd64 (20181017.3)
Lsusb:
 Bus 002 Device 002: ID 0781:5581 SanDisk Corp. Ultra
 Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
 Bus 001 Device 002: ID 8087:0a2a Intel Corp. Bluetooth wireless interface
 Bus 001 Device 003: ID 0bda:568a Realtek Semiconductor Corp. Integrated Webcam
 Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: Dell Inc. Inspiron 15 7000 Gaming
ProcFB: 0 i915drmfb
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-5.15.0-27-generic root=UUID=e6745a81-1ffd-46f5-ae77-652fc77ba79a ro acpi_osi=! "acpi_osi=Windows 2013" quiet splash nvidia-drm.modeset=1 vga=0 rdblacklist=nouveau nouveau.modeset=0 vt.handoff=7
PulseList: Error: command ['pacmd', 'list'] failed with exit code 1: No PulseAudio daemon running, or not running as session daemon.
RelatedPackageVersions:
 linux-restricted-modules-5.15.0-27-generic N/A
 linux-backports-modules-5.15.0-27-generic N/A
 linux-firmware 20220329.git681281e4-0ubuntu1
SourcePackage: linux
UpgradeStatus: Upgraded to jammy on 2022-04-22 (13 days ago)
dmi.bios.date: 08/30/2021
dmi.bios.release: 1.15
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.15.0
dmi.board.name: 065C71
dmi.board.vendor: Dell Inc.
dmi.board.version: A00
dmi.chassis.type: 10
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvr1.15.0:bd08/30/2021:br1.15:svnDellInc.:pnInspiron157000Gaming:pvr:rvnDellInc.:rn065C71:rvrA00:cvnDellInc.:ct10:cvr:sku0798:
dmi.product.family: Inspiron
dmi.product.name: Inspiron 15 7000 Gaming
dmi.product.sku: 0798
dmi.sys.vendor: Dell Inc.

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

This change was made by a bot.

[John Smith (chromastone)]

I tested Pop! OS 22.04 as well, which I think uses Linux 5.16,

It also has the same problem.

So apparently, last working was Linux 5.13.

Problem starts at Linux 5.15 and continues at Linux 5.16

[bam (mybigspam)]

I have similar problem but with Bluetooth devices.

Does it wake up with other USB devices for you? As mouse, etc.

[John Smith (chromastone)]

I tried USB mouse and keyboard, none of which wake-up the device.

(p.s. It might be some setting issue or it could be this bug).

[John Smith (chromastone)]

It wakes-up with USB devices,
(after enabling it in BIOS).

Touchpad/trackpad interaction to wakeup still does not work.

[John Smith (chromastone)]

Tested on Kinetic Kudu 2022-05-16 08:31,

bug still persists,

i.e. Touchpad trigger to wake from suspend DOES NOT work.

Linux Kernel Version on Kinetic Kudu: Linux ubuntu 5.15.0-27-generic #28-Ubuntu SMP Thu Apr 14 04:55:28 UTC 2022 x86_64 x86_64 x86_64 GNU/Linux.

[John Smith (chromastone)]

Thanks @arraybolt3 for tagging.

[John Smith (chromastone)]

https://patchwork.kernel.org<email address hidden>/

This patch from 2020 seems relevant to the bug.

[Kai-Heng Feng (kaihengfeng)]

Author here. This is on my back burner and I hope I can have some spare time to finish it.

[John Smith (chromastone)]

thanks for your efforts on Ubuntu kaihengfeng,

It was working in Ubuntu 21.10/Kernel 5.13,
was it because of manually-applied/non-up-streamed patch,
and, was it disabled because of touchscreen wakeup thing?

And, can I do anything to temporarily fix it ?

(Considering there was no issue with the unintentional wakeup on dell laptop)

(p.s I also get that, counter-intuitively, you spending time replying here is time spent away from fixing things, but....)
(its just that, once you get used to touchpad wakeup, its really jarring to go back to power button wakeup)

[John Smith (chromastone)]

Updated title as WakeUp on touchpad input used to work in previous versions of Ubuntu up till Ubuntu 21.10 (Kernel 5.13)

[Kai-Heng Feng (kaihengfeng)]

Please find the input device node via sysfs and enable the wakeup.

For instance, on my laptop I can do this to enable wakeup:
# echo enabled > /sys/devices/pci0000:00/0000:00:15.0/i2c_designware.0/i2c-0/i2c-SYNA30B3:00/power/wakeup

[John Smith (chromastone)]

Does not appear to have the node

./platform/PNP0C0D:00/power/wakeup disabled
./platform/PNP0C0C:00/power/wakeup disabled
./platform/serial8250/tty/ttyS15/power/wakeup disabled
./platform/serial8250/tty/ttyS6/power/wakeup disabled
./platform/serial8250/tty/ttyS23/power/wakeup disabled
./platform/serial8250/tty/ttyS13/power/wakeup disabled
./platform/serial8250/tty/ttyS31/power/wakeup disabled
./platform/serial8250/tty/ttyS4/power/wakeup disabled
./platform/serial8250/tty/ttyS21/power/wakeup disabled
./platform/serial8250/tty/ttyS11/power/wakeup disabled
./platform/serial8250/tty/ttyS2/power/wakeup disabled
./platform/serial8250/tty/ttyS28/power/wakeup disabled
./platform/serial8250/tty/ttyS0/power/wakeup disabled
./platform/serial8250/tty/ttyS18/power/wakeup disabled
./platform/serial8250/tty/ttyS9/power/wakeup disabled
./platform/serial8250/tty/ttyS26/power/wakeup disabled
./platform/serial8250/tty/ttyS16/power/wakeup disabled
./platform/serial8250/tty/ttyS7/power/wakeup disabled
./platform/serial8250/tty/ttyS24/power/wakeup disabled
./platform/serial8250/tty/ttyS14/power/wakeup disabled
./platform/serial8250/tty/ttyS5/power/wakeup disabled
./platform/serial8250/tty/ttyS22/power/wakeup disabled
./platform/serial8250/tty/ttyS12/power/wakeup disabled
./platform/serial8250/tty/ttyS30/power/wakeup disabled
./platform/serial8250/tty/ttyS3/power/wakeup disabled
./platform/serial8250/tty/ttyS20/power/wakeup disabled
./platform/serial8250/tty/ttyS10/power/wakeup disabled
./platform/serial8250/tty/ttyS29/power/wakeup disabled
./platform/serial8250/tty/ttyS1/power/wakeup disabled
./platform/serial8250/tty/ttyS19/power/wakeup disabled
./platform/serial8250/tty/ttyS27/power/wakeup disabled
./platform/serial8250/tty/ttyS17/power/wakeup disabled
./platform/serial8250/tty/ttyS8/power/wakeup disabled
./platform/serial8250/tty/ttyS25/power/wakeup disabled
./platform/i8042/serio0/power/wakeup disabled
./platform/i8042/serio1/power/wakeup disabled
./pci0000:00/0000:00:17.0/power/wakeup disabled
./pci0000:00/0000:00:1c.0/0000:02:00.0/power/wakeup disabled
./pci0000:00/0000:00:01.0/0000:01:00.0/power/wakeup disabled
./pci0000:00/0000:00:1c.5/0000:03:00.0/power/wakeup disabled
./pci0000:00/0000:00:16.0/power/wakeup disabled
./pci0000:00/0000:00:1f.3/power/wakeup disabled
./pci0000:00/0000:00:14.0/usb1/power/wakeup disabled
./pci0000:00/0000:00:14.0/usb1/1-4/power/wakeup disabled
./pci0000:00/0000:00:14.0/usb2/power/wakeup disabled

The above is the output of
find ./ -type f -iname "*wakeup" -printf '%p\t\t' -exec cat {} \; | grep -i disabled

In the directory: /sys/devices

[John Smith (chromastone)]

I tried enabling

./pci0000:00/0000:00:17.0/power/wakeup disabled
./pci0000:00/0000:00:1c.0/0000:02:00.0/power/wakeup disabled
./pci0000:00/0000:00:01.0/0000:01:00.0/power/wakeup disabled
./pci0000:00/0000:00:1c.5/0000:03:00.0/power/wakeup disabled
./pci0000:00/0000:00:16.0/power/wakeup disabled
./pci0000:00/0000:00:1f.3/power/wakeup disabled
./pci0000:00/0000:00:14.0/usb1/power/wakeup disabled
./pci0000:00/0000:00:14.0/usb1/1-4/power/wakeup disabled
./pci0000:00/0000:00:14.0/usb2/power/wakeup disabled

did not work.

Also, when I enabled ./pci0000:00/0000:00:14.0/usb1/power/wakeup,
the system instantly wokeup without any interaction after suspend,
(maybe another bug... ?)

I tried enabling one-by-one,
none of them worked.

[John Smith (chromastone)]

@kaihengfeng any other workaround ... ?

[Kai-Heng Feng (kaihengfeng)]

It's "/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00" on your system.

[John Smith (chromastone)]

@kaihengfeng There is no "wakeup" file in "/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00"

[John Smith (chromastone)]

@kaihengfeng There is no "wakeup" file in /sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00

I'm attaching the output of sudo ls --recursive /sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00 > fs-ls.txt

"tree" command had weird characters in output file as rendered on bug page.

[John Smith (chromastone)]

@kaihengfeng The above "tree /sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00" command output in html format.

[John Smith (chromastone)]

@kaihengfeng any workarounds?
The device node "/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00" doesn't have "wakeup" file to write "enabled" to ...

Am I missing something ?

[Kai-Heng Feng (kaihengfeng)]

There's no "/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00/power/wakeup"?

[John Smith (chromastone)]

$ sudo ls -l /sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00/power/wakeup

ls: cannot access '/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00/power/wakeup': No such file or directory

[Kai-Heng Feng (kaihengfeng)]

Some characters may need to escape, so it's better to cd to the sysfs directory first.

[John Smith (chromastone)]

I did, there is no "wakeup" file.
I used tab auto-complete to reach there.

[John Smith (chromastone)]

$ pwd
/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00/power

$ sudo ls -l
total 0
-rw-r--r-- 1 root root 4096 May 24 19:13 async
-rw-r--r-- 1 root root 4096 May 24 19:13 autosuspend_delay_ms
-rw-r--r-- 1 root root 4096 May 24 19:13 control
-r--r--r-- 1 root root 4096 May 24 19:13 runtime_active_kids
-r--r--r-- 1 root root 4096 May 24 19:13 runtime_active_time
-r--r--r-- 1 root root 4096 May 24 19:13 runtime_enabled
-r--r--r-- 1 root root 4096 May 24 19:13 runtime_status
-r--r--r-- 1 root root 4096 May 24 19:13 runtime_suspended_time
-r--r--r-- 1 root root 4096 May 24 19:13 runtime_usage

[Kai-Heng Feng (kaihengfeng)]

Oh please remove all the "acpi*" kernel parameters which mess with the ACPI.

[John Smith (chromastone)]

Didn't Work.
---
I removed acpi_os parameters,

updated grub with update-grub,

rebooted,

touchpad still does not wakeup device, and,

$ pwd
/sys/devices/pci0000:00/0000:00:15.1/i2c_designware.1/i2c-2/i2c-DLL0798:00/power

$ ls -la
total 0
drwxr-xr-x 2 root root 0 May 25 14:55 .
drwxr-xr-x 4 root root 0 May 25 14:34 ..
-rw-r--r-- 1 root root 4096 May 25 14:55 async
-rw-r--r-- 1 root root 4096 May 25 14:55 autosuspend_delay_ms
-rw-r--r-- 1 root root 4096 May 25 14:55 control
-r--r--r-- 1 root root 4096 May 25 14:55 runtime_active_kids
-r--r--r-- 1 root root 4096 May 25 14:55 runtime_active_time
-r--r--r-- 1 root root 4096 May 25 14:55 runtime_enabled
-r--r--r-- 1 root root 4096 May 25 14:55 runtime_status
-r--r--r-- 1 root root 4096 May 25 14:55 runtime_suspended_time
-r--r--r-- 1 root root 4096 May 25 14:55 runtime_usage

[Kai-Heng Feng (kaihengfeng)]

OK, so the laptop doesn't use s2idle, it's using S3 instead. Please perform a kernel bisection [1] to find the regression commit.

[1] https://wiki.ubuntu.com/Kernel/KernelBisection

[John Smith (chromastone)]

$ cat /sys/power/mem_sleep
s2idle [deep]

selecting s2idle doesn't suspend as it used to,
with keyboard lights on, and power light on,
also it doesn't wake with touchpad in "s2idle".

I had up-to-date Ubuntu 21.10 and there was no issue,
The release day update to 22.04 started the problem.

So 5.13(ubuntu most up-to-date) -> 5.15 (maybe earliest ubuntu build).

Will get precise after familiarizing myself with,
bisecting, building kernel, booting with built kernel ... and all that.

Will try to get into that ...
----

Also, is there any source available for archives of Ubuntu daily builds of Jammy (22.04) which I can live boot and try.
(As a shortcut to bisecting ¯\_(ツ)_/¯ )

[John Smith (chromastone)]

Also what would happen if I (manage to) boot with kernel 5.14 ... ?

(I use Proprietary Nvidia driver with Nvidia prime)
(Intel Kaby-Lake processor (7700HQ) )

[Aaron Rainbolt (arraybolt3)]

Successfully replicated this bug on an HP Elitebook 8570p, 16 GB RAM, Intel i5-3210M (if dmidecode is not deceiving me). I also cannot get the touchpad to cause the system to wake from suspend even trying to enable the wakeup files for all three of the USB controllers in my system. OS is the latest Lubuntu Kinetic.

[John Smith (chromastone)]

Thanks for confirming arraybolt13.

[Kai-Heng Feng (kaihengfeng)]

Touchpad wake in general only works on newer laptops that support Modern Standby (i.e. s2idle).

[John Smith (chromastone)]

Touchpad wake was working till Ubuntu 21.10 (Kernel 5.13) and all previous (Ubuntu) versions on my Dell Inspiron 7000 series laptop.

And it was working with [deep] sleep.

[John Smith (chromastone)]

I tried Fedora 34 (Kernel 5.11) on which touchpad wake from [deep] sleep WAS WORKING.

I tried Fedora 35 (Kernel 5.14) on which touchpad wake from [deep] sleep WAS NOT working.

So Kernel Version 5.13 is the last major series on which touchpad wake was working.

[John Smith (chromastone)]

Ubuntu 21.10 (Working) -> Ubuntu 22.04 (Not Working) -> Ubuntu 22.10 snapshot-kinetic (Not Working)

Fedora 34 (Working) -> Fedora 35 (Not Working)

------

#> Linux 5.11 (Working) (Fedora 34)
-> Linux 5.13 (Working) (Ubuntu 21.10)

-> Linux 5.14 (NOT working) (Fedora 35)
-> Linux 5.15 (NOT working) (Ubuntu 22.04) (Ubuntu Kinetic)

[John Smith (chromastone)]

Is anyone working on this, 'cause I have no experience "actually" bisecting kernel.

It will likely take time if/after I start now.

I have narrowed it down to 5.13->bad-change->5.14.

😁

[Aaron Rainbolt (arraybolt3)]

@chromastone I have experience with building software from source, and have a laptop that replicates the problem. I'll give it a shot.

[Aaron Rainbolt (arraybolt3)]

Sadly, I have to correct myself - I thought I had replicated the issue, but it turns out my particular laptop doesn't use USB to attach the mousepad. I tried plugging a USB mouse into my system while running a "bad" kernel, and it was able to wake from suspend when I moved the mouse. Also, it appears my system is using s2idle. So sadly, I cannot reproduce the bug on my hardware after all.

What I can do is leave a hint for the next person who goes to bisect the kernel. Due to a change in initrd compression, if you try to install a kernel that's too old onto Ubuntu Jammy or Kinetic, it won't be able to boot since it won't be able to mount the initrd image. To fix this, do "sudo nano /etc/initramfs-tools/initramfs.conf", and change the "COMPRESS" option to "gzip" (it will probably be set to "zstd" by default). That should get your older kernels booting, so you can actually have a fighting chance at bisecting the kernel.

Sorry I couldn't do it myself on my hardware.

[John Smith (chromastone)]

Thanks for trying Aaron,
Effort much appreciated.

Also, I think there is some miscommunication,
i.e. My laptop also wakes up with USB devices
(After configuration change in BIOS),

Problem is, my laptop used to wakeup on touchpad interaction as well (till
Ubuntu 21.10).
But after upgrading (to 22.04 jammy),

Touchpad wake is not working.

Does it work on your laptop or it never did ?
(Touchpad interaction to wakeup)

On Fri, May 27, 2022, 11:00 AM Aaron Rainbolt <email address hidden>
wrote:

> Sadly, I have to correct myself - I thought I had replicated the issue,
> but it turns out my particular laptop doesn't use USB to attach the
> mousepad. I tried plugging a USB mouse into my system while running a
> "bad" kernel, and it was able to wake from suspend when I moved the
> mouse. Also, it appears my system is using s2idle. So sadly, I cannot
> reproduce the bug on my hardware after all.
>
> What I can do is leave a hint for the next person who goes to bisect the
> kernel. Due to a change in initrd compression, if you try to install a
> kernel that's too old onto Ubuntu Jammy or Kinetic, it won't be able to
> boot since it won't be able to mount the initrd image. To fix this, do
> "sudo nano /etc/initramfs-tools/initramfs.conf", and change the
> "COMPRESS" option to "gzip" (it will probably be set to "zstd" by
> default). That should get your older kernels booting, so you can
> actually have a fighting chance at bisecting the kernel.
>
> Sorry I couldn't do it myself on my hardware.
>
> --
> You received this bug notification because you are subscribed to the bug
> report.
> https://bugs.launchpad.net/bugs/1971933
>
> Title:
> [Regression] Unable to wake laptop using trackpad input
>
> Status in linux package in Ubuntu:
> Confirmed
>
> Bug description:
> After upgrade to Ubuntu 22.04,
> the dell laptop no longer wakes up using trackpad movement/interaction.
>
> Wake-on trackpad-interaction used to work since Ubuntu Bionic, i.e.,
> Working On:
> Ubuntu 18.04, 18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10.
>
> NOT Working on: Ubuntu 22.04, Ubuntu 22.10 (Kinetic - 2022-05-16 08:31
> )
>
> Just to clarify: Suspend and Resume are working, trackpad is functional
> before and after suspend,
> But,
> Trackpad trigger to wakeup from suspend is not working.
>
> ----------
>
> $ cat /proc/version_signature > version.log
> => Ubuntu 5.15.0-27.28-generic 5.15.30
>
> -----
>
> $ lsb_release -rd
> =>
> Description: Ubuntu 22.04 LTS
> Release: 22.04
>
> -----
>
> $ apt-cache policy linux-image-generic
> =>
> linux-image-generic:
> Installed: 5.15.0.27.30
> Candidate: 5.15.0.27.30
> Version table:
> *** 5.15.0.27.30 500
> 500 http://mirror2.tuxinator.org/ubuntu jammy-updates/main
> amd64 Packages
> 500 http://mirror2.tuxinator.org/ubuntu jammy-security/main
> amd64 Packages
> 100 /var/lib/dpkg/status
> 5.15.0.25.27 500
> 500 http://mirror2.tuxinator.org/ubuntu jammy/main amd64
> Packages
>
> -----
>
> What I expected to happen:
> Laptop wakes-up from suspend on touchpad interaction
>
> -----
>
> What happened:
> Laptop ...

[Aaron Rainbolt (arraybolt3)]

I installed the same kernel that is in 20.04 onto a Lubuntu Kinetic (22.10 alpha) installation, and the touchpad wake didn't work on my laptop. I then tried USB wake on the kernel that's part of Kinetic, and USB wake did work.

[John Smith (chromastone)]

Was it working in any version on your laptop ?

(could be hardware difference).

I have an old XPS 15 (now barely used) that never had touchpad to wake.

On the new dell Inspiron 7000 series laptop, the touchpad (interaction) to wake worked from the start. It worked for Ubuntu (18.10, 19.04, 19.10, 20.04, 20.10, 21.04, 21.10)

[Aaron Rainbolt (arraybolt3)]

I don't believe that my system ever was able to wake from the touchpad - I seem to remember having to use the power button or open the lid in the past. I thought maybe I just had something misconfigured back then, but maybe not.

[John Smith (chromastone)]

Then, maybe, this (touchpad wake trigger) feature is more recent than the model of laptop you are using.

Because USB wakeup feature has been present in laptops for quite a while.
(My 10 year old laptop had that (USB wake trigger), but, touchpad wake has been available only on Dell Inspiron 7000 (series) laptop.)

[John Smith (chromastone)]

Sorry for late reply, I had headache related issues, and hence I was a bit away from my device.

[bam (mybigspam)]

Could someone try wake up from deep sleep on Bluetooth? Didn't work for me since recently (maybe Ubuntu 21.10), I wonder if it's related issue or not.
Thanks.

[John Smith (chromastone)]

bam, I don't have any bluetooth keyboard or mouse but I tried with an App on an android device that acts as bluetooth keyboard/mouse, it did nothing (i.e. no wakeup)

Although, the moment the system went to sleep, the app disconnected, so,
I think the bluetooth connection isn't maintained in deep sleep.

Did it ever work on any version of Ubuntu?

[bam (mybigspam)]

Thanks for testing John.
Yes, it did work IIRC, one or two releases above.
So maybe these issues are related.

Bluetooth disconnects on Sleep, but when you press a button on bt keyboard or mouse, it sends special broadcasts packets to wake the host device up. Maybe worth to try on real BT hw.

[John Smith (chromastone)]

Does your bluetooth keyboard/mouse connect directly to laptop or it has its own adapter ?

[BT Mouse]~~~~bluetooth~~~~~~~[laptop]

or

[BT mouse]~~~~bluetooth~~~~~~~[mouse adapter]-[laptop]

[bam (mybigspam)]

I'm not sure what you mean, bt adapter is needed anyway, in my case it's M.2 BT card but it has USB interface internally, the same as external USB BT dongle would have.

[John Smith (chromastone)]

I was totally guessing, that if its plugged into USB, then it might be using USB wakeup.

¯\_(ツ)_/¯

(because USB wakeup ...is... working on my laptop (after changing config in BIOS) )

[bam (mybigspam)]

USB wakeup is working for me too, despite the fact BT is connected over USB but doesn't work

[John Smith (chromastone)]

I just noticed, why is the importance marked as "wishlist"?

it is confirmed bug as,

A function (wake on touchpad interaction) was working in several past version of Ubuntu
(atleast 18.04 to 21.04), but stopped working with Ubuntu 21.10 (Kernel 5.15).

Kernel: 5.13 -> bug -> 5.14

Last when I was looking into it, I managed to identify the buggy kernel version to between 5.13 & 5.14.
(After that I got ill for half a month, then, my main internet connection broke for half a month),

After that it just got backlogged in mind.

Now my main internet is again broken, so I was checking on progress of this bug,
unfortunately, I can't really make any progress as I am on very limited data connection.

[John Smith (chromastone)]

I am happy to report that as of Linux 6.2.0-1003-lowlatency the touchpad interaction to wake from suspend is working again.

(After Upgrading to Lunar (23.04)).

Just noticed that it started working again.

Big thanks to whomever fixed it.
Kudos.
Live Long and Prosper 🖖

😀😀😀😀😀😀