Please always also send your mails to the bugreport.
On Thu, Nov 16, 2006 at 02:13:22PM +0100, Ivan Sergio Borgonovo wrote:
> On Wed, 15 Nov 2006 11:20:35 +0100
> [EMAIL PROTECTED] (Sjoerd Simons) wrote:
>
> > Could you show us how exactly it's not starting properly. I.e. both
> > the output of /etc/init.d/dbus restart and if that doesn't throw
> > clear errors then please run: dbus-daemon --system --nofork
>
> This is an excerpt of /var/log/message
>
> Nov 16 08:09:29 localhost dhcdbd: message_handler: message handler
> not found under /com/redhat/dhcp/et h2 for sub-path
> eth2.dbus.get.reason Nov 16 08:09:29 localhost dhcdbd:
> message_handler: message handler not found under /com/redhat/dhcp/et
> h0 for sub-path eth0.dbus.get.reason Nov 16 08:09:29 localhost
> dhcdbd: message_handler: message handler not found
> under /com/redhat/dhcp/et h0 for sub-path eth0.dbus.get.reason
> ...
> Nov 16 08:09:35 localhost dhcdbd: message_handler: message handler
> not found under /com/redhat/dhcp/et h0 for sub-path
> eth0.dbus.get.nis_domain Nov 16 08:09:35 localhost dhcdbd:
> message_handler: message handler not found under /com/redhat/dhcp/et
> h0 for sub-path eth0.dbus.get.nis_servers
> ...
> Nov 16 08:22:58 localhost dhcdbd: message_handler: message handler
> not found under /com/redhat/dhcp/et h0 for sub-path
> eth0.dbus.get.reason Nov 16 08:22:58 localhost dhcdbd:
> message_handler: message handler not found under /com/redhat/dhcp/et
> h0 for sub-path eth0.dbus.get.reason Nov 16 08:23:00 localhost
> powersaved: Starting powersaved with ACPI support Nov 16 08:23:01
> localhost kernel: Bluetooth: Core ver 2.8 Nov 16 08:23:01 localhost
> kernel: NET: Registered protocol family 31 Nov 16 08:23:01 localhost
> kernel: Bluetooth: HCI device and connection manager initialized Nov
> 16 08:23:01 localhost kernel: Bluetooth: HCI socket layer initialized
> Nov 16 08:23:01 localhost dhcdbd: message_handler: message handler
> not found under /com/redhat/dhcp/et h0 for sub-path
> eth0.dbus.get.nis_domain Nov 16 08:23:01 localhost dhcdbd:
> message_handler: message handler not found under /com/redhat/dhcp/et
> h0 for sub-path eth0.dbus.get.nis_servers
>
> output of
> dark:~# /etc/init.d/dbus restart
> Stopping network events dispatcher: NetworkManagerDispatcher.
> Stopping Avahi mDNS/DNS-SD Daemon: avahi-daemon.
> Stopping network connection manager: NetworkManager.
> Stopping DHCP D-Bus daemon: dhcdbd.
> Stopping Hardware abstraction layer: hald.
> Stopping system message bus: dbus.
> Starting system message bus: dbus.
> Starting Hardware abstraction layer: hald.
> Starting DHCP D-Bus daemon: dhcdbd.
> Starting network connection manager: NetworkManager.
> Starting Avahi mDNS/DNS-SD Daemon: avahi-daemon.
> Starting network events dispatcher: NetworkManagerDispatcher.
>
> message while dbus is manually restarted:
> Nov 16 14:07:51 localhost dhcdbd: Started up.
> Nov 16 14:07:51 localhost dhcdbd: message_handler: message handler
> not found under /com/redhat/dhcp/et h2 for sub-path
> eth2.dbus.get.reason Nov 16 14:07:51 localhost dhcdbd:
> message_handler: message handler not found under /com/redhat/dhcp/et
> h0 for sub-path eth0.dbus.get.reason Nov 16 14:07:51 localhost
> dhcdbd: message_handler: message handler not found
> under /com/redhat/dhcp/et h0 for sub-path eth0.dbus.get.reason Nov 16
> 14:07:54 localhost dhcdbd: message_handler: message handler not found
> under /com/redhat/dhcp/et h0 for sub-path eth0.dbus.get.nis_domain
> Nov 16 14:07:54 localhost dhcdbd: message_handler: message handler
> not found under /com/redhat/dhcp/et h0 for sub-path
> eth0.dbus.get.nis_servers
>
>
> output of before starting X
> ps aux | grep dbus
> 102 4963 0.0 0.0 8412 884 ? Ss 13:53
> 0:00 /usr/bin/dbus-daemon --system root 5483 0.0 0.0 4568
> 1268 ? S 13:53 0:00 /sbin/dhclient -1 -lf /var/lib/dhcp3/
> dhclient.eth0.leases -pf /var/run/dhclient.eth0.pid -q -e dhc_dbus=31
> -d eth0 ivan 5904 0.0 0.0 7876 728 tty1 S+ 13:55
> 0:00 grep dbus
>
> After X start, but KDE complain no dbus running:
> dark:~# ps aux | grep dbus
> 102 4961 0.0 0.0 8548 968 ? Ss 13:36
> 0:00 /usr/bin/dbus-daemon --system root 5476 0.0 0.0 4568
> 1264 ? S 13:36 0:00 /sbin/dhclient -1
> -lf /var/lib/dhcp3/dhclient.eth0.leases
> -pf /var/run/dhclient.eth0.pid -q -e dhc_dbus=31 -d eth0 ivan
> 5945 0.0 0.0 17816 792 ? Ss 13:38
> 0:00 /usr/bin/ssh-agent /usr/bin/dbus-launch --exit-with-session
> x-session-manager ivan 5950 0.0 0.0 7852 672 ? S
> 13:38 0:00 /usr/bin/dbus-launch --exit-with-session
> x-session-manager ivan 5951 0.0 0.0 4100 420 ? Ss
> 13:38 0:00 /usr/bin/dbus-daemon --fork --print-pid 4
> --print-address 6 --session root 6129 0.0 0.0 7880 736
> pts/1 S+ 13:40 0:00 grep dbus
Ok, all this logs indicate that dbus is starting properly.
> Could it be a timing problem? dbus starting too late?
> I'm willing to report as much information required to diagnose the
> problem but I don't know where to start from.
Which program reports that dbus isn't running? What is the exact error? Could
you try to run dbus-monitor --system and dbus-monitor --session in your KDE
session so we know for sure that both busses are operating properly?
(dbus-monitor is in the dbus-1-utils package)
Sjoerd
--
To invent, you need a good imagination and a pile of junk.
-- Thomas Edison
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
