I just upgraded my Slack-current system - which usually goes well, I might add - but this time when I rebooted, I got down to the line that says :

Starting hal daemon: /usr/sbin/hald --daemon=yes --retain privileges
Dbus is already running (will not start it twice).
Starting hal daemon: /usr/sbin/hald --daemon=yes

Then the machine sits there for about three minutes, then I get to a login screen normally (runlevel 4)). I'm also using DLGnome... if that matters.

Thanks!

Ya it does matter because DLG installed HAL and Dbus.

All gnomes on the face of the planet install hal and dbus.(even on FreeBSD, hal just doesn't get used)

The gnomes for slackware were created and linked against packages in 10.2. They will not work with current usually.(none of the gnome desktops will)

I reinstalled DLGnome and have the same problem - I was hoping that it would go away.

As liquidtenmilion said, Dropline GNOME is only supported on Slackware 10.2 and not "current". Having said that, you might get more help about your problem by posting on the Dropline Forums.

What version of DLG are you using? I'm using Dropline GNOME 2.12.2 and Slackware 10.2, booting to runlevel 3, and this does not occur on my PC.

The "Dbus is already running" message sounds a little "wierd", what is in your /etc/rc.d/rc.local script?

Later,
MMYoung

/etc/rc.d/rc.local:

#!/bin/sh
#
# /etc/rc.d/rc.local: Local system initialization script.
#
# Put any local setup commands in here:

if [ -x /etc/rc.d/rc.messagebus ]; then
if [ -w /var/run/dbus/dbus.pid ]; then
rm /var/run/dbus/dbus.pid
fi
sh /etc/rc.d/rc.messagebus start
fi

if [ -x /etc/rc.d/rc.hald ]; then
sh /etc/rc.d/rc.hald start
fi

if [ -x /etc/rc.d/rc.howl ]; then
sh /etc/rc.d/rc.howl start
fi


ntpdate 128.59.59.177




# Delete pam_console lock and refcount files
rm -f /var/run/console/*

My rc.local file doesn't have anything in it about rc.messagebus or rc.hald, but I am running DLG 2.12.2 (latest release). I do have an old PC setting around that has DLG 2.12.1 on it and the rc.local file contains the following:
You didn't answer my question about which version of DLG you are running, but according to your profile you are using 2.12.1. If you are using 2.12.2 (latest release) your rc.local doesn't need to have anything in it about rc.messagebus or rc.hal.

HTH,
MMYoung

I'm sorry, I am running 2.12.2, but haven't updated my signature yet... thank you for your reply - I'll try a blank rc.local and see what happens...

The thing is when you installed/upgraded DLG-2.12.2 it *should've* cleared any references to rc.hal and rc.messagebus from your rc.local file. If it didn't you really need to post this to the DLG Forums as this could be a potential bug in the way the install/upgrade runs.

BTW, only GNOME uses messagebus/hal now, but it's on the way for KDE.

(edit)Be sure and leave the pam_console lock script in rc.local(end edit)

Later,
MMYoung

I left the reference to pam, ntpupdate and howl and commented out the rest - and things are fine now, normal boot-up.

It occurs to me that I used to run FRGnome and/or Gware.... this may have been a holdover from then - until I discovered DLGnome.

Thanks for your help! Merry Christmas!

No problem, glad you got it straightened out.

Later,
MMYoung

This is correct. Dropline's latest HAL and Dbus updates utilize sysvinit for the execution of HAL and Dbus daemons. We're attempting to avoid making any modifications to any existing files now (that includes rc.local), and will be utilizing sysvinit instead for future updates. This way, we never have to add anything to rc.local again.

On a slightly contradictory related note... The new HAL and Dbus attempts to remove any previous entries that our packages created in rc.local, but will ignore anything that a user might have manually added (in your case, anything that was there from FRG or Gware). 2.14.0 won't be this way; as we're really aiming for the most clean release possible.