[Bug 213789] x11/xdm can't login after security update 10.3p9
bugzilla-noreply at freebsd.org
bugzilla-noreply at freebsd.org
Tue Nov 8 21:27:37 UTC 2016
https://bugs.freebsd.org/bugzilla/show_bug.cgi?id=213789
mexas at bris.ac.uk changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |mexas at bris.ac.uk
--- Comment #1 from mexas at bris.ac.uk ---
also in 11.0-RELEASE-p2
As soon as I type in my username, passwd and hit enter,
xdm gets back to the login screen.
xdm.log:
$ cat /var/log/xdm.log
xdm info (pid 966): Starting
xdm info (pid 966): Starting X server on :0
X.Org X Server 1.17.4
Release Date: 2015-10-28
X Protocol Version 11, Revision 0
Build Operating System: FreeBSD 11.0-RELEASE-p1 amd64
Current Operating System: FreeBSD minky 11.0-RELEASE-p2 FreeBSD 11.0-RELEASE-p2
#0: Mon Oct 24 06:55:27 UTC 2016
root at amd64-builder.daemonology.net:/usr/obj/usr/src/sys/GENERIC amd64
Build Date: 16 October 2016 04:53:46PM
Current version of pixman: 0.34.0
Before reporting problems, check http://wiki.x.org
to make sure that you have the latest version.
Markers: (--) probed, (**) from config file, (==) default setting,
(++) from command line, (!!) notice, (II) informational,
(WW) warning, (EE) error, (NI) not implemented, (??) unknown.
(==) Log file: "/var/log/Xorg.0.log", Time: Tue Nov 8 22:19:20 2016
(==) Using config file: "/etc/X11/xorg.conf"
xdm info (pid 970): sourcing /usr/local/lib/X11/xdm/Xsetup_0
xdm info (pid 970): sourcing /usr/local/lib/X11/xdm/GiveConsole
xdm info (pid 979): executing session /usr/local/lib/X11/xdm/Xsession
xdm info (pid 970): sourcing /usr/local/lib/X11/xdm/TakeConsole
XIO: fatal IO error 35 (Resource temporarily unavailable) on X server ":0"
after 162 requests (131 known processed) with 0 events remaining.
xdm info (pid 966): Starting X server on :0
xdm info (pid 991): sourcing /usr/local/lib/X11/xdm/Xsetup_0
Logging in from a text terminal and then launching startx works fine.
Anton
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the freebsd-x11
mailing list