[Asus X541NC] wakes up from sleep mode after 1 second (unless ACPI RP03 is disabled)

Thanks for the bug report. The first thing to try is to unplug your peripherals (before sleeping) to see if it is any of them waking the machine up.

joao 1000 joao 1945 gsd-media-keys handle-power-key:handle-suspend-key:handle-hibernate-key GNOME handling keypresses block

this is the only thing i have, but it should be disabled automatically when entering sleep mode, right?

I'm not sure if that is relevant. I was recommending you unplug any keyboards and mice etc but it looks like you might not have any such things plugged in...

Do you have any Bluetooth devices configured? If so then please try disabling Bluetooth on the laptop before entering sleep mode.

well, i have nothing plugged into computer. this is just a laptop with nothing connected here, no mouse, no mic, nothing, and i even have the bluetooth off all the time. this happens since i changed recently from 18.04 to 20.04, from that very moment computer never went to sleep mode. when it comes the time to do ti, as i set it, it goes to sleep for one second or sell and wakes up immediately. and besides, i can not find anywhere in the configurations how to set what computer does when closing the lid.

I have seen suggestions that some machines get monitor "hotplug" events when they go to sleep and that might cause them to immediately wake up again. If that was the cause then selecting:

  Ubuntu on Wayland

from the login screen (bottom right corner just before you enter your password) might avoid the issue. Actually trying 'Ubuntu on Wayland' might avoid the issue even if the root cause is something different.

well, i have nothing plugged into computer. this is just a laptop with nothing connected here, no mouse, no mic, nothing, and i even have the bluetooth off all the time. this happens since i changed recently from 18.04 to 20.04, from that very moment computer never went to sleep mode. when it comes the time to do it, as i set it, it goes to sleep for one second or less and wakes up immediately. and besides, i can not find anywhere in the configurations how to set what computer does when closing the lid.

I know there is no monitor connected but "hotplug" events might still occur internally for the laptop's screen as it is turned on or off. Please try the instructions in comment #6.

I have just tried it (on wayland) I doesn't work. The same happens.

I saw on the internet that other people are facing the same issue, so that's why i decided to report it, it looks to me that is is a bug.

It never happend to me when using 16 nor 18.04, and this is so annoying that i am considering going back to 18.04.

*it doesn't work

OK, next please:

1. Reproduce the bug again.

2. As soon as it's woken itself up, open a Terminal and run:

   journalctl -b0 > woke.txt

3. Attach the resulting text file here.

thank you for your help!
here it is attached the information you requested.

Looks like it's the network waking the machine up, so try disabling any wake-on-network-activity option(s) in your BIOS.

rugs. 17 11:48:13 joao-X541NC systemd[1]: Finished Suspend.
rugs. 17 11:48:13 joao-X541NC systemd[1]: Stopped target Sleep.
rugs. 17 11:48:13 joao-X541NC systemd[1]: Reached target Suspend.
rugs. 17 11:48:13 joao-X541NC systemd[1]: Stopped target Suspend.
rugs. 17 11:48:13 joao-X541NC systemd-logind[966]: Operation 'sleep' finished.
rugs. 17 11:48:13 joao-X541NC NetworkManager[937]: <info> [1631868493.2691] manager: sleep: wake requested (sleeping: yes enabled: yes)
rugs. 17 11:48:13 joao-X541NC NetworkManager[937]: <info> [1631868493.2693] device (enp1s0): state change: unmanaged -> unavailable (reason 'managed', sys-iface-state: 'managed')
rugs. 17 11:48:13 joao-X541NC kernel: RTL8208 Fast Ethernet r8169-100:00: attached PHY driver (mii_bus:phy_addr=r8169-100:00, irq=POLL)

Ok thanks, I will try to do it and let you know here.

It doesn't work. Are you sure it is internal and an issue that can be solve in computer BIOS? Actually I couldn't find there where to disable any network wake request. The only one available was the "wake on lid open" that I indeed disabled just now, but the situation doesn't change.

And besides, computer was sleeping with windows before alongside with ubuntu 18.04, but since i formated computer and installed 20.04, there is no way i can "put computer to sleep". There were no changes in BIOS, just this flaw.

It appears you can configure what hardware components can wake the machine up with /proc/acpi/wakeup

Can you attach a copy of that file here?

Yes, sure. Here it is...

Thanks. That seems to show only internal components (PCIe) and the USB 3.0 controller can wake the machine up. Please try disabling each of them separately:

  sudo sh -c 'echo XHC > /proc/acpi/wakeup'
  sudo sh -c 'echo RP01 > /proc/acpi/wakeup'
  sudo sh -c 'echo RP03 > /proc/acpi/wakeup'
  sudo sh -c 'echo RP04 > /proc/acpi/wakeup'

If none of those work then the next step would be to see if the nouveau driver is causing the issue. I would recommend trying the official Nvidia driver instead, which you can enable by the 'Additional Drivers' app or:

  sudo apt install nvidia-driver-430

Well, i tried installing nvidia but nothing changed. I am going now to try to disable those controllers. But aren't they going to mess other things in computer? Can you please tell me how to enable them if something goes not right?

To re-enable them is the same command, it only toggles the setting. Also it may not be remembered between reboots so just rebooting likely will reset them too.

finally it worked after:

sudo sh -c 'echo RP03 > /proc/acpi/wakeup'

but computer is not sleeping after i restarted it... and besides, doing this i am disabling something, right?

RP03 is the "PCI Express Port A #1" but that doesn't tell us much else. And no you're not disabling anything other than the ability of one device to wake the machine up. So long as you have some other way of waking the machine up it should be safe.

I'm not sure what the recommended way of disabling RP03 by default would be...

thank you for your help. at least i know now how to enable sleep, although the problem still persists. i will try to find a way to make this permanent, so i don't have to run it on terminal each time i turn on computer...