startx intermittant failure, "X server already running on display :0"
by jrch from LinuxQuestions.org on (#4VZZC)
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
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