Bug 101143 - Xvfb command cannot start at xorg-xserver 1.16.3 ~ xserver 1.18.4
Summary: Xvfb command cannot start at xorg-xserver 1.16.3 ~ xserver 1.18.4
Status: RESOLVED NOTABUG
Alias: None
Product: xorg
Classification: Unclassified
Component: Server/DDX/Xvfb (show other bugs)
Version: git
Hardware: Other All
: medium normal
Assignee: Xorg Project Team
QA Contact: Xorg Project Team
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-05-22 06:40 UTC by susanbian
Modified: 2017-05-24 02:29 UTC (History)
0 users

See Also:
i915 platform:
i915 features:


Attachments

Description susanbian 2017-05-22 06:40:06 UTC
Xvfb command cannot start at xorg-xserver1.16.3 ~ xorg-xserver1.18.4

------------------------------
export DISPLAY=127.0.0.1:1
Xvfb :1 -screen 0 1024x768x16
-------------------------------

According to strace log, epoll_wait() command error occurd. Output log is showed as follow.
-----------------------------
INIT: Id "S1" respawning too fast: disabled for 5 minutes
----------------------------- 

According to /etc/inittab file, define is as follow.
-----------------------------
#
S0:12345:respawn:/bin/start_getty 115200 ttyS0 vt102
S1:12345:respawn:/bin/start_getty 115200 ttyS0 vt102
# /sbin/getty invocations for the runlevels.
#
# The "id" field MUST be the same as the last
# characters of the device (after "tty").
#
# Format:
#  <id>:<runlevels>:<action>:<process>
#

1:12345:respawn:/sbin/getty 38400 tty1
-----------------------------
Comment 1 Adam Jackson 2017-05-23 15:31:05 UTC
No, that starts Xvfb fine. Whatever's going wrong here, it's not the server.
Comment 2 susanbian 2017-05-24 02:08:13 UTC
Xvfb command can not end. The following log loop output.
-----------------------
INIT: Id "S1" respawning too fast: disabled for 5 minutes
-----------------------
Comment 3 Alan Coopersmith 2017-05-24 02:29:07 UTC
Your inittab says S1 is /bin/start_getty not Xvfb.


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.