wmaker fatal error: could not open display ":0"

2003-07-19 Thread digitalsmear
Having trouble getting X to run...  The worst part about  this is that I
had it working a few hours ago, but I uninstalled and reinstalled becaused
I foobared my package choices and vim couldn't find some resource.  So
atleast I know it's a configuration problem.  Now to pin it down...

I am using WindowsXP Home Ed. SP1
When I attempt to startx I get the following:
-
$ startx
waiting for X server to shut down
$ wmaker fatal error: could not open display ":0"
-
I've also tried:
- 
$ startx -display ":1" // I've tried it as 1, :1 and ":1" with
the same response
/usr/X11R6/bin/xterm Xt error: Can't open display: :1
waiting for X server to shut down
-

My XWin.log from just the command "startx" reads as...

- $ cat XWin.log -
ddxProcessArgument - Initializing default screens
winInitializeDefaultScreens - w 1024 h 768
winInitializeDefaultScreens - Returning
OsVendorInit - Creating bogus screen 0
_XSERVTransmkdir: Owner of /tmp/.X11-unix should be set to root
(EE) Unable to locate/open config file
InitOutput - Error reading config file
winDetectSupportedEngines - Windows NT/2000/XP
winDetectSupportedEngines - DirectDraw installed
winDetectSupportedEngines - Allowing PrimaryDD
winDetectSupportedEngines - DirectDraw4 installed
winDetectSupportedEngines - Returning, supported engines 001f
InitOutput - g_iNumScreens: 1 iMaxConsecutiveScreen: 1
winSetEngine - Using Shadow DirectDraw NonLocking
winAdjustVideoModeShadowDDNL - Using Windows display depth of 32 bits per
pixel
winCreateBoundingWindowWindowed - User w: 1024 h: 768
winCreateBoundingWindowWindowed - Current w: 1024 h: 768
winAdjustForAutoHide - Original WorkArea: 0 0 768 1024
winAdjustForAutoHide - Taskbar is auto hide
winAdjustForAutoHide - Found BOTTOM auto-hide taskbar
winAdjustForAutoHide - Adjusted WorkArea: 0 0 767 1024
winCreateBoundingWindowWindowed - WindowClient w 1018 h 735 r 1018 l 0 b
735 t 0
winCreateBoundingWindowWindowed -  Returning
winCreatePrimarySurfaceShadowDDNL - Creating primary surface
winCreatePrimarySurfaceShadowDDNL - Created primary surface
winCreatePrimarySurfaceShadowDDNL - Attached clipper to primary surface
winAllocateFBShadowDDNL - lPitch: 4072
winAllocateFBShadowDDNL - Created shadow pitch: 4072
winAllocateFBShadowDDNL - Created shadow stride: 1018
winFinishScreenInitFB - Masks: 00ff ff00 00ff
winInitVisualsShadowDDNL - Masks 00ff ff00 00ff BPRGB 8 d 24
bpp 32
winCreateDefColormap - Deferring to fbCreateDefColormap ()
winFinishScreenInitFB - returning
winScreenInit - returning
InitOutput - Returning.
(EE) No primary keyboard configured
(==) Using compiletime defaults for keyboard
Rules = "xfree86" Model = "pc101" Layout = "us" Variant = "(null)" Options
= "(null)"
winPointerWarpCursor - Discarding first warp: 509 367
winBlockHandler - Releasing pmServerStarted
winBlockHandler - pthread_mutex_unlock () returned
- END XWin.log -

And my cygwin.bat file reads

- cygwin.bat -
@echo off

set DISPLAY=127.0.0.1:0.0
set CYGWIN=tty notitle glob
set HOME=C:\cygwin\home

PATH=C:\cygwin\bin;C:\cygwin\sbin;C:\cygwin\usr\bin;C:\cygwin\usr\sbin;C:\cy
gwin\usr\local\bin;C:\cygwin\usr\X11R6\bin;..

C:
chdir C:\cygwin\bin

bash --login -i
- END cygwin.bat -


Last but not least... my .xinitrc file looks like this...

- $ cat .xinitrc -
#!/bin/sh
# $Xorg: xinitrc.cpp,v 1.3 2000/08/17 19:54:30 cpqbld Exp $

userresources=$HOME/.Xresources
usermodmap=$HOME/.Xmodmap
sysresources=/usr/X11R6/lib/X11/xinit/.Xresources
sysmodmap=/usr/X11R6/lib/X11/xinit/.Xmodmap

# merge in defaults and keymaps

if [ -f $sysresources ]; then
xrdb -merge $sysresources
fi

if [ -f $sysmodmap ]; then
xmodmap $sysmodmap
fi

if [ -f $userresources ]; then
xrdb -merge $userresources
fi

if [ -f $usermodmap ]; then
xmodmap $usermodmap
fi

# start some nice programs

# twm &
# xclock -geometry 50x50-1+1 &
# xterm -geometry 80x50+494+51 &
# xterm -geometry 80x20+494-0 &
# exec xterm -geometry 80x66+0+0 -name login

wmaker &
- END $ cat .xinitrc -


Heeelllp! :P

_
Free email with personality! Over 200 domains!
http://www.MyOwnEmail.com
Looking for friendships,romance and more?
http://www.MyOwnFriends.com



Re: wmaker fatal error: could not open display ":0"

2003-07-19 Thread Andrew Markebo
What happens if you try "startxwin.sh"? Thats how I pull up my
xwindows.

 /Andy

/ "digitalsmear" <[EMAIL PROTECTED]> wrote:
| Having trouble getting X to run...  The worst part about  this is that I
| had it working a few hours ago, but I uninstalled and reinstalled becaused
| I foobared my package choices and vim couldn't find some resource.  So
| atleast I know it's a configuration problem.  Now to pin it down...
|
| I am using WindowsXP Home Ed. SP1
| When I attempt to startx I get the following:
| -
| $ startx
| waiting for X server to shut down
| $ wmaker fatal error: could not open display ":0"

-- 
 The parser of the compiler rests on the code!

Please note, new email, @telia.com -> @comhem.se