Swap Files and Hibernation

[ericmarceau]

Have you reviewed the following for enabling hibernate?

• How To Enable Hibernation On Ubuntu (When Using A Swap File)

• Re-visiting hibernate on Ubuntu - #21 by michel.ekimia

---

Making a reference to a couple of earlier posts …

@paddylandau

Hibernation is disabled. Linux itself is incompatible with Secure Boot (I don’t know why), hence why Ubuntu has specifically disabled it.

@popey

if it’s so catastrophically broken, how is it I seem to stumble upon only the people running other distros (today, OpenSUSE) who claim it works fine for them, and are agog that we don’t enable it?

I understand the “Corporate” stance that … because “hibernate” is incompatible with Secure Boot … the coding for that functionality is neither implemented, nor proven. Where “Corporate” is looking to make commitments regarding “safety” and “security” that stance is sound.

However, that “contract-based” corporate market is only one slice of the market.

The other slice of the market is those that want the hibernate function. Since that is a functionality on other platforms, that is a functionality which should be developped and implemented because, the loss of market-penetration resulting from NOT having the capability is too serious a slice to ignore!

My suggestion is that the capability be implemented in two phases:

• firstly … operating mode with Secure Boot OFF,         then
• secondly … operating mode with Secure Boot ON.

After all, if other operating systems can manage implementing the functionality, with Secure Boot ON, how can Linux not be able to do better?

Since it is a Linux-wide failing, that sounds like a joint-venture opportunity with other Distros to throw some resources into making it work, for the shared benefit of the Linux Community!

And let’s not overlook what looks like some very good work by the Arch Linux Team at investigating and documenting all that .

Stepping off the podium!

Thank you for hearing me out.

[paddylandau]

@ericmarceau

implementing the functionality, with Secure Boot ON, how can Linux not be able to do better?

Linus Torvalds has explained this, though I don’t understand the technical details. You can look it up.

It has to be implemented in the kernel, and it isn’t trivial, and so it’s unlikely to be something that distros can do. Their specialities don’t include the kernel.

[rubi1200]

Considering the original poster had indicated their issue was resolved and we try to avoid reviving old topics, the reply and following response have been moved to the Lounge.

This is a better place for such general discussions.

Thanks

[ericmarceau]

Given the need to use a SWAPFILE for the “hibernate” function, can I ask for comments regarding the benefit of having/sharing a script like the one I posted on the UbuntuMATE discourse site?

As for other aspects of the “Sleep” service, I’ve tried to identify the “built-in” tools that give End Users control over their machines but, while reference material is out there, there doesn’t seem to be a distilled “neat” packaging or presentation of that material from the standpoint of ease of use for Windows “immigrants” focused on “just making use” of their computers, not playing OS mechanics with them.

[ne29914]

I’ve never had success with using a swap file for hibernation. A swap partition works every time, though. The setup is a bit involved, and you need to create the partition of course.

[ericmarceau]

So, I tried hibernate with an assigned physical partition:

When I entered

sudo systemctl hibernate

there was no apparent action, screen blink or otherwise. It is like nothing happened!

sudo systemctl status sleep.target hibernate.target

gives me the following:

○ sleep.target - Sleep
     Loaded: loaded (/lib/systemd/system/sleep.target; static)
     Active: inactive (dead) since Mon 2025-12-01 12:49:29 EST; 1min 56s ago
       Docs: man:systemd.special(7)

Dec 01 12:49:28 OasisMega1 systemd[1]: Reached target Sleep.
Dec 01 12:49:29 OasisMega1 systemd[1]: Stopped target Sleep.

○ hibernate.target - System Hibernation
     Loaded: loaded (/lib/systemd/system/hibernate.target; static)
     Active: inactive (dead)
       Docs: man:systemd.special(7)

Dec 01 12:49:29 OasisMega1 systemd[1]: Dependency failed for System Hibernation.
Dec 01 12:49:29 OasisMega1 systemd[1]: hibernate.target: Job hibernate.target/start failed with result 'dependency'.

Examining the “syslog” messages, I see the following:

