D-Bus notification failed: Transport endpoint is not connected [was System always "Resumes from hibernation" on startup]

I would bet that if you "cat /proc/cmdline" you will see a resume= parameter, but even if not this may be the default. At any rate, it doesn't look like your resume attempt is the reason for the delay, as the delay has already occurred when the resume is attempted: Jun 30 12:19:40 amito kernel: Console: switching to colour frame buffer device 240x75         <Note 1:28 minute Delay> Jun 30 12:21:08 amito dracut-initqueue[526]: WARNING: D-Bus notification failed: Transport endpoint is not connected Note that delay has already occurred at this point. Jun 30 12:21:08 amito systemd[1]: Found device /dev/mapper/fedora- swap. Jun 30 12:21:08 amito systemd[1]: Starting Resume from hibernation using device /dev/mapper/fedora-swap... Jun 30 12:21:08 amito systemd-hibernate-resume[547]: Could not resume from '/dev/mapper/fedora-swap' (253:1). ...and the resume failure is a second or less after the attempted resume starts. On Thu, Jul 1, 2021 at 8:14 AM Jonathan Ryshpan <jonrysh(a)pacbell.net&gt; wrote: > ... > System configuration"   >    Operating System: Fedora 34 >    KDE Plasma Version: 5.22.2 >    KDE Frameworks Version: 5.83.0 >    Qt Version: 5.15.2 >    Kernel Version: 5.12.13-300.fc34.x86_64 (64-bit) >    Graphics Platform: Wayland >    Processors: 8 × Intel® Core™ i7-4790K CPU @ 4.00GHz >    Memory: 15.5 GiB of RAM >    Graphics Processor: Mesa DRI Intel® HD Graphics 4600