I forgot that before the issue started, I tried to log out of my user session which resulted in a black screen and seemed to be stuck. I waited a while and then did a hard reboot. I presume I interrupted a process that caused the issue. I have edited the original post accordingly.
To fix the issue, I went into the KDE Partition Manager GUI, selected the device, right clicked on the partition, and ran the Check process And that fixed the issue!
This is the output I received:
Check and repair partition ‘/dev/sda1’ (931.51 GiB, ext4)
Job: Check file system on partition ‘/dev/sda1’
Command: e2fsck -f -y -v /dev/mapper/luks-4ea2cd3f-8824-23d9-a1a4-cb6b74c02144
e2fsck 1.45.6 (20-Mar-2020)
SSD: recovering journal
JBD2: Invalid checksum recovering block 60293235 in log
Journal checksum error found in SSD
Pass 1: Checking inodes, blocks, and sizes
Pass 2: Checking directory structure
Pass 3: Checking directory connectivity
Pass 4: Checking reference counts
Pass 5: Checking group summary information
Block bitmap differences: +26705922 +26705924 +(26705926--26705927) [... I have omitted a large amount of text here]
Fix? yes
>SSD: ***** FILE SYSTEM WAS MODIFIED *****
102214 inodes used (0.17%, out of 61054976)
1303 non-contiguous files (1.3%)
70 non-contiguous directories (0.1%)
# of inodes with ind/dind/tind blocks: 0/0/0
Extent depth histogram: 101646/538
43977913 blocks used (18.01%, out of 244189696)
0 bad blocks
2 large files
80773 regular files
21397 directories
0 character device files
0 block device files
0 fifos
0 links
35 symbolic links (22 fast symbolic links)
0 sockets
102205 files
Check file system on partition ‘/dev/sda1’: Success
Job: Maximise file system on ‘/dev/sda1’ to fill the partition
The file system on partition ‘/dev/sda1’ already has the requested length of 1,953,521,664 sectors.
Maximise file system on ‘/dev/sda1’ to fill the partition: Success
Check and repair partition ‘/dev/sda1’ (931.51 GiB, ext4): Success