Dec  1 12:49:28 OasisMega1 ModemManager[1339]: <info>  [sleep-monitor-systemd] system is about to suspend
Dec  1 12:49:28 OasisMega1 NetworkManager[1024]: <info>  [1764611368.5322] manager: sleep: sleep requested (sleeping: no  enabled: yes)
Dec  1 12:49:28 OasisMega1 systemd[1]: Reached target Sleep.
Dec  1 12:49:28 OasisMega1 systemd[1]: Starting Record successful boot for GRUB...
Dec  1 12:49:28 OasisMega1 systemd[1]: Starting Hibernate...
Dec  1 12:49:28 OasisMega1 systemd[1]: Stopping Atop advanced performance monitor...
Dec  1 12:49:28 OasisMega1 run-parts[4868]: run-parts: executing /lib/systemd/system-sleep/atop-pm pre
Dec  1 12:49:28 OasisMega1 systemd[1]: grub-common.service: Deactivated successfully.
Dec  1 12:49:28 OasisMega1 systemd[1]: Finished Record successful boot for GRUB.
Dec  1 12:49:28 OasisMega1 systemd[1]: Starting GRUB failed boot detection...
Dec  1 12:49:29 OasisMega1 systemd[1]: atop.service: Deactivated successfully.
Dec  1 12:49:29 OasisMega1 systemd[1]: Stopped Atop advanced performance monitor.
Dec  1 12:49:29 OasisMega1 run-parts[4868]: run-parts: executing /lib/systemd/system-sleep/hdparm pre
Dec  1 12:49:29 OasisMega1 run-parts[4868]: run-parts: executing /lib/systemd/system-sleep/unattended-upgrades pre
Dec  1 12:49:29 OasisMega1 systemd[1]: grub-initrd-fallback.service: Deactivated successfully.
Dec  1 12:49:29 OasisMega1 systemd[1]: Finished GRUB failed boot detection.
Dec  1 12:49:29 OasisMega1 s2disk[4881]: s2disk: Invalid resume device. Reason: Success
Dec  1 12:49:29 OasisMega1 systemd[1]: systemd-hibernate.service: Main process exited, code=exited, status=22/n/a
Dec  1 12:49:29 OasisMega1 systemd[1]: systemd-hibernate.service: Failed with result 'exit-code'.
Dec  1 12:49:29 OasisMega1 ModemManager[1339]: <info>  [sleep-monitor-systemd] system is resuming
Dec  1 12:49:29 OasisMega1 systemd[1]: Failed to start Hibernate.
Dec  1 12:49:29 OasisMega1 systemd[1]: Dependency failed for System Hibernation.
Dec  1 12:49:29 OasisMega1 systemd[1]: hibernate.target: Job hibernate.target/start failed with result 'dependency'.
Dec  1 12:49:29 OasisMega1 systemd[1]: Stopped target Sleep.
Dec  1 12:49:29 OasisMega1 NetworkManager[1024]: <info>  [1764611369.1912] manager: sleep: wake requested (sleeping: yes  enabled: yes)
Dec  1 12:49:29 OasisMega1 systemd-networkd[506]: enp2s0: Reset carrier
Dec  1 12:49:29 OasisMega1 systemd-networkd[506]: lo: Reset carrier

Examining “dmesg”, we see the following reported:

[    0.037443] kernel: PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
[    0.037445] kernel: PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
[    0.037447] kernel: PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000e5fff]
[    0.037448] kernel: PM: hibernation: Registered nosave memory: [mem 0x000e6000-0x000fffff]
[    0.037451] kernel: PM: hibernation: Registered nosave memory: [mem 0xcff90000-0xcffa7fff]
[    0.037452] kernel: PM: hibernation: Registered nosave memory: [mem 0xcffa8000-0xcffcffff]
[    0.037453] kernel: PM: hibernation: Registered nosave memory: [mem 0xcffd0000-0xcfffffff]
[    0.037455] kernel: PM: hibernation: Registered nosave memory: [mem 0xd0000000-0xffefffff]
[    0.037456] kernel: PM: hibernation: Registered nosave memory: [mem 0xfff00000-0xffffffff]
[    0.037459] kernel: [mem 0xd0000000-0xffefffff] available for PCI devices

***

[    0.049341] kernel: PM: hibernation: Registered nosave memory: [mem 0xc8000000-0xcbffffff]

From the “kern.log”, we see

