recent security updates to 10.3-RELEASE broke xdm?

Konstantin Schukraft konstantin at
Sun Oct 23 20:57:46 UTC 2016

Did you get around to reporting this bug?

On Sun, Oct 02, 2016 at 11:00:23AM +0100, Anton Shterenlikht wrote:
>This is an amd64 laptop.
>After updating to:
># /bin/freebsd-version -ku
>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
>D-Bus per-session daemon address is:
>My .xsession script is:
>xautolock -locker slock &
># test for an existing bus daemon, just to be safe
>if test -z "$DBUS_SESSION_BUS_ADDRESS" ; then
>    # if not found, launch a new one
>    eval 'dbus-launch --sh-syntax --exit-with-session'
>    echo "D-Bus per-session daemon address is: $DBUS_SESSION_BUS_ADDRESS"
>Am I out of date?
>Is my .xsession script too old?
>Any other advice?
>freebsd-questions at mailing list
>To unsubscribe, send any mail to "freebsd-questions-unsubscribe at"
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 801 bytes
Desc: not available
URL: <>

More information about the freebsd-questions mailing list