[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

Re: Bug#175618: xdm fails to start X



below is the output of the commands you suggested, after attempting to
run xdm again.  there are no processes with the name "xdm", and the
contents of the Xservers file looks sane.  the modification time on that
file is from Dec 8 last year.  between then and last night, when i ran
into this problem, the machine has been rebooted and successfully
restarted xdm.

to me it looks like the xdm package is rendered unusable by xdm failing
to start X, and that matched the "grave" severity option in the list
provided by reportbug.  what bug severity would you suggest?

alex.

tess-turbo:/home/alex# /usr/bin/X11/xdm
tess-turbo:/home/alex# ps -C xdm
  PID TTY          TIME CMD
tess-turbo:/home/alex# cat /etc/X11/xdm/Xservers
# $Xorg: Xserv.ws.cpp,v 1.3 2000/08/17 19:54:17 cpqbld Exp $
#
# Xservers file, workstation prototype
#
# This file should contain an entry to start the server on the
# local display; if you have more than one display (not screen),
# you can add entries to the list (one per line).  If you also
# have some X terminals connected which do not support XDMCP,
# you can add them here as well.  Each X terminal line should
# look like:
#       XTerminalName:0 foreign
#
# When adding X servers, please keep the following things in mind:
# - For each X server other than :0, the display number must be on the
# command
#   line.
# - This is the place to add the -bpp option to the command line.
# - It is wise to add the vtXX option to each local X server, since this
# is
#   the only sure way of knowing in advance which X server attaches to
# which
#   console.
# - See the Xserver(1) manpage for a description of X server options.
#
# Examples for multiple local X displays:
# :0 local /usr/X11R6/bin/X :0 vt9 -bpp 16
# :1 local /usr/X11R6/bin/X :1 vt10 -bpp 8
:0 local /usr/X11R6/bin/X vt7 -dpi 100 -nolisten tcp



Reply to: