On Thu, Jan 31, 2013 at 12:35 PM, Stefan G. Weichinger <li...@xunil.at> wrote: > Am 31.01.2013 19:26, schrieb Canek Peláez Valdés: > >> And I suppose both sgw and gdm are in the video group (the later is >> done by the ebuild, if I'm not mistaken). > > Yes, they are: > > # getent group video > video:x:27:root,mythtv,sgw,gdm > >> What is the uid and gid of >> gdm? > > # getent passwd gdm > gdm:x:104:446:added by portage for gdm:/var/lib/gdm:/sbin/nologin > >> Also, did GDM (the same version) worked with OpenRC, or did you >> installed systemd and upgraded gdm at the same time? > > hmm. No upgrade of gdm, but a re-build as it changed USE-flags > (-consolekit systemd). > >> What does "systemctl --all --full" says, which units are in red? > > > # systemctl --all --full | grep erro > auditd.service > error inactive dead > auditd.service > > plymouth-quit-wait.service > error inactive dead > plymouth-quit-wait.service > > plymouth-start.service > error inactive dead > plymouth-start.service > > syslog.service > error inactive dead > syslog.service > > > # systemctl --all --full | grep fail > gdm.service > loaded failed failed Gnome > Display Manager > > I dont't have plymouth or sys-process/audit ... nothing pulled that in.
sshd.service, ssh@.service, systemd-update-utmp-runlevel.service, and systemd-update-utmp-shutdown.service have auditd.service in their After= field; several others have plymouth services. After= is just for ordering of units, is not a requirement; systemd detects that auditd.service doesn't exists, and it starts the units that have it in ther After= field anyway. To make a unit depend on another, you need Require=. You can mask the services you don't have by creating a soft link to /dev/null: # ll /etc/systemd/system/rc-local.service lrwxrwxrwx 1 root root 9 Aug 16 13:51 /etc/systemd/system/rc-local.service -> /dev/null It cleans up the output of systemctl --full --all. >> And lastly, how did you set gdm as your display manager? Do you have: >> >> # ls -l /etc/systemd/system/display-manager.service >> lrwxrwxrwx 1 root root 37 Dec 6 00:40 >> /etc/systemd/system/display-manager.service -> >> /usr/lib64/systemd/system/gdm.service >> >> ? > > Right now it links to xdm, but I had it the way you posted and tested that. > > When I test, I switch to a text console: > > systemctl stop xdm > systemctl start gdm Well, I have no idea why your gdm is not letting you log in; obviously it's related to polkit (since it started when you changed from consolekit to polkit), but nothing in your config seems to differ from mine. It is not impossible that somehow the configuration files of the gdm user got messed up when the change happened. I don't know how this could happen, but as a hail Mary you could delete /var/lib/gdm, and reemerge it so it gets a clean install. Also, you have USE=pam for polkit, right? And could you post the output from "journalctl -b /usr/lib/polkit-1/polkitd"? Regards. -- Canek Peláez Valdés Posgrado en Ciencia e Ingeniería de la Computación Universidad Nacional Autónoma de México
