Andrew's questions

I just encrypted my swap file and now after a reboot I see two devices with "swap" listed when I run blkid:

/dev/loop0: UUID="82a141ee-b1fd-4d52-a1fb-c0690bed732e" TYPE="swap"
/dev/mapper/cryptswap1: UUID="3c73ab32-331e-47e7-8cb9-79f82ab41f5d" TYPE="swap"

Does this mean I have two swap files, one encrypted and one not, or is this normal with encrypted swap?

My /etc/fstab only lists one:

# /etc/fstab: static file system information.
#
# Use 'blkid' to print the universally unique identifier for a
# device; this may be used with UUID= as a more robust way to name devices
# that works even if disks are added and removed. See fstab(5).
#
# <file system> <mount point>   <type>  <options>       <dump>  <pass>
# / was on /dev/nvme0n1p2 during installation
UUID=6135b409-f997-4289-895e-a0abb0617c2b /               ext4    errors=remount-ro 0       1
# /boot/efi was on /dev/nvme0n1p1 during installation
UUID=757B-FF35  /boot/efi       vfat    umask=0077      0       1
#/swapfile none            swap    sw              0       0
/dev/mapper/cryptswap1 none swap sw 0 0

As does my /etc/crypttab:

# <target name> <source device>         <key file>      <options>
cryptswap1 /swapfile /dev/urandom swap,offset=1024,cipher=aes-xts-plain64

And fdisk -lu lists them both as having 4GiB:

Disk /dev/loop0: 4 GiB, 4294967296 bytes, 8388608 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Disk /dev/mapper/cryptswap1: 4 GiB, 4294443008 bytes, 8387584 sectors
Units: sectors of 1 * 512 = 512 bytes
Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

Ubuntu 18.04 Thinkpad X1 Carbon 5th Gen

When I click the shutdown button in the menu bar, Ubuntu occasionally hangs for ~30 seconds before opening the Shutdown/Reboot/Cancel window. I haven't been able to find a culprit and I haven't found another post with this exact problem. I replicated the problem and captured the system log for the period of time that the computer was frozen below. 16:12:09 was before I clicked the shutdown button and it hung until about 12:42. The final line from 12:47 was after I regained control of the computer.

When this happens, I can ctrl+alt+F1, which returns me to the login screen and I can ctrl+alt+F7, but it doesn't open a terminal that I can interact with. I can still move the mouse, but I can't click on anything or type anything.

Any suggestions of how to fix this problem?

Thank you

May 16 16:12:09 kernel: [  519.281393] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=54:e1:ad:a7:48:05:70:54:d2:7f:14:78:08:00 SRC=128.223.43.197 DST=128.223.43.178 LEN=406 TOS=0x00 PREC=0x00 TTL=128 ID=30847 PROTO=UDP SPT=1900 DPT=52108 LEN=386  
May 16 16:12:18 at-spi2-registr[2706]: Failed to send session response Timeout was reached 
May 16 16:12:28 kernel: [  538.725747] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=54:e1:ad:a7:48:05:70:54:d2:7f:14:78:08:00 SRC=128.223.43.197 DST=128.223.43.178 LEN=304 TOS=0x00 PREC=0x00 TTL=128 ID=30854 PROTO=UDP SPT=1900 DPT=52108 LEN=284  
May 16 16:12:42 gnome-session-binary[2602]: Entering running state 
May 16 16:12:42 gnome-shell[2742]: Ignored exception from dbus method: Gio.IOErrorEnum: GDBus.Error:org.gtk.GDBus.UnmappedGError.Quark._g_2dio_2derror_2dquark.Code19: Operation was cancelled 
May 16 16:12:42 gnome-shell[2742]: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor2 
May 16 16:12:42 gnome-shell[2742]: gnome-session gave us a dead inhibitor: /org/gnome/SessionManager/Inhibitor3 
May 16 16:12:47 kernel: [  557.813435] [UFW BLOCK] IN=enp0s31f6 OUT= MAC=54:e1:ad:a7:48:05:70:54:d2:7f:14:78:08:00 SRC=128.223.43.197 DST=128.223.43.178 LEN=406 TOS=0x00 PREC=0x00 TTL=128 ID=30863 PROTO=UDP SPT=1900 DPT=52108 LEN=386