Hi, everyone.

Recently, I got a problem.

After updating latest security update, some of my Slackware system no
more boot promptly.

Concretely, when the system boots up, it hangs where rc.messagebus is
called, and it indefinitely waits somethings I don't understand. And
it merely echoes the message:

"Starting system message bus: /usr/bin/dbus-uuidgen --ensure ; /usr/bin/dbus-daemon --system"

By the way, I use runlevel 3.

At first, I thought that my laptop is somewhat broken, so I
reinstalled Slackware, but the problem was same.

To find what causes the problem, I installed a fresh Slackware64 14.2,
and installed security packages one by one, and figured out that the
latest expat package (expat-2.2.2-x86_64-1_slack14.2) causes the
problem.

And there's a few more thing I've found:

1. Not all of my Slackware system do suffer this symptom; what's
in common of the troubled system is that they are capable of EFI. I
also turned from elilo to traditional lilo, but it didn't help.

2. If a USB flash is inserted during the boot process, it boots
normally as usual (I tested this behavior with my Slackware
installation USB).

3. There's a workaround, that is, if I switch a virtual console by
pressing ALT-F2, and then ALT-F1, then the system resumes where it
suspended (rc.messagebus).


Is there anyone else having this problem? And if so it is, what
went wrong with the latest expat package?

I've been using Slackware since ver 2.3, and I definitely don't want
lose my faith.

Regards,
Sungjin

Yes, same problem here (but on BIOS machine, no EFI)
I work around the problem by getting rid of dbus, but I understand it's not an option for many others who depend on it.

Hello,

Found this bug report.

--
SeB

3 members found this post helpful.

OK. Then I'll wait for a bug fix.

Thank you for your help.

Attempted fix is up now. It's only in 14.2 and -current since I don't think anything else should be affected -- only those try to use (and could be blocked from using) kernel based entropy with the newest expat library. Oddly enough, I was never able to reproduce this issue here and only got a few reports of it, so it must be a fairly hardware-dependent thing.

5 members found this post helpful.

Thanks, can confirm this patch resolves the issue on slackware-14.2 and slackware64-14.2

Thanks. the updated dbus patch solves the problem.