Yes, I created a 10GB-swapfile as per the instructions in the tutorial and added it to fstab, rebooted, verified it was active, and then suspended and resumed and it made no difference. The system locks upon resume.

    Aero9000 Not this sync, but the one after will likely contain kernel 6.4. It's possible that your issue will be resolved by that.

        That's a good point, do you have the same issues on the LTS kernel, or is this isolated to linux-current?

          ReillyBrogan Not this sync, but the one after will likely contain kernel 6.4. It's possible that your issue will be resolved by that.

          I'm not sure I totally understand your reply... After the latest update (7/29/2023) I am still at kernel 6.3.x

          Brucehankins That's a good point, do you have the same issues on the LTS kernel, or is this isolated to linux-current?

          How do I go about to install an lts-kernel? https://getsol.us/articles/troubleshooting/boot-management/en/ no longer seems to exist.

                Aero9000 should just need to run sudo eopkg it linux-lts then reboot and select the LTS kernel on boot. You can load the kennel selection screen by repeatedly pressing spacebar, f12, f10 or one of those keys as soon as the machine starts the boot process.
                LTS I believe is the 6.1.xx kernel branch.

                  Aero9000 There were a few hotfix syncs just to get out some fixes to the Friday sync. We still haven't merged kernel 6.4 into unstable.

                      7 days later

                      ReillyBrogan As per today (august 7, 2023) I am at kernel 6.4. Sadly with no improvement. The system still locks upon resume. :-(

                      Please do note that a short time before the release of Solus 4.4 ISO this issue occurred first. Then, upon the release of Solus 4.4 ISO (which I installed freshly) the issue was resolved and since a few weeks it is back. It looks like a bug regression was inadvertently introduced. Does anyone know which config files relating to power management were changed between 4.4 ISO and now?

                      Is there any way I can actually see which config files were changed since the introduction of 4.4 ISO. I am more than happy to commit the time to reinstall 4.4 ISO and manually compare changes to config files related to power management up until now. I would just like to receive some hints so I don't end up chasing my own tail for days and days for nothing. :-)

                          inxi -b:

                          System:
  Host: solus-desktop Kernel: 6.4.8-247.current arch: x86_64 bits: 64
    Desktop: Budgie v: 10.7.2 Distro: Solus 4.4 harmony
Machine:
  Type: Desktop Mobo: ASUSTeK model: P8B75-V v: Rev X.0x
    serial: <superuser required> BIOS: American Megatrends v: 0801
    date: 10/11/2012
CPU:
  Info: quad core Intel Core i7-3770S [MT MCP] speed (MHz): avg: 1611
    min/max: 1600/3900
Graphics:
  Device-1: NVIDIA GF100 [GeForce GTX 470] driver: nouveau v: kernel
  Display: x11 server: X.Org v: 1.20.14 with: Xwayland v: 23.1.1 driver: X:
    loaded: nouveau unloaded: fbdev,modesetting,vesa dri: nouveau gpu: nouveau
    resolution: 1920x1080~60Hz
  API: OpenGL v: 4.3 Mesa 23.1.5 renderer: NVC0
Network:
  Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet
    driver: r8169
Drives:
  Local Storage: total: 942.7 GiB used: 184.31 GiB (19.6%)
Info:
  Processes: 392 Uptime: 0m Memory: available: 15.57 GiB used: 1.39 GiB (9.0%)
  Shell: Bash inxi: 3.3.27
                          5 months later

                          First of all, congrats to the team for updating Solus to 4.5. :-)

                          But, unfortunately my problem as described above hasn't disappeared. HOWEVER.... I have been able to replicate the issue (i.e., no resume after suspend) on 5 different boxes, all real metal so there definitely there is something wrong and here is how I was able to replicate the issue without failure (ehm... pun intended?).

                          All of my 5 boxes share only one piece of hardware in common. They all have an NVidia graphics card (different models) and they all use the Nouveau driver. I would like to ask volunteers to try the procedure and report back here. The good part is you only need to have the 4.5 iso dd'ed onto a thumb drive and you don't need to install it. I used the Budgie edition.

                          1. Boot off the thumb drive and wait for the desktop to appear.
                          2. Open a terminal and change the password for the live user (type: passwd, the current password is empty and type a new password twice -- I used "live" for the new password).
                          3. Suspend the box and wait for the power supply fans to fall silent. Then wait another 10 seconds.
                          4. Wake up the box. In the resume logon dialog enter your password.
                          5. Verify everything works as per normal.
                          6. Suspend the box again.
                          7. Wake up the box again. On all of my 5 boxes it is now end of story. The background image appears, but no resume logon dialog appears. Or it does appear, but after entering the password nothing responds to mouse clicks or keyboard input anymore.

                          It is as easy as that. Like I wrote, I tested it on 5 different boxes and they all freeze after a 2 time suspend/resume (InteL, AMD doesn't matter).

                            6 days later

                            Aero9000 Please open a bug report on our tracker. The tracker is where we collect information on bugs like this and work on fixes. Thank you.