Dec  1 12:41:21 OasisMega1 kernel: [    0.037443] PM: hibernation: Registered nosave memory: [mem 0x00000000-0x00000fff]
Dec  1 12:41:21 OasisMega1 kernel: [    0.037445] PM: hibernation: Registered nosave memory: [mem 0x0009f000-0x0009ffff]
Dec  1 12:41:21 OasisMega1 kernel: [    0.037447] PM: hibernation: Registered nosave memory: [mem 0x000a0000-0x000e5fff]
Dec  1 12:41:21 OasisMega1 kernel: [    0.037448] PM: hibernation: Registered nosave memory: [mem 0x000e6000-0x000fffff]
Dec  1 12:41:21 OasisMega1 kernel: [    0.037451] PM: hibernation: Registered nosave memory: [mem 0xcff90000-0xcffa7fff]
Dec  1 12:41:21 OasisMega1 kernel: [    0.037452] PM: hibernation: Registered nosave memory: [mem 0xcffa8000-0xcffcffff]
Dec  1 12:41:21 OasisMega1 kernel: [    0.037453] PM: hibernation: Registered nosave memory: [mem 0xcffd0000-0xcfffffff]
Dec  1 12:41:21 OasisMega1 kernel: [    0.037455] PM: hibernation: Registered nosave memory: [mem 0xd0000000-0xffefffff]
Dec  1 12:41:21 OasisMega1 kernel: [    0.037456] PM: hibernation: Registered nosave memory: [mem 0xfff00000-0xffffffff]
Dec  1 12:41:21 OasisMega1 kernel: [    0.037459] [mem 0xd0000000-0xffefffff] available for PCI devices

***

Dec  1 12:41:21 OasisMega1 kernel: [    0.049341] PM: hibernation: Registered nosave memory: [mem 0xc8000000-0xcbffffff]

Since I specified a dedicated swap partition, as seen here,

My /etc/fstab file has the following entry:

UUID=d6818877-fcce-4e10-b45c-17d5bf4670b8       none 		swap 	sw,pri=99	0 	0

My /etc/default/grub file has the following set:

GRUB_CMDLINE_LINUX_DEFAULT="resume=UUID=d6818877-fcce-4e10-b45c-17d5bf4670b8 quiet splash scsi_mod.use_blk_mq=1 usb-storage.quirks=1058:25ee:u usbcore.autosuspend=-1 ipv6.disable=1"

Note that there is no “resume_offset” value assignment.

The contents of /etc/initramfs-tools/conf.d/resume are as follows:

RESUME=UUID=d6818877-fcce-4e10-b45c-17d5bf4670b8

The contents of /etc/systemd/sleep.conf are as follows:

[Sleep]
#AllowSuspend=yes
AllowSuspend=yes

#AllowHibernation=yes
AllowHibernation=yes

#AllowSuspendThenHibernate=yes
AllowSuspendThenHibernate=yes

#AllowHybridSleep=yes
### REF: https://forum.garudalinux.org/t/suspend-and-hibernate-work-correctly-but-suspend-then-hibernate-hangs-for-5-minutes/27586
AllowHybridSleep=no

#SuspendMode=
SuspendMode=suspend

#SuspendState=mem standby freeze
SuspendState=mem freeze disk

#HibernateMode=platform shutdown
HibernateMode=platform shutdown

#HibernateState=disk
HibernateState=disk

#HybridSleepMode=suspend platform shutdown
HybridSleepMode=suspend platform shutdown

#HybridSleepState=disk
HybridSleepState=disk

### suspend for 15 minutes then, if not revived, hibernate 
HibernateDelaySec=900

The contents of /etc/systemd/logind.conf are as follows:

[Login]

#HandleSuspendKey=suspend
HandleSuspendKey=suspend-then-hibernate

#HandleHibernateKey=hibernate
HandleHibernateKey=hibernate

#HandleLidSwitch=suspend
HandleLidSwitch=suspend-then-hibernate

I do not have “Secure Boot”, neither the capability nor enabled.

Can anyone tell me where I went wrong?

[ne29914]

First open a terminal and run the commands:
lsblk
and
blkid

Post the results.

[ericmarceau]

Thank you for looking into this …

For lsblk:

