startx intermittant failure, "X server already running on display :0"

Slackware64 14.2 / multilib, with original kernel ('huge') as released.
After boot and user login, I type 'startx' and it fails first time or maybe first two times, then launches. When it fails, it says, among other things, "X server already running on display :0" - which is pretty hard to understand since I just launched it for the first time.

Here is most of the visible message when startx fails:
"...
...
(==) Log file: "/var/log/Xorg.0.log", Time: Mon Dec 2 13:47:31 2019
(==) Using system config directory "/usr/share/X11/xorg.conf.d"
resize called 1920 1080
/usr/bin/startxfce4: X server already running on display :0
_IceTransSocketUNIXCreateListener: ...SocketCreateListener() failed
_IceTransMakeAllCOTSServerListeners: server already running
xfce4-session: Unable to establish ICE listeners: Cannot establish any listening sockets
xinit: connection to X server lost
waiting for X server to shut down (II) Server terminated successfully (0). Closing log file."

I used to use one of the 'xorgconfig' type programs to painfully setup a *.conf file, with sections for everything, monitor, keyboard, etc. But last few years, I just use startx after install and login to user acct.

I'm hoping I don't have to go thru the process of generating a conf file again. Right now there is none in /etc/X11/; in /usr/share/X11/xorg.conf.d (folder) there are only a few specific files apparently for laptops; no overall x conf file anywhere.

I've looked at the log file in /var/log/Xorg.0.log after both startx failure and startx success, and have trouble locating anything meaningful. Mostly seems like lists of optional vid cards and monitors it is 'trying'....

I've gotten used to just living with this, knowing X will start 2nd or 3rd try; so far no damage is apparent. I'm really not a 'gamer', and I don't need all the fancy gimicks on newer vid cards. This just gets a bit old, is all.

I don't know how to 'post' a copy of a file here.

I can't find any relevant information online - I must be the only one with this error message...

Thanks for any comments on situation..
jrc

Manual says it's only necessary to run X -configure in case autodetect fails.

But it also says to run xwmconfig to select environment... (bottom): https://docs.slackware.com/slackware:beginners_guide

Jan - I did that (xwmconfig) as part of normal slack install. Also repeated it (with no effect, since I was already in xfce4) just in case, before latest error - same thing,

"X server already running on display :0"

Actually this problem has been present on several different computers running slack/xfce for years. Same symptom, same message.

Could be you're booting to the wrong level. By default Slackware boots to level 3 (console login); level 4 is graphical login. Maybe you changed the level and then forgot about it. Check /etc/inittab.

Also if X is running, you should be able to find it with alt-Fn (probably alt-F7).

Thanks Hazel, I will check those things next reboot (today).
jrc

Thanks for suggestions Hazel. I tried both of those things, with no resolution.

1) Have been consistently starting on runlevel 3.

2) When startx fails with message, "X server already running on display :0", I try ALT-F7 AND also CTRL-ALT-F7 with no response from machine.

In addition, I went to the 'x' webpage (www.x.org/wiki) and checked the FAQ (and the 'other FAQ's'). One FAQ item (error messages...) "Server is already active for display 0". I performed all the steps there (as root) and nothing helped. The 'lock' file is not there at all. But x claiims the 'server isa lready running ...".

A bit mistifying to me.

jrc

I thank Hazel and whoever else contributed to this question.

However, in order to solicit more responses, I'm going to move this topic to the main 'Slackware' forum.

If this irritates some folks, I'm sorry. But that kind of response will - as far as I'm concerned - demonstrate that this 'Installatin' subforum is the wrong place to start a topic of any but the most elementary kind.

jrc

If you enter "ps ax|grep Xorg" at the console, can you see Xorg running? Is there a /var/log/Xorg file with the current date?