Comment 22 for bug 529230

Revision history for this message
Jamie Krug (jamie-thekrugs) wrote :

@John: Interesting... I meant to also comment on your question about stuff like this showing up in /var/log/auth.log:

$ cat /var/log/auth.log | grep FAILED
Sep 1 21:38:16 jkrug-serval login[6215]: FAILED LOGIN (1) on '/dev/tty1' FOR 'UNKNOWN', Authentication failure
Sep 1 21:38:19 jkrug-serval login[6215]: FAILED LOGIN (2) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Sep 1 21:38:22 jkrug-serval login[6215]: FAILED LOGIN (3) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Sep 1 21:38:25 jkrug-serval login[6215]: FAILED LOGIN (4) on '/dev/tty1' FOR 'UNKNOWN', Error in service module
Sep 1 21:38:27 jkrug-serval login[6215]: FAILED LOGIN (5) on '/dev/tty1' FOR 'UNKNOWN', Error in service module

What's strange is that, when I went to grab this to paste here, I noticed that the most recent date is Sep 1, but I'm positive I had one or two X resets yesterday, Sep 2. The difference was that yesterday I was trying out this suggested workaround:
sudo mv /etc/init/plymouth-splash.conf /etc/init/plymouth-splash.conf.disabled

So, apparently those "FAILED LOGIN" messages didn't appear in /var/log/auth.log, but X still reset on me :(