DebianThis forum is for the discussion of Debian Linux.
Notices
Welcome to LinuxQuestions.org, a friendly and active Linux Community.
You are currently viewing LQ as a guest. By joining our community you will have the ability to post topics, receive our newsletter, use the advanced search, subscribe to threads and access many other special features. Registration is quick, simple and absolutely free. Join our community today!
Note that registered members see fewer ads, and ContentLink is completely disabled once you log in.
If you have any problems with the registration process or your account login, please contact us. If you need to reset your password, click here.
Having a problem logging in? Please visit this page to clear all LQ-related cookies.
Get a virtual cloud desktop with the Linux distro that you want in less than five minutes with Shells! With over 10 pre-installed distros to choose from, the worry-free installation life is here! Whether you are a digital nomad or just looking for flexibility, Shells can put your Linux machine on the device that you want to use.
Exclusive for LQ members, get up to 45% off per month. Click here for more info.
Peeths001:~# uname -a
Linux Peeths001 2.6.26-2-amd64 #1 SMP Mon Oct 26 10:39:40 UTC 2009 x86_64 GNU/Linux
Today I installed Samba, I restarted the machine . But there was no issues. and after that there was some security updates I installed the updates and after restarting I am getting the error message box after loggin in . The message is "Failed to Initialize HAL!".
ANd I dont have a network also now !!!!!! What is that it is going on ?
I also tried the below
Quote:
Peeths001:~# dpkg-reconfigure hal
Stopping Hardware abstraction layer: hald.
Reloading system message bus config...Failed to open connection to "system" message bus: Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: No such file or directory
invoke-rc.d: initscript dbus, action "force-reload" failed.
Starting Hardware abstraction layer: haldinvoke-rc.d: initscript hal, action "start" failed.
Peeths001:~# /etc/init.d/networking restart
Reconfiguring network interfaces...There is already a pid file /var/run/dhclient.eth0.pid with pid 3006
killed old client process, removed PID file
Internet Systems Consortium DHCP Client V3.1.1
Copyright 2004-2008 Internet Systems Consortium.
All rights reserved.
For info, please visit http://www.isc.org/sw/dhcp/
Listening on LPF/eth0/00:1f:c6:c7:ad:8a
Sending on LPF/eth0/00:1f:c6:c7:ad:8a
Sending on Socket/fallback
DHCPRELEASE on eth0 to 192.168.1.1 port 67
done.
(network-admin:3414): Liboobs-WARNING **: Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: No such file or directory
(network-admin:3414): Liboobs-WARNING **: OobsSession object hasn't connected to the bus, cannot register OobsObject
process 3414: arguments to dbus_connection_send_with_reply_and_block() were incorrect, assertion "connection != NULL" failed in file dbus-connection.c line 3338.
This is normally a bug in some application using the D-Bus library.
D-Bus not built with -rdynamic so unable to print a backtrace
Peeths001:~# tail -25 /var/log/messages
Dec 31 12:07:00 Peeths001 kernel: [ 14.915459] Adding 2144636k swap on /dev/sda8. Priority:-1 extents:1 across:2144636k
Dec 31 12:07:00 Peeths001 kernel: [ 15.303253] EXT3 FS on sda6, internal journal
Dec 31 12:07:00 Peeths001 kernel: [ 15.980022] loop: module loaded
Dec 31 12:07:00 Peeths001 kernel: [ 16.509062] kjournald starting. Commit interval 5 seconds
Dec 31 12:07:00 Peeths001 kernel: [ 16.509062] EXT3 FS on sda7, internal journal
Dec 31 12:07:00 Peeths001 kernel: [ 16.509062] EXT3-fs: mounted filesystem with ordered data mode.
Dec 31 12:07:00 Peeths001 kernel: [ 16.537056] kjournald starting. Commit interval 5 seconds
Dec 31 12:07:00 Peeths001 kernel: [ 16.537056] EXT3 FS on sda5, internal journal
Dec 31 12:07:00 Peeths001 kernel: [ 16.537056] EXT3-fs: mounted filesystem with ordered data mode.
Dec 31 12:07:00 Peeths001 kernel: [ 18.046692] r8169: eth0: link up
Dec 31 12:07:00 Peeths001 kernel: [ 19.471622] powernow-k8: Found 1 AMD Phenom(tm) 8450 Triple-Core Processor processors (3 cpu cores) (version 2.20.00)
Dec 31 12:07:00 Peeths001 kernel: [ 19.471622] powernow-k8: 0 : pstate 0 (2100 MHz)
Dec 31 12:07:00 Peeths001 kernel: [ 19.471622] powernow-k8: 1 : pstate 1 (1050 MHz)
Dec 31 12:07:01 Peeths001 kernel: [ 20.414081] NET: Registered protocol family 10
Dec 31 12:07:01 Peeths001 kernel: [ 20.414081] lo: Disabled Privacy Extensions
Dec 31 12:07:01 Peeths001 kernel: [ 20.638840] lp0: using parport0 (interrupt-driven).
Dec 31 12:07:01 Peeths001 kernel: [ 20.661421] ppdev: user-space parallel port driver
Dec 31 12:07:04 Peeths001 kernel: [ 23.988366] VBoxDrv: dbg - g_abExecMemory=ffffffffa02e4360
Dec 31 12:07:04 Peeths001 kernel: [ 23.988366] vboxdrv: fAsync=0 offMin=0xd61 offMax=0x2b78
Dec 31 12:07:04 Peeths001 kernel: [ 23.988366] vboxdrv: TSC mode is 'synchronous', kernel timer mode is 'normal'. Dec 31 12:07:04 Peeths001 dhcdbd: dbus_svc_init failed: org.freedesktop.DBus.Error.NoServer Failed to connect to socket /usr/local/var/run/dbus/system_bus_socket: Connection refused
Dec 31 12:07:04 Peeths001 dhcdbd: Failed to initialise D-Bus service.
Dec 31 12:07:09 Peeths001 kernel: [ 28.932233] nvidia: module license 'NVIDIA' taints kernel.
Dec 31 12:07:09 Peeths001 kernel: [ 29.196750] ACPI: PCI Interrupt 0000:01:00.0[A] -> GSI 18 (level, low) -> IRQ 18
Dec 31 12:07:09 Peeths001 kernel: [ 29.196941] NVRM: loading NVIDIA UNIX x86_64 Kernel Module 173.14.09 Wed Jun 4 23:40:50 PDT 2008
any solution for this ?
I also tried
Quote:
Peeths001:~# apt-get install dhcdbd
Reading package lists... Done
Building dependency tree
Reading state information... Done
dhcdbd is already the newest version.
dhcdbd set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 6 not upgraded.
the one thing that strikes me as strange here is that the dbus socket is being looked for in /usr/local/var/run instead of /var/run. Did you install dbus manually or using apt?
Sorry the problem does not appear to be with dbus but with network-admin which I believe is a part of the gnome-system-tools package. You could try reinstalling that.
LinuxQuestions.org is looking for people interested in writing
Editorials, Articles, Reviews, and more. If you'd like to contribute
content, let us know.