NAME    MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
loop0     7:0    0  13.4M  1 loop /snap/canonical-livepatch/364
loop1     7:1    0     4K  1 loop /snap/bare/5
loop2     7:2    0 183.4M  1 loop /snap/chromium/3293
loop3     7:3    0 175.2M  1 loop /snap/chromium/3313
loop4     7:4    0  55.5M  1 loop /snap/core18/2959
loop5     7:5    0  55.5M  1 loop /snap/core18/2976
loop6     7:6    0  63.8M  1 loop /snap/core20/2669
loop7     7:7    0  63.8M  1 loop /snap/core20/2682
loop8     7:8    0  73.9M  1 loop /snap/core22/2139
loop9     7:9    0    74M  1 loop /snap/core22/2163
loop10    7:10   0  66.8M  1 loop /snap/core24/1225
loop11    7:11   0  48.8M  1 loop /snap/cups/1127
loop12    7:12   0  48.8M  1 loop /snap/cups/1130
loop13    7:13   0 218.4M  1 loop /snap/gnome-3-34-1804/93
loop14    7:14   0 218.4M  1 loop /snap/gnome-3-34-1804/90
loop15    7:15   0 349.7M  1 loop /snap/gnome-3-38-2004/140
loop16    7:16   0   516M  1 loop /snap/gnome-42-2204/202
loop17    7:17   0 349.7M  1 loop /snap/gnome-3-38-2004/143
loop18    7:18   0 516.2M  1 loop /snap/gnome-42-2204/226
loop19    7:19   0 669.8M  1 loop /snap/gnome-46-2404/145
loop20    7:20   0  74.5M  1 loop /snap/gs/x1
loop21    7:21   0  81.3M  1 loop /snap/gtk-common-themes/1534
loop22    7:22   0  91.7M  1 loop /snap/gtk-common-themes/1535
loop23    7:23   0   395M  1 loop /snap/mesa-2404/1165
loop24    7:24   0  50.8M  1 loop /snap/snapd/25202
loop25    7:25   0  50.9M  1 loop /snap/snapd/25577
loop26    7:26   0    16K  1 loop /snap/software-boutique/57
loop27    7:27   0    16K  1 loop /snap/software-boutique/54
loop28    7:28   0  13.5M  1 loop /snap/ubuntu-mate-welcome/720
loop29    7:29   0  13.5M  1 loop /snap/ubuntu-mate-welcome/726
sda       8:0    0 465.8G  0 disk 
├─sda1    8:1    0 463.8G  0 part /site/DB003_F1
└─sda2    8:2    0     2G  0 part [SWAP]
sdb       8:16   0   1.8T  0 disk 
├─sdb1    8:17   0     1G  0 part 
├─sdb2    8:18   0     1G  0 part 
├─sdb3    8:19   0 195.3G  0 part /
├─sdb4    8:20   0  93.5G  0 part /DB001_F8
├─sdb5    8:21   0     6G  0 part [SWAP]
├─sdb7    8:23   0   293G  0 part /DB001_F2
├─sdb8    8:24   0   293G  0 part /DB001_F3
├─sdb9    8:25   0   293G  0 part /DB001_F4
├─sdb10   8:26   0 996.2M  0 part [SWAP]
├─sdb11   8:27   0 996.2M  0 part [SWAP]
├─sdb12   8:28   0 195.3G  0 part /DB001_F5
├─sdb13   8:29   0 195.3G  0 part /DB001_F6
└─sdb14   8:30   0   293G  0 part /DB001_F7
sr0      11:0    1  1024M  0 rom  

For blkid:

