From owner-freebsd-questions@freebsd.org Sun Oct 2 19:42:59 2016 Return-Path: Delivered-To: freebsd-questions@mailman.ysv.freebsd.org Received: from mx1.freebsd.org (mx1.freebsd.org [IPv6:2001:1900:2254:206a::19:1]) by mailman.ysv.freebsd.org (Postfix) with ESMTP id 371ADAF2427 for ; Sun, 2 Oct 2016 19:42:59 +0000 (UTC) (envelope-from konstantin@schukraft.org) Received: from server949-han.de-nserver.de (server949-han.de-nserver.de [77.75.250.185]) (using TLSv1.2 with cipher ECDHE-RSA-AES256-GCM-SHA384 (256/256 bits)) (Client did not present a certificate) by mx1.freebsd.org (Postfix) with ESMTPS id C6DFDB34 for ; Sun, 2 Oct 2016 19:42:57 +0000 (UTC) (envelope-from konstantin@schukraft.org) Received: (qmail 30527 invoked from network); 2 Oct 2016 21:42:44 +0200 X-Fcrdns: Yes Received: from schukraft.it (HELO midgard.local.schukraft.it) (80.147.5.44) (smtp-auth username konstantin@schukraft.org, mechanism plain) by server949-han.de-nserver.de (qpsmtpd/0.92) with (ECDHE-RSA-AES256-GCM-SHA384 encrypted) ESMTPSA; Sun, 02 Oct 2016 21:42:44 +0200 Date: Sun, 2 Oct 2016 21:42:40 +0200 From: Konstantin Schukraft To: freebsd-questions@freebsd.org Subject: Re: recent security updates to 10.3-RELEASE broke xdm? Message-ID: <20161002194024.lios7rsb3zmdhbbm@midgard.local.schukraft.it> References: <201610021000.u92A0Nta016476@mech-as222.men.bris.ac.uk> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha256; protocol="application/pgp-signature"; boundary="jh2ry5ro7jck2d26" Content-Disposition: inline In-Reply-To: <201610021000.u92A0Nta016476@mech-as222.men.bris.ac.uk> User-Agent: NeoMutt/20160916 (1.7.0) X-User-Auth: Auth by konstantin@schukraft.org through 80.147.5.44 X-BeenThere: freebsd-questions@freebsd.org X-Mailman-Version: 2.1.23 Precedence: list List-Id: User questions List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , X-List-Received-Date: Sun, 02 Oct 2016 19:42:59 -0000 --jh2ry5ro7jck2d26 Content-Type: text/plain; charset=utf-8; format=flowed Content-Disposition: inline Hi, >After updating to: > ># /bin/freebsd-version -ku >10.3-RELEASE-p7 >10.3-RELEASE-p9 > >My xdm doesn't want to login me anymore. >As soon as I enter the passwd, xdm reboots >and presents me with the login prompt again. > >I see this in .xsession-errors: > >Protocol not supported by server >Couldn't connect to :0 >Protocol not supported by server >mwm: Could not open display. >Protocol not supported by server >DBUS_SESSION_BUS_ADDRESS='unix:path=/tmp/dbus-dEtC0CeeXH,guid=f1d367e2b8c81e06b0 >b3ce7257f0d422'; >export DBUS_SESSION_BUS_ADDRESS; >DBUS_SESSION_BUS_PID=1555; >D-Bus per-session daemon address is: I see the same phenomenon here, so you're not alone. I even have troubles starting a session with startx, I have to start an X server on a separate console before startx would work. I'm running current nvidia-driver-367.44, so it's not your driver either. Since I'd like to do a fresh reinstall once 11.0 is finalised and I'm able to work atm I didn't bother looking into it so far, but I wanted to let you know you're not alone. All the best, Konstantin --jh2ry5ro7jck2d26 Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- Version: GnuPG v2 iQIcBAEBCAAGBQJX8WMwAAoJEH3raMNeVmMFDRQP/0G3q0GYUsJI//Xkz5441JPR 6G7uwR2O/TFpoGN4CgHSvmmMeuMj0ymU0gmxmG8R3OgY1NpF4fA+jPwU9g7H3tlx 0h0KTkqExsZuFIrWkZjETdoYdx034JdeGfe8N7AUvuuGtc1YNMmpKgI0GdvnmKa4 pCllxzVV4QY74nxmUcz3E+zx5dJtxSdxD5OkZ/8IZ7ZMGn9OOwE+ahx9AFCrSKNo oytKuAyORZSMwOwQnFHOl0ECcO5TBTO+5R/2ldQYSsMyF9eMFywnMcasUURSjSXx O3+5YQc+ZKZ5M4A7HvRcYLFg7qeBapgjXjTA2lRH1wUHImsUQCFvOi1+lJmSeeMj 7OSY2PKRzAibHBu+yA7yH2NRyciY9EdioMC5a5GEhLQfJJ/0VPqNcBAaumSq8d8K yb0v1jD2NaIRRfrdIS0gEcUNhmRD8xQ+aTYAMMqxGhMLFQuFF0Jyz/zk8YkmNp4z u2Kt2hGjBmPVn2k3PNcPabGXBAFbCc9Jhz2Foj9fuc58IJdelXHjroEGoaiSDkuR CSGtqEwHutjEjXMCLEr76yg82gNFNOrqaq7Wanii6zyKo8Y4tEGnfp9Jk6MSzOP9 BI7QFCPgnavn46v5AtBCiQbeUpT3Fy70LW0tMTLCKIuPPudU57d9rQgt+rXQ/fr1 Qitcjdgk+lq7E+eW/l+d =5vul -----END PGP SIGNATURE----- --jh2ry5ro7jck2d26--