1 |
Am 2013-01-31 19:54, schrieb Canek Peláez Valdés: |
2 |
|
3 |
> sshd.service, ssh@.service, systemd-update-utmp-runlevel.service, and |
4 |
> systemd-update-utmp-shutdown.service have auditd.service in their |
5 |
> After= field; several others have plymouth services. After= is just |
6 |
> for ordering of units, is not a requirement; systemd detects that |
7 |
> auditd.service doesn't exists, and it starts the units that have it in |
8 |
> ther After= field anyway. To make a unit depend on another, you need |
9 |
> Require=. |
10 |
> |
11 |
> You can mask the services you don't have by creating a soft link to /dev/null: |
12 |
> |
13 |
> # ll /etc/systemd/system/rc-local.service |
14 |
> lrwxrwxrwx 1 root root 9 Aug 16 13:51 |
15 |
> /etc/systemd/system/rc-local.service -> /dev/null |
16 |
> |
17 |
> It cleans up the output of systemctl --full --all. |
18 |
|
19 |
Ok, so I don't need auditd or plymouth, right? |
20 |
|
21 |
> Well, I have no idea why your gdm is not letting you log in; obviously |
22 |
> it's related to polkit (since it started when you changed from |
23 |
> consolekit to polkit), but nothing in your config seems to differ from |
24 |
> mine. It is not impossible that somehow the configuration files of the |
25 |
> gdm user got messed up when the change happened. I don't know how this |
26 |
> could happen, but as a hail Mary you could delete /var/lib/gdm, and |
27 |
> reemerge it so it gets a clean install. |
28 |
|
29 |
Tried that as well, same problems after .... :-( |
30 |
|
31 |
> Also, you have USE=pam for polkit, right? |
32 |
|
33 |
Yes. |
34 |
|
35 |
[I] sys-auth/polkit |
36 |
Available versions: 0.107-r1 0.110 {examples gtk +introspection |
37 |
kde nls pam selinux systemd} |
38 |
Installed versions: 0.110(19:19:55 30.01.2013)(gtk introspection |
39 |
nls pam systemd -examples -kde -selinux) |
40 |
|
41 |
> And could you post the |
42 |
> output from "journalctl -b /usr/lib/polkit-1/polkitd"? |
43 |
|
44 |
That is empty! |
45 |
|
46 |
S |