/dev/sdb5: LABEL="HIBERNATE" UUID="d6818877-fcce-4e10-b45c-17d5bf4670b8" TYPE="swap" PARTLABEL="HIBERNATE" PARTUUID="864badb5-67f8-464a-9f7e-244b9de7243e"
/dev/sdb3: LABEL="DB001_F1" UUID="5dcf1a96-fa2e-42f5-9a08-37fcce0f0878" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="DB001_F1" PARTUUID="b029db3b-abff-4f60-bbce-180ec1492693"
/dev/loop1: TYPE="squashfs"
/dev/loop29: TYPE="squashfs"
/dev/loop19: TYPE="squashfs"
/dev/loop27: TYPE="squashfs"
/dev/loop17: TYPE="squashfs"
/dev/loop8: TYPE="squashfs"
/dev/loop25: TYPE="squashfs"
/dev/sdb4: LABEL="DB001_F8" UUID="46fcb33d-5f0d-423b-b6a7-512c58c76aba" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="DB001_F8" PARTUUID="14af70ad-19ff-43e4-9879-22b41cc06f62"
/dev/sdb10: UUID="3b9a2c7a-67d4-4de7-ae66-214937dc47f4" TYPE="swap" PARTLABEL="DB001_S2" PARTUUID="f49c79c1-c02f-43eb-8248-52744478fbbb"
/dev/sdb2: UUID="266efd3e-f04d-4ea3-89e6-45e6ac227fa1" TYPE="swap" PARTLABEL="DB001_S1" PARTUUID="c8ce3896-546e-483f-9631-005667dbec66"
/dev/sdb9: LABEL="DB001_F4" UUID="7f37ffd4-779a-46c6-b440-f384fb75eb98" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="DB001_F4" PARTUUID="3e93c152-a155-4dc5-abc7-584548196527"
/dev/sdb7: LABEL="DB001_F2" UUID="7e9a663e-ff1d-4730-8544-c37519056b6f" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="DB001_F2" PARTUUID="f79b4cc4-0626-452c-a153-0b45cc05ca74"
/dev/sdb13: LABEL="DB001_F6" UUID="0d416936-e091-49a7-9133-b8137d327ce0" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="DB001_F6" PARTUUID="02bd10de-e2bb-4d64-98ab-20123774cfab"
/dev/sdb11: UUID="78b04c8c-8ace-4b46-817d-7059aa1668b7" TYPE="swap" PARTLABEL="DB001_S3" PARTUUID="41403fb3-7ca9-45ba-958c-13c690ccbbbd"
/dev/sdb1: PARTLABEL="GRUB" PARTUUID="fe082f38-212d-4218-95a4-3e8b56bb942f"
/dev/sdb8: LABEL="DB001_F3" UUID="4f7d4192-b136-4a94-b06b-736f76155816" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="DB001_F3" PARTUUID="40bfd875-e5c5-430e-9164-f88aa0bb5f4e"
/dev/sdb14: LABEL="DB001_F7" UUID="c2ff9e15-b50e-4c56-9c03-918bf81e0ab5" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="DB001_F7" PARTUUID="054d4618-cedf-4d70-b833-433349a87fee"
/dev/sdb12: LABEL="DB001_F5" UUID="14e15125-6c47-499e-b1a9-734a0f928b5e" BLOCK_SIZE="4096" TYPE="ext4" PARTLABEL="DB001_F5" PARTUUID="351f9dc4-80ea-444f-bac3-9392f466ce2e"
/dev/loop15: TYPE="squashfs"
/dev/loop6: TYPE="squashfs"
/dev/loop23: TYPE="squashfs"
/dev/loop13: TYPE="squashfs"
/dev/loop4: TYPE="squashfs"
/dev/loop21: TYPE="squashfs"
/dev/loop11: TYPE="squashfs"
/dev/loop2: TYPE="squashfs"
/dev/loop0: TYPE="squashfs"
/dev/loop28: TYPE="squashfs"
/dev/loop18: TYPE="squashfs"
/dev/loop9: TYPE="squashfs"
/dev/loop26: TYPE="squashfs"
/dev/loop16: TYPE="squashfs"
/dev/loop7: TYPE="squashfs"
/dev/loop24: TYPE="squashfs"
/dev/sda2: LABEL="DB003_S1" UUID="b9aa2a71-9430-4011-a955-9451d7f2c421" TYPE="swap" PARTUUID="b660a43d-02"
/dev/sda1: UUID="56521faa-ded9-493f-a0b9-c6a8d68183e9" BLOCK_SIZE="4096" TYPE="ext4" PARTUUID="b660a43d-01"
/dev/loop14: TYPE="squashfs"
/dev/loop5: TYPE="squashfs"
/dev/loop22: TYPE="squashfs"
/dev/loop12: TYPE="squashfs"
/dev/loop3: TYPE="squashfs"
/dev/loop20: TYPE="squashfs"
/dev/loop10: TYPE="squashfs"

[ne29914]

Ouch!
I’m totally overwhelmed. You apparently have a snap installation, of which I have no experience at all. I see four (!) swap partitions, but assume that sdb5 is the one your want for hibernation.
I’ve consciously avoided snap and disable snapd on every new installation.
I’m afraid I can’t help any further.
I can offer the following: send me a PM with your email, and I’ll send you a document I’ve created for doing new installs. It includes a hibernate setup section. But whether it’s compatible with snap is an open question.

[ericmarceau]

sda is the 500 GB disk on which I have installed a test image of the UM 26.04 LTS daily build of Nov 19 2025. Sticking with basic default “overwrite everything” (no customized partitioning), all went very well. Operates lik a charm!

sdb is the 2 TB disk, which is my daily driver with UM 22.04.5 LTS image. I have the 4 SWAP partitions and 7 data partitions ( /DB001_F2 thru /DB001_F8, /DB001_F1 being a symlink to / ), each partition dedicated to a functional purpose, and keeping root as purely OS as possible.

• /DB001_F2       Software (old and current scripts) and real location of standard HOME sub-folders; Repository for electronic versions of all paperback novels that I previously owned and purged
• /DB001_F3       Movie/Video files library
• /DB001_F4       Personal files; S/W coding work files & samples; Career legacy files; workspace for scanning and conversion/OCR
• /DB001_F5       Books and documentation on any/all topics general/society/history/geography/politics/conflict/software/systems
• /DB001_F6       Music file repository
• /DB001_F7       Sizable “spare room” for performing operations with large numbers of files
• /DB001_F8       Leftovers from earlier Windows/Ubuntu migrations that need to be reviewed and distilled for critical info.

