Re: D-Bus notification failed: Transport endpoint is not connected [was System always "Resumes from hibernation" on startup]
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 > > > > 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 > > 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 Power tends to corrupt. Absolute power tends to corrupt absolutely. -- Lord Acton ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
D-Bus notification failed: Transport endpoint is not connected [was System always "Resumes from hibernation" on startup]
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 > > 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 > 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. -- Thanks - jon Rich or poor, it's good to have money. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: System always "Resumes from hibernation" on startup
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 > > 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 > 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. -- Sincerely Jonathan Ryshpan "Never try to teach a pig to sing. It wastes time and annoys the pig." ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: System always "Resumes from hibernation" on startup
On Thu, 01 Jul 2021 17:25:30 -0700 Jonathan Ryshpan wrote: > On Thu, 2021-07-01 at 07:26 -0700, stan via users wrote: > > On Thu, 01 Jul 2021 07:13:38 -0700 > > Jonathan Ryshpan wrote: > > > > > The system always tries to restore from hibernation on startup; > > > this causes about a 1-1/2 minute delay. I see no reason for > > > this, since the system is halted by "(Start)->Shut Do..." Here > > > is an extract from the system log with inserted comments. > > > > A long time ago I remember having a problem like this, and it was > > because the kernel had a resume on the command line, telling it to > > try an ancient hibernation on a swap partition. When I removed > > that, it went away. You could interrupt the boot and look at the > > kernel command line, and if it is there remove it before booting to > > see if that is the cause. > > Interesting! Did you remove the "resume=/..." from the command line, > or the ancient hibernation from the swap partition? If the > hibernation, how did you remove it? I removed the resume. I didn't think of removing the image from the swap. This is conjecture, since I haven't done it, but you should be able to swapoff the swap partition, mkswap the swap partition, and swapon the partition again. See man swapon. I don't have the kernel docs handy, but I think the resume parameter is necessary to reboot from swap. Tim could be right, but I recall that it was possible to recover from a faulty hibernate image, or skip it, by removing the resume parameter so that normal boot would take place. I haven't used hibernate for a long time, so memory only, and could be wrong. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: System always "Resumes from hibernation" on startup
On Thu, 2021-07-01 at 12:21 -0400, Tom Horsley wrote: > If you are never going to want to hibernate, do what I do > and remove the resume= from the kernel boot line in grub. Then > it won't even look for a device to resume from. It was my understanding that there didn't need to be a resume parameter on the kernel line to be able to resume, so long as the system could find the swap partition by itself without problems. It was only needed to ensure it found the right one. -- uname -rsvp Linux 3.10.0-1160.31.1.el7.x86_64 #1 SMP Thu Jun 10 13:32:12 UTC 2021 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: System always "Resumes from hibernation" on startup
On Thu, 2021-07-01 at 07:26 -0700, stan via users wrote: > On Thu, 01 Jul 2021 07:13:38 -0700 > Jonathan Ryshpan wrote: > > > The system always tries to restore from hibernation on startup; this > > causes about a 1-1/2 minute delay. I see no reason for this, since > > the system is halted by "(Start)->Shut Do..." Here is an extract > > from the system log with inserted comments. > > A long time ago I remember having a problem like this, and it was > because the kernel had a resume on the command line, telling it to try > an ancient hibernation on a swap partition. When I removed that, it > went away. You could interrupt the boot and look at the kernel command > line, and if it is there remove it before booting to see if that is the > cause. Interesting! Did you remove the "resume=/..." from the command line, or the ancient hibernation from the swap partition? If the hibernation, how did you remove it? -- Many Thanks - Jonathan Ryshpan Honesty may not be the best policy, but it is worth trying once in a while. --Richard Nixon ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: System always "Resumes from hibernation" on startup
If you are never going to want to hibernate, do what I do and remove the resume= from the kernel boot line in grub. Then it won't even look for a device to resume from. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: System always "Resumes from hibernation" on startup
On Thu, 2021-07-01 at 07:13 -0700, Jonathan Ryshpan wrote: > The system always tries to restore from hibernation on startup; this > causes about a 1-1/2 minute delay. I see no reason for this, since > the system is halted by "(Start)->Shut Do..." I was of the understanding that when a system fires up it looks to see if it should be resuming, tries to, then just boots normally if it can't. It just seems to look for suitable resumption data in the swap file, that's its test. If it finds nothing useful there, it cold boots. If what's there has something wrong with it, it cold boots. As has been pointed out by another poster, this attempt is quickly over and done with (both in your logs, and in the normal run of things for other people). -- uname -rsvp Linux 3.10.0-1160.31.1.el7.x86_64 #1 SMP Thu Jun 10 13:32:12 UTC 2021 x86_64 Boilerplate: All unexpected mail to my mailbox is automatically deleted. I will only get to see the messages that are posted to the mailing list. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: System always "Resumes from hibernation" on startup
On Thu, 01 Jul 2021 07:13:38 -0700 Jonathan Ryshpan wrote: > The system always tries to restore from hibernation on startup; this > causes about a 1-1/2 minute delay. I see no reason for this, since > the system is halted by "(Start)->Shut Do..." Here is an extract > from the system log with inserted comments. A long time ago I remember having a problem like this, and it was because the kernel had a resume on the command line, telling it to try an ancient hibernation on a swap partition. When I removed that, it went away. You could interrupt the boot and look at the kernel command line, and if it is there remove it before booting to see if that is the cause. ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
Re: 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 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. --Greg On Thu, Jul 1, 2021 at 8:14 AM Jonathan Ryshpan wrote: > The system always tries to restore from hibernation on startup; this > causes about a 1-1/2 minute delay. I see no reason for this, since the > system is halted by "(Start)->Shut Do..." Here is an extract from the > system log with inserted comments. > > Jun 30 12:19:38 amito dracut-initqueue[523]: inactive > '/dev/fedora/windows' [400.00 GiB] inherit > Jun 30 12:19:38 amito dracut-initqueue[523]: inactive > '/dev/fedora/root' [100.00 GiB] inherit > Jun 30 12:19:38 amito dracut-initqueue[523]: inactive > '/dev/fedora/swap' [24.00 GiB] inherit > Jun 30 12:19:38 amito dracut-initqueue[523]: inactive > '/dev/fedora/home' [<1.31 TiB] inherit > Jun 30 12:19:38 amito systemd[1]: Found device /dev/mapper/fedora-root. > > Jun 30 12:19:38 amito systemd[1]: Reached target Initrd Root Device. > Jun 30 12:19:40 amito kernel: fbcon: Taking over console > Jun 30 12:19:40 amito kernel: Console: switching to colour frame buffer > device 240x75 > > Jun 30 12:21:08 amito dracut-initqueue[526]: WARNING: D-Bus notification > failed: Transport endpoint is not connected > 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). > Jun 30 12:21:08 amito systemd[1]: > systemd-hibernate-resume@dev-mapper-fedora\x2dswap.service: Deactivated > successfully. > Jun 30 12:21:08 amito systemd[1]: Finished Resume from hibernation using > device /dev/mapper/fedora-swap. > Jun 30 12:21:08 amito kernel: PM: Image not found (code -22) > Jun 30 12:21:08 amito kernel: kauditd_printk_skb: 7 callbacks suppressed > > 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 > > -- > Sincerely Jonathan Ryshpan > > But what are all these mysteries to me, > 2 Whose thoughts are full of indices and surds. > X + 7 X + 53 > = 11 / 3. > -- Lewis Carrol > ___ > users mailing list -- users@lists.fedoraproject.org > To unsubscribe send an email to users-le...@lists.fedoraproject.org > 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@lists.fedoraproject.org > Do not reply to spam on the list, report it: > https://pagure.io/fedora-infrastructure > ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
System always "Resumes from hibernation" on startup
The system always tries to restore from hibernation on startup; this causes about a 1-1/2 minute delay. I see no reason for this, since the system is halted by "(Start)->Shut Do..." Here is an extract from the system log with inserted comments. Jun 30 12:19:38 amito dracut-initqueue[523]: inactive '/dev/fedora/windows' [400.00 GiB] inherit Jun 30 12:19:38 amito dracut-initqueue[523]: inactive '/dev/fedora/root' [100.00 GiB] inherit Jun 30 12:19:38 amito dracut-initqueue[523]: inactive '/dev/fedora/swap' [24.00 GiB] inherit Jun 30 12:19:38 amito dracut-initqueue[523]: inactive '/dev/fedora/home' [<1.31 TiB] inherit Jun 30 12:19:38 amito systemd[1]: Found device /dev/mapper/fedora-root. Jun 30 12:19:38 amito systemd[1]: Reached target Initrd Root Device. Jun 30 12:19:40 amito kernel: fbcon: Taking over console Jun 30 12:19:40 amito kernel: Console: switching to colour frame buffer device 240x75 Jun 30 12:21:08 amito dracut-initqueue[526]: WARNING: D-Bus notification failed: Transport endpoint is not connected 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). Jun 30 12:21:08 amito systemd[1]: systemd-hibernate-resume@dev-mapper-fedora\x2dswap.service: Deactivated successfully. Jun 30 12:21:08 amito systemd[1]: Finished Resume from hibernation using device /dev/mapper/fedora-swap. Jun 30 12:21:08 amito kernel: PM: Image not found (code -22) Jun 30 12:21:08 amito kernel: kauditd_printk_skb: 7 callbacks suppressed 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 -- Sincerely Jonathan Ryshpan But what are all these mysteries to me, 2 Whose thoughts are full of indices and surds. X + 7 X + 53 = 11 / 3. -- Lewis Carrol ___ users mailing list -- users@lists.fedoraproject.org To unsubscribe send an email to users-le...@lists.fedoraproject.org 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@lists.fedoraproject.org Do not reply to spam on the list, report it: https://pagure.io/fedora-infrastructure
