Lennart Poettering on Fri, 2013/05/03 16:30:
> On Tue, 30.04.13 00:03, Christian Hesse ([email protected]) wrote:
>
> > Hello everybody,
> >
> > ok, this looks very tricky... I have no idea what happens and I have no
> > way to reproduce this. It just happens from time to time - very seldom.
> >
>
On Tue, 30.04.13 00:03, Christian Hesse ([email protected]) wrote:
> Hello everybody,
>
> ok, this looks very tricky... I have no idea what happens and I have no way
> to reproduce this. It just happens from time to time - very seldom.
>
> If this happens I am not able to log in from lxdm and getty.
Zbigniew Jędrzejewski-Szmek on Tue, 2013/04/30 01:05:
> On Tue, Apr 30, 2013 at 12:03:24AM +0200, Christian Hesse wrote:
> > Hello everybody,
> >
> > ok, this looks very tricky... I have no idea what happens and I have no
> > way to reproduce this. It just happens from time to time - very seldom.
On Tue, Apr 30, 2013 at 1:05 AM, Zbigniew Jędrzejewski-Szmek
wrote:
>> This is an Arch Linux system with Linux 3.8.8-1-ARCH and systemd 202-1.
>> Any ideas?
> Are you using selinux, runinng in enforcing mode? How soon after boot,
> and how soon after selinux policy is loaded, does this happen?
Th
On Tue, Apr 30, 2013 at 12:03:24AM +0200, Christian Hesse wrote:
> Hello everybody,
>
> ok, this looks very tricky... I have no idea what happens and I have no way
> to reproduce this. It just happens from time to time - very seldom.
>
> If this happens I am not able to log in from lxdm and getty
Hello everybody,
ok, this looks very tricky... I have no idea what happens and I have no way
to reproduce this. It just happens from time to time - very seldom.
If this happens I am not able to log in from lxdm and getty. The only way back
into the system is getting a failed login from getty, it
