Jorge Boscan wrote:
Check that dbus (messagebus) is running - dbus fails to start if it cannot get user or group information, we had to ensure NSCD was running for dbus to start for other service that use dbus to start.update.. Sep 21 22:36:39 vader NetworkManager: <info> starting... Sep 21 22:36:39 vader netplugd[1846]: Netlink packet came from pid 3257, not from kernel Sep 21 22:36:39 vader NetworkManager: <WARN> nm_dbus_init(): nm_dbus_init() could not get the system bus. Make sure the message bus daemon is running! Sep 21 22:36:39 vader NetworkManager: <ERROR> [1190406999.036167] main (): nm_dbus_init() failed, exiting. Either dbus is not running, or the NetworkManager dbus security policy was not loaded. Sep 21 22:36:39 vader NetworkManager: traceback: Sep 21 22:36:39 vader NetworkManager: NetworkManager(main+0x702) [0x421c12] Sep 21 22:36:39 vader NetworkManager: /lib64/libc.so.6(__libc_start_main+0xf4) [0x3cf9a1dab4] Sep 21 22:36:39 vader NetworkManager: NetworkManager [0x40e049] Sep 21 22:36:39 vader kernel: NetworkManager[3257] trap int3 rip:421aaf rsp:7fffcff50570 error:0 On 9/22/07, Jorge Boscan <joretur@xxxxxxxxx> wrote:/etc/init.d/ConsoleKit restart console-kit-daemon[2845]: WARNING: Couldn't connect to system bus: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken. -- [Jorge J. Boscán Etura] quando omni flunkus moritatus --
|