You are not logged in.

#1 2012-09-27 10:26:00

utops
Member
Registered: 2012-09-24
Posts: 44

Dbus issues

dbus-monitor --session
Failed to open connection to session 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.
Sep 27 11:46:26 wootzilla login: pam_systemd(login:session): Failed to 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.

No erros on

 systemctl --fail|--all



I've got systemd with commented (#)rc.conf and transfered daemons as foobar.service to systemd.
sysvinit removed sysvcompat installed.
Should I be worried?

Offline

#2 2012-09-27 12:45:04

nTia89
Banned
From: varese, italy
Registered: 2008-12-22
Posts: 1,230

Re: Dbus issues

do you have consolekit?


+pc: custom | AMD Opteron 175 | nForce4 Ultra | 2GB ram DDR400 | nVidia 9800GT 1GB | ArchLinux x86_64 w/ openbox
+laptop: Apple | MacBook (2,1) | 2GB ram | Mac OS X 10.4 -> DIED
+ultrabook: Dell | XPS 13 (9343) | 8GB ram | 256GB ssd | FullHD display | Windows 8.1 64bit ArchLinux x86_64 w/ Gnome

Offline

Board footer

Powered by FluxBB