My thinking with having the multiple 1 GB SWAP partitions was that if they were all online, when there was a need for swap, the system might speed up the swapping process by writing to all swap partitions at the same time, increasing the swap thruput to/from disk. I don’t know if the Kernel is smart enough to do that, but that was my thinking.

My partitions as specifically named/labelled, in order to facilitate actions with my various scripts, available from

• Eric Marceau @ GitHub

I only have SNAP for those pieces of Ubuntu which I am forced to accept. If those are removed, I am told that the OS will not function properly for boot or upgrades.

# snap list

Name                 Version                         Rev    Tracking         Publisher      Notes
bare                 1.0                             5      latest/stable    canonical✓     base
canonical-livepatch  10.11.9                         364    latest/stable    canonical✓     -
chromium             142.0.7444.175                  3313   latest/stable    canonical✓     -
core18               20251029                        2976   latest/stable    canonical✓     base
core20               20250822                        2682   latest/stable    canonical✓     base
core22               20251009                        2163   latest/stable    canonical✓     base
core24               20251001                        1225   latest/stable    canonical✓     base
cups                 2.4.12-2                        1130   latest/stable    openprinting✓  -
gnome-3-34-1804      0+git.3556cb3                   93     latest/stable    canonical✓     -
gnome-3-38-2004      0+git.efb213a                   143    latest/stable    canonical✓     -
gnome-42-2204        0+git.837775c-sdk0+git.7b07595  226    latest/stable    canonical✓     -
gnome-46-2404        0+git.df85349-sdk0+git.54e4d8f  145    latest/stable    canonical✓     -
gs                   10.02.1                         x1     -                -              devmode
gtk-common-themes    0.1-81-g442e511                 1535   latest/stable    canonical✓     -
mesa-2404            25.0.7-snap211                  1165   latest/stable    canonical✓     -
snapd                2.72                            25577  latest/stable    canonical✓     snapd
software-boutique    0+git.0fdcecc                   57     latest/stable/…  flexiondotorg  classic
ubuntu-mate-welcome  22.04.0-d3d4bb1a                726    latest/stable/…  flexiondotorg  classic

[ne29914]

The only package I see that needs snap is Chromium. If that’s a must for you, so be it.
Just for fun, here’s the output of my lsblk command (it’s a laptop):

mac24@dk6910p:~$ lsblk
NAME   MAJ:MIN RM   SIZE RO TYPE MOUNTPOINTS
sda      8:0    0 223,6G  0 disk 
├─sda1   8:1    0     8M  0 part 
├─sda2   8:2    0  29,3G  0 part /
├─sda3   8:3    0 188,4G  0 part /home
└─sda4   8:4    0   5,9G  0 part [SWAP]
sr0     11:0    1  1024M  0 rom 

[ericmarceau]

I appreciate the feedback, but how does that relate to hibernation and the SWAP partition being configured for it?

[ne29914]

It’s just a silly comparison snap/non-snap (complexity/simplicity).
Check your email.

Cheers.

[paddylandau]

@ne29914

You apparently have a snap installation

This has nothing to do with it. Snap is just another program like flatpak. It creates extra mounts, yes, but for the purposes of this thread, you can ignore it.

[paddylandau]

@ericmarceau

I only have SNAP for those pieces of Ubuntu which I am forced to accept. If those are removed, I am told that the OS will not function properly for boot or upgrades.

It depends on what you’re using snap for. If you use Livepatch, you must use snap. There are alternatives for almost everything else.

However, you don’t have to remove snap. This doesn’t affect hibernation or swap files in the slightest.

As long as you aren’t using Secure Boot, it’s possible to enable hibernation. Unfortunately, I haven’t done this in several years (I always use Secure Boot), so I don’t know how it’s done these days.

[ogra]

@paddylandau

There are alternatives for almost everything else.

Well, if you use TPM based full disk encryption your kernel comes as a snap

[paddylandau]

@ogra

if you use TPM based full disk encryption your kernel comes as a snap

I thought that this was still in development! It’s good to know that it’s now available.

On a side note, I’m still looking forward to trying out Ubuntu Core Desktop. It has quite a lot of competition out there right now, so I hope that it arrives soon. It was due by the end of this year, but it’s obviously not going to happen.