Activity

1. dannycoulombe commented on May 14, 2022

   

   dannycoulombe

   on May 14, 2022 – with utterances

   More actions

   Any luck with the hibernate/suspend issue?
2. dannycoulombe commented on May 15, 2022

   

   dannycoulombe

   on May 15, 2022

   More actions

   I found the root cause of the issue (at least on my XPS 9510). Closing the lid while having bluetooth enabled was somehow waking the computer, so I managed to test a fix of the issue just by disabling bluetooth in Gnome. Closing the lid now enter in S3 deep sleep.

   So I wrote a script to disable bluetooth and reenable it whenever I close/open the lid.

   1. Create a script with the following command rfkill block bluetooth and make it executable : chmod +x YOUR_SCRIPT_NAME

   2. Create a service

   [Unit]
   Description=User suspend actions
   Before=suspend.target
   
   [Service]
   User=%I
   ExecStart=/home/YOUR_USERNAME/YOUR_SCRIPT_NAME
   
   [Install]
   WantedBy=sleep.target
   

   3. Enable service
      sudo systemctl enable suspend@YOUR_USERNAME

   4. Create service

   [Unit]
   Description=User suspend actions
   Before=suspend.target
   
   [Service]
   User=%I
   ExecStart=/home/YOUR_USERNAME/YOUR_SCRIPT_NAME
   
   [Install]
   WantedBy=suspend.target
   

   4. Enable service
      sudo systemctl enable resume@YOUR_USERNAME

   👍React with 👍1Reacted by Ben Mezger
3. benmezger commented on Jun 17, 2022

   

   benmezger

   on Jun 17, 2022 – with utterances

   Last edited by benmezger

   Owner

   More actions

   @dannycoulombe I managed to get it working days before my XPS decided to die, so I couldn't get this post updated. I use LUKS with an encrypted swap partition, and it turns out I didn't enable the resume [1] hook in my mkinitcpio config and some other things. These are the file changes I needed to do.

   ❤️React with ❤️1Reacted by Dan
4. Repository owner deleted a comment from arielfernandes on Jun 17, 2022
5. benmezger

   added

   commentPost commentPost comment

   on Mar 31, 2023
6. Repository owner locked and limited conversation to collaborators on Jun 19, 2026
7. benmezger

   converted this issue into a discussion #32 on Jun 19, 2026