On 05/21/2012 07:30 AM, Kamil Paral wrote:
I can't find anything in /var/log/messages, dmesg output,
~/.xsession-errors, or /var/log/Xorg.0.log to explain this.
I have auto-login configured, and if I reboot my machine, I _am_
logged in successfully. It's only when I log out and log back in
again that the login fails.
It seems Xserver is crashing. After the crash have a look at
/var/log/Xorg.0.log.old and `dmesg` output.
The X server is NOT crashing.
As I said, "I can't find anything in /var/log/messages, dmesg output,
~/.xsession-errors, or /var/log/Xorg.0.log to explain this."
The X server does not exit and restart when the login fails. It's the
same instance of the X server, the same /var/log/Xorg.0.log file,
afterwards.
Here's what shows up in /var/log/messages when I attempt to log in:
May 21 07:34:21 jik2 TIFIER=systemd-logind[759]: New session 72 of user jik.
May 21 07:34:22 jik2 TIFIER=systemd-logind[759]: Removed session 72.
May 21 07:34:22 jik2 dbus-daemon[772]: dbus[772]: [system] Activating
service name='net.reactivated.Fprint' (using servicehelper)
May 21 07:34:22 jik2 dbus[772]: [system] Activating service
name='net.reactivated.Fprint' (using servicehelper)
May 21 07:34:22 jik2 dbus-daemon[772]: Launching FprintObject
May 21 07:34:22 jik2 dbus-daemon[772]: dbus[772]: [system] Successfully
activated service 'net.reactivated.Fprint'
May 21 07:34:22 jik2 dbus[772]: [system] Successfully activated service
'net.reactivated.Fprint'
May 21 07:34:22 jik2 dbus-daemon[772]: ** Message: D-Bus service
launched with name: net.reactivated.Fprint
May 21 07:34:22 jik2 dbus-daemon[772]: ** Message: entering main loop
Note the oddly truncated "TIFIER" tag at the beginning of some of the
messages. I don't know if that's relevant. It wasn't happening until
after last night's update.
--
test mailing list
[email protected]
To unsubscribe:
https://admin.fedoraproject.org/mailman/listinfo/test
