Bug 21301

Created attachment 24966 [details]
Script for compiling Xorg

export PACK_VERSION=7.4 &&
export MESA_VERSION=7.4 &&
tar jxf MesaLib-${MESA_VERSION}.tar.bz2 &&
tar jxf MesaGLUT-${MESA_VERSION}.tar.bz2 &&
tar jxf MesaDemos-${MESA_VERSION}.tar.bz2 &&
cd Mesa-${MESA_VERSION} &&
sed -i configs/linux-dri* -e "s@/usr/X11R6@/usr/X11R7@g" -e "s/-DHAVE_ALIAS/& -DGLX_USE_TLS/" &&
sed -i 's@X11R6/lib/modules@X11R7/lib/xorg/modules@' configs/default &&
sed -i 's@X11R6/lib/modules@X11R7/lib/xorg/modules@' src/glx/x11/dri_glx.c &&
cd .. &&
export CONFFLAGS='--sysconfdir=/etc --datadir=/usr/share --mandir=/usr/X11R7/man --localstatedir=/var --with-cursorpath="\~/.cursors:/usr/share/cursors" --with-mapdir=/usr/share/fonts/util --with-fontdir=/usr/share/fonts
 --with-top-fontdir=/usr/share/fonts --with-encodingsdir=/usr/share/fonts/encodings' &&
export xorg_server='--enable-nptl --enable-glx-tls --enable-ipv6 --enable-dri --enable-dmx --enable-xvfb --enable-xnest --enable-composite --enable-xcsecurity --enable-xorg --enable-xtrap --enable-xevie --disable-xprint --with-dri-driver-path=/usr/X11R7/lib/dri' &&
/src/scripts/build-X11R7 -m $PWD/Mesa-${MESA_VERSION} -lzma /usr/X11R7

Created attachment 24967 [details]
Xorg config generated by xorg -configure

Created attachment 24968 [details]
trace file

The screen stay black a the line 17048 of the strace file and after this line i try to launch a program on the display from another computer.

Created attachment 24969 [details]
trace file

The screen stay black a the line 18565 of the trace file after this line i try to launch some program on the display from another computer

every Xorg i've tried does that if you don't use open/fail as seen below.  why don't ask me (there is no fail in the logs)

00000000000000000000000

welcome to why you should be running telnet so you can get it back !

sometimes blind typeing gets it back

alt-leftarrow (linux key) change to prev virt term
ctrl-alt-backpace (xorg - but changed recently?) close down Xorg

after you do the above you may be at virtual terminal and not see plain text.  if that is so blind type:

$chvt 1
$vbetool vbemode set 3
$vbetool dpms on

if that didn't work and your telnet'ed in.  keep trying you'll most likely get it back.

---------------------

every Xorg i've tried does that if you don't use open/fail as seen below.  why don't ask me (there is no fail in the logs)

that's right.  your logs say mouse ok, you get black screen, but mouse is ok, but when you allow mouseopen fail: you see the bright shiny login

Section "ServerFlags"
        # use ctrl-alt-div to grab keyboard back
        Option "AllowDeactivateGrabs" "on"
        Option "AllowClosedownGrabs" "on"
        Option "AllowMouseOpenFail" "on"
        Option "AllowEmptyInput" "off"
EndSection

------------------------------
be careful to be sure you have right /usr/share/X11/xkb/

if your no X wiz kid, you need to install an X login suite such as xdm-options, kdm, gdm, (others).  which set file perms, start services, so that X login is running

that's right: if you try to run X as root without stuff setup: expect a black screen

-----------------------------
really this isn't a bug posting.  you didn't show your logs, your version, machine your running, anything you've gone through to resolve

there are many linux forums to ask new questions

leave bug tracking system for real repeatable bugs, ones that are not simply due to lack of reading and or participating in online discussions

if your compiling then

1) at runtime it needs a T symbol (see nm(1) ) and crashes without a coherent message


2) you linked but some .o were out of date.  or you installed into a 1/2 and 1/2 old and new directory.  (ie, mv /usr/local /usr/local.old ; # now install all )

3) you have an off-brand video card (likely not reason why) try 'vesa' driver see if that works

after that it , in Xorg.0.log you should see keyboard and mouse

if you have no keyboard mouse after video driver, i'd guess it crashed upon opening, which tells you nearly what is missing.

Please file a new bug if you still see issues with 1.20.