Bug 13166 - X does not start when having Xvfb running
Summary: X does not start when having Xvfb running
Status: RESOLVED FIXED
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/General (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-11-09 22:39 UTC by Dobromir Gaydarov
Modified: 2018-06-11 19:31 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments
log file (662 bytes, text/plain)
2007-11-09 22:41 UTC, Dobromir Gaydarov
no flags Details

Description Dobromir Gaydarov 2007-11-09 22:39:24 UTC
I have configuration that worked in Fedora 7 but does not work in Fedora 8.
I need to start Proxomitron as a service. It is a Windows based proxy server. I am  running it with Wine. Since it creates a small icon in the tray I need an X screen to connect in order to start it. So as part of the startup scripts I start Xvfb instance on screen 2 and then run Proxomitron with wine and connect to screen 2.
This always worked in Fedora 7. With Fedora 8 I get an error and X refuses to start. I looked at the /tmp/.X11-unix directory - it is there, it is owned by root and it has X2 already in it. When I do not start the service from the rc5.d scripts X starts normally, I can start the service after that and everything works. A workaround to schedule the service to start in a minute (effectively after X has opportunity to start) works.
All similar message I was able to find on the web are related to the directory being owned by root. In my case there it is something else.
Comment 1 Dobromir Gaydarov 2007-11-09 22:41:06 UTC
Created attachment 12434 [details]
log file
Comment 2 Jesse Adkins 2010-12-01 16:51:38 UTC
I'm rather suspicious of this bug after seeing the log posted. At first I thought this was an issue with Xvfb requesting a lock file in the same place as Xserver.

The log shows stat and mkdir failing to create the necessary sockets. Who are you trying to start X as? Also, can you post the result of ls on /tmp/ and /tmp/.X11-unix/


...


On second thought, try using /tmp/.X11-unix/ instead (with the slash at the end).
Comment 3 Adam Jackson 2018-06-11 19:31:53 UTC
systemd handles creating this directory now.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.