Created attachment 353488 [details] journalctl -xb Diffrent errors appear after switching to systemd. gdm does not start. Seems it can not connect to dbus; but why? ------------------------------- Jul 17 07:42:29 gdm[492]: error getting system bus: GDBus.Error:org.freedesktop.DBus.Error.AccessDenied: Failed to determine seats of user "0": Permission denied Jul 17 07:42:29 systemd-logind[484]: Failed to get system D-Bus connection: Access denied Jul 17 07:42:29 systemd-logind[484]: Failed to fully start up daemon: Connection refused ------------------------------- Has anyone an idear?
1. Did you rebuild with USE="+pam +policykit +systemd -consolekit"? 2. Any odd configuration in one of those files, or is everything standard? 3. Did you set up systemd properly? Try following the Wiki for it, especially the pam_systemd part; as seen here: http://wiki.gentoo.org/wiki/Systemd#systemd-logind_.26_pam_systemd
Please post your `emerge --info' output in a comment.
(In reply to Tom Wijsman (TomWij) from comment #1) > 1. Did you rebuild with USE="+pam +policykit +systemd -consolekit"? rebuild was at least with "systemd -consolekit" in make.conf. i will have a look at +pam +policykit, too. > 2. Any odd configuration in one of those files, or is everything standard? in those parts not; but i have a special initrd to decrypt the Luks partitions. but all partitions are decrypted bevore systemd starts (journalctl-xd.log). > 3. Did you set up systemd properly? Try following the Wiki for it, > especially the pam_systemd part; as seen here: > http://wiki.gentoo.org/wiki/Systemd#systemd-logind_.26_pam_systemd it has no effect on the gdm/systemd-logind `emerge --info' is underway ------------------------------ i do not understand why "0" gets no permission Failed to determine seats of user "0": Permission denied Failed to get system D-Bus connection: Access denied
(In reply to all.xi from comment #3) > i do not understand why "0" gets no permission > Failed to determine seats of user "0": Permission denied > Failed to get system D-Bus connection: Access denied Can't really tell without a log; if you can, feel free to run it with `strace -f -s9999 -o /tmp/gdm.log gdm`. If that's insufficient, you might need to do the same with systemd-logind... Seems the main error to pay attention to here is "Failed to fully start up daemon: Connection refused" though; I'm not entirely sure if the permission are the cause or the consequence...
Created attachment 353514 [details] emergeInfo_20130717.txt
Created attachment 353516 [details] gdm.log
Created attachment 353518 [details] gdm--nodaemon.log
Created attachment 353520 [details] systemd-logind.log
For all three, we see that it tries to talk to DBus: 4440 sendmsg(5, {msg_name(0)=NULL, msg_iov(1)=[{"l\1\0\1\0\0\0\0\1\0\0\0m\0\0\0\1\1o\0\25\0\0\0/org/freedesktop/DBus\0\0\0\3\1s\0\5\0\0\0Hello\0\0\0\2\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0\6\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0", 128}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 128 But then it receives an access denied error from DBus stating it can't determine the seats of user 0 because permission is denied: 4440 recvmsg(5, {msg_name(0)=NULL, msg_iov(1)=[{"\4\1s\0'\0\0\0org.freedesktop.DBus.Error.AccessDenied\0\5\1u\0\1\0\0\0\10\1g\0\1s\0\0\7\1s\0\24\0\0\0org.freedesktop.DBus\0\0\0\0008\0\0\0Failed to determine seats of user \"0\": Permission denied\0", 157}], msg_controllen=0, msg_flags=MSG_CMSG_CLOEXEC}, MSG_CMSG_CLOEXEC) = 157 Can you tarball the /etc/dbus-1 folder and attach it to this bug?? `tar czf dbus-1.tar.gz /etc/dbus-1` Also, please copy the relevant portion of the following command output to show the versions of those packages: `emerge -Cpv sys-apps/systemd sys-apps/accountsservice sys-auth/pambase sys-libs/pam dev-libs/dbus-glib sys-apps/dbus`
Created attachment 353530 [details] dbus-1.tbz Hello Tom, thanks a lot for your debugging. here is the next bucket of information. the dbus-1 directory
Created attachment 353532 [details] emergedPackages.txt and the package versions. thanks xi
Interestingly I came across the same issue on one of my systems. The biggest similarity I see here is the use of an initrd for luks, which seems unrelated to the dbus problems... Has this issue since been resolved somehow ?
Looks solved with current dbus and systemd versions in the tree
