recent security updates to 10.3-RELEASE broke xdm?

Anton Shterenlikht mexas at
Sun Oct 2 13:08:45 UTC 2016

>From freebsd at Sun Oct  2 13:48:31 2016
>> 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.
>Can you start X without using XDM (i. e., by "startx")?

Yes, startx works fine.
I'd still prefer to get xdm working again.
Apparently startx doesn't allow xconsole access to /dev/consile.

Anyway, this is what I get:

####> cat .xsession
source ~/.tcshrc
exec ~/.xinitrc
####> cat .xinitrc
xautolock -locker slock &
xconsole &
exec mwm
####> cat .xsession-errors
Protocol not supported by server                                                
Error: Can't open display: :0                                                   
Protocol not supported by server                                                
Couldn't connect to :0                                                          
Protocol not supported by server                                                
mwm: Could not open display.                                                    

In fact startx works fine even without
~/.xinitrc. In that case it opens some
default windows and uses twm.

/var/log/xdm.log is not much help:

xdm info (pid 917): Starting X server on :0                                     
xdm info (pid 4040): sourcing /usr/local/lib/X11/xdm/Xsetup_0                   
xdm info (pid 4040): sourcing /usr/local/lib/X11/xdm/GiveConsole                
xdm info (pid 4057): executing session /usr/local/lib/X11/xdm/Xsession          
xdm info (pid 4040): sourcing /usr/local/lib/X11/xdm/TakeConsole                
XIO:  fatal IO error 35 (Resource temporarily unavailable) on X server ":0"     
      after 169 requests (162 known processed) with 0 events remaining.      

Many thanks for your help


More information about the freebsd-questions mailing list