Resuming after loginctl suspend or closing/reopening laptop lid

[NuLL3rr0r]

Pre-requisites

• I have looked for any other duplicate issues

Ly version

Ly version 1.0.1

Observed behavior

When invoking:

$ loginctl suspend

Or, by closing the laptop lid the system goes to suspend, which is expected. But, as soon as I reopen the lid, even though the laptop keyboard and power LED turn on, I see the display is blank, pressing Ctrl+Alt+F1 won't go to TTY1 either.

I SSH from another machine and can check the lid and loginctl status as well:

$ cat /proc/acpi/button/lid/LID0/state 
state:      open

$ loginctl session-status
4 - mamadou (1000)
           Since: Sun 2024-07-28 18:59:30 CEST; 1min 19s ago
          Leader: 15256 (sshd-session)
          Remote: 192.168.2.140
         Service: sshd; type tty; class user
           State: active

$ loginctl list
SESSION  UID USER    SEAT  TTY 
      3 1000 mamadou seat0 tty2
      4 1000 mamadou       

2 sessions listed.

$ loginctl list-users
 UID USER    LINGER
1000 mamadou no

1 users listed.

$ loginctl user-status mamadou
mamadou (1000)
           Since: Sun 2024-07-28 18:57:15 CEST; 5min ago
           State: active
        Sessions: 4 *3
          Linger: no
            Unit: user-1000.slice

I'm on Gentoo using OpenRC.

Expected behavior

The laptop should resume working where I left off in order to preserve the current session, especially since SDDM works perfectly fine on this laptop.

Steps to reproduce

1. Close the lid or loginctl suspend.
2. Reopen the lid.

Relevant logs

No response

[AnErrupTion]

@NuLL3rr0r Does using s2ram as root work? If so, try to do the following:

Open the file /etc/pam.d/ly, and add the following line right after #%PAM-1.0:

-session   optional     pam_elogind.so

Reboot, and try to use loginctl suspend again.

[NuLL3rr0r]

Thank you for the suggestion. I tried s2ram, but it refused to work since it could not detect the hardware:

$ s2ram        
Machine is unknown.
This machine can be identified by:
    sys_vendor   = ""
    sys_product  = ""
    sys_version  = ""
    bios_version = ""

But, s2ram -f works. It suspends and resumes successfully.

I tried your suggestion, but still loginctl suspend or closing the lid and reopening it gives me a blank screen.

$ cat /etc/pam.d/ly 
#%PAM-1.0

session   optional     pam_elogind.so

auth       include      login
account    include      login
password   include      login
session    include      login

I tried this with the - as well but did not work either:

$ cat /etc/pam.d/ly 
#%PAM-1.0

-session   optional     pam_elogind.so

auth       include      login
account    include      login
password   include      login
session    include      login

[NuLL3rr0r]

Interesting, I did a bit more experiments. If I add that session line to /etc/pam.d/ly it breaks s2ram as well. But, another experiment when I do s2ram -f if I don't close the lid it's able to wake up. If I close the lid and reopen it, I don't get the exact same blank screen, this time the cursor is visible but everything is black. Even if I switch my i3wm workspaces to my terminal workspace or the web browser workspace, I see the cursor changes accordingly but nothing is visible and black, until I press the power button, then for a fraction of a second, I see my desktop wallpaper before switching to tty1 for shutdown. Without s2ram I don't see anything until it switches to tty1.