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

[Jonathan Ryshpan <jonrysh@xxxxxxxxxxx>]

On Fri, 2021-07-09 at 08:18 -0700, Jonathan Ryshpan wrote:

On Thu, 2021-07-01 at 08:25 -0600, Greg Woods wrote:

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@xxxxxxxxxxx> 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

GW is correct.  I recreated the swap partition ($ swapoff -a; $ mkswap; $ swapon -a) and the problem persisted.  Then I examined the full system log, which goes back to Thu 2020-07-09.  There a large number of entries like 

Starting Resume from hibernation using device /dev/mapper/fedora-swap...

none of which is associated with a delay

However there are no entries like

WARNING: D-Bus notification failed: Transport endpoint is not connected

until 2021-06-30, about a year.  After the first one appears, there is one following each reboot, and each is associated with a delay, generally, but not always, about 1 minute 28 seconds.

The system was upgraded from Fedora-33 to Fedora-34 on 2021-05-25, so there may be some connection.  I don't see anything on the web about this kind of error.  Can anyone enlighten me.

This is a known bug.  See: https://bugzilla.redhat.com/show_bug.cgi?id=1976653

-- 

Sincerely Jonathan Ryshpan <jonrysh@xxxxxxxxxxx>

	Power tends to corrupt.  Absolute power tends to
	corrupt absolutely.  -- Lord Acton

_______________________________________________
users mailing list -- users@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to users-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/users@xxxxxxxxxxxxxxxxxxxxxxx
Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure