This is the mail archive of the cygwin mailing list for the Cygwin project.

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]
Other format: [Raw text]

Re: XWin won't run xterm on start

Dear Marco:

So, are you saying that not starting xterm is by design?

The manpage above is a bit outdated; creating a .startxwinrc with

xrdb -load $HOME/.Xresources
xbiff -geometry -430+5 &
oclock -geometry 75x75-0-0 &
xload -geometry -80-0 &
xterm -geometry +0+60 -ls &
xterm -geometry +0-100 &
xconsole -geometry -0+0 -fn 5x7 &
exec fbpanel -profile multiwindow

and running startxwin from the text console results in

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
OS: CYGWIN_NT-6.3 dell_vostro 2.4.1(0.293/5/3) 2016-01-24 11:26 x86_64
OS: Windows 8.1  [Windows NT 6.3 build 9600] (Win64)
Package: version 1.18.1-1 built 2016-02-18

XWin was started with the following command line:

/usr/bin/XWin :0 -multiwindow -auth /home/admin/.serverauth.2104

(II) xorg.conf is not supported
(II) See for more information
LoadPreferences: /home/admin/.XWinrc not found
LoadPreferences: Loading /etc/X11/system.XWinrc
LoadPreferences: Done parsing the configuration file...
winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL
winDetectSupportedEngines - Returning, supported engines 00000005
winSetEngine - Multi Window or Rootless => ShadowGDI
winScreenInit - Using Windows display depth of 32 bits per pixel
winAllocateFBShadowGDI - Creating DIB with width: 3520 height: 1080 depth: 32
winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32
MIT-SHM extension disabled due to lack of kernel support
XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll'
(II) AIGLX: Testing pixelFormatIndex 1
GL_VERSION:     3.1.0 - Build
GL_VENDOR:      Intel
GL_RENDERER:    Intel(R) HD Graphics 3000
(II) AIGLX: enabled GLX_SGI_make_current_read
(II) AIGLX: enabled GLX_MESA_copy_sub_buffer
(II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control
(II) AIGLX: enabled GLX_SGIX_pbuffer
(II) AIGLX: enabled GLX_ARB_multisample and GLX_SGIS_multisample
(II) 60 pixel formats reported by wglGetPixelFormatAttribivARB
(II) AIGLX: Set GLX version to 1.4
(II) 15 fbConfigs
(II) ignored pixel formats: 0 not OpenGL, 6 RBGA float, 3 RGBA unsigned float, 0 unknown pixel type, 36 unaccelerated
(II) GLX: Initialized Win32 native WGL GL provider for screen 0
winPointerWarpCursor - Discarding first warp: 1760 540
(--) 3 mouse buttons found
(--) Setting autorepeat to delay=500, rate=31
(--) Windows keyboard layout: "00000407" (00000407) "German", type 4
(--) Found matching XKB configuration "German (Germany)"
(--) Model = "pc105" Layout = "de" Variant = "none" Options = "none"
Rules = "base" Model = "pc105" Layout = "de" Variant = "none" Options = "none"
winInitMultiWindowWM - DISPLAY=:0.0
winMultiWindowXMsgProc - DISPLAY=:0.0
winMultiWindowXMsgProc - xcb_connect() returned and successfully opened the display.
winProcEstablishConnection - winInitClipboard returned.
winClipboardThreadProc - DISPLAY=:0.0
OS maintains clipboard viewer chain: yes
winInitMultiWindowWM - xcb_connect () returned and successfully opened the display.
winClipboardProc - XOpenDisplay () returned and successfully opened the display.
xrdb: No such file or directory
xrdb: can't open file '/home/admin/.Xresources'
/home/admin/.startxwinrc: Zeile 2: xbiff: Kommando nicht gefunden.
/home/admin/.startxwinrc: Zeile 3: oclock: Kommando nicht gefunden.
/home/admin/.startxwinrc: Zeile 4: xload: Kommando nicht gefunden.
/home/admin/.startxwinrc: Zeile 7: xconsole: Kommando nicht gefunden.
fbpanel: unknown option - -profile
fbpanel 6.1 - lightweight GTK2+ panel for UNIX desktops
Command line options:
--help      -- print this help and exit
--version   -- print version and exit
--log <number> -- set log level 0-5. 0 - none 5 - chatty
--configure -- launch configuration utility
--profile name -- use specified profile

-h  -- same as --help
-p  -- same as --profile
-v  -- same as --version
-C  -- same as --configure

Visit for detailed documentation,

xinit: connection to X server lost

waiting for X server to shut down winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop.
winClipboardProc - XDestroyWindow succeeded.
winMultiWindowXMsgProc - Fatal error 1 on xcb connection
winDeinitMultiWindowWM - Noting shutdown in progress
(II) Server terminated successfully (0). Closing log file.

Adding one more hyphen in front of -profile leads to two xterm windows. However, there are lots of other errors on the console. Said that, what would be an appropriate .startxwinrc or /etc/X11/xinit/startxwinrc for getting one (not two) xterm? Better, one uxterm?


Problem reports:
Unsubscribe info:

Index Nav: [Date Index] [Subject Index] [Author Index] [Thread Index]
Message Nav: [Date Prev] [Date Next] [Thread Prev] [Thread Next]