public inbox for cygwin-xfree@sourceware.org help / color / mirror / Atom feed
From: GEORGE BARRICK <gbarrick@kent.edu> To: cygwin-xfree@cygwin.com Subject: Dfficulty with xorg-server-1.17.1-2. Date: Tue, 24 Feb 2015 18:13:00 -0000 [thread overview] Message-ID: <CAKST5xOu6paHhw=upDLk26Xe7_8xKiLM=M5V1LSJ8SKix8WCUw@mail.gmail.com> (raw) 2015.02.24.09:26:38 EST Hey cygwin folks, I've been using xlaunch with a windows desktop shortcut for about a year to start a multi-window instance of xwin on my Win7 computers. This is cygwin32 on an installation of Win7_x86-64. The command within the shortcut is: C:\cygwin\bin\run.exe /usr/bin/Xlaunch.exe -run ~/config/config.xlaunch and I've defined the ~-directory to be C:\cygwin\home\gbarrick using the HOME variable in the Win7 environment. My .xlaunch-file is just: <file: C:/cygwin/home/gbarrick/config/config.xlaunch > <?xml version="1.0" encoding="UTF-8"?> <XLaunch WindowMode="MultiWindow" ClientMode="StartProgram" LocalClient="True" Display="0" RemoteProtocol="" LocalProgram="xterm -rw -sb -rightbar -geometry 128x44+72+60 -bg goldenrod" RemoteProgram="" RemoteHost="" RemoteUser="" XDMCPHost="" XDMCPBroadcast="False" XDMCPIndirect="False" Clipboard="True" ExtraParams="" Wgl="True" DisableAC="False" XDMCPTerminate="False" SSHKeyChain="False" SSHTerminal="True" ExtraSSH=""/> </file> (without the "file:"-tags). This setup successfully gives me the multi-window instance of xwin, and generates a /var/log/xwin/Xwin.0.log file as follows. The only thing that I've done is to edit the log-file to better fit the width for an e-mail message. <file: C:/cygwin/var/log/xwin/xwin.0.log > Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.16.3.0 OS: CYGWIN_NT-6.1-WOW WC-BARRICK 1.7.34(0.285/5/3) 2015-02-04 12:12 i686 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64) Package: version 1.16.3-1 built 2014-12-30 XWin was started with the following command line: XWin :0 -multiwindow -clipboard -wgl ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1680 h 1050 winInitializeScreenDefaults - native DPI x 120 y 120 [ 1668.181] (II) xorg.conf is not supported [ 1668.181] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 1668.181] LoadPreferences: /home/gbarrick/.XWinrc not found [ 1668.212] LoadPreferences: Loading /etc/X11/system.XWinrc [ 1668.227] LoadPreferences: Done parsing the configuration file... [ 1668.243] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [ 1668.259] winDetectSupportedEngines - Returning, supported engines 00000015 [ 1668.259] winSetEngine - Multi Window or Rootless => ShadowGDI [ 1668.259] winScreenInit - Using Windows display depth of 32 bits per pixel [ 1668.259] winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 [ 1668.259] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [ 1668.259] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [ 1668.274] MIT-SHM extension disabled due to lack of kernel support [ 1668.305] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [ 1668.337] glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll' [ 1668.586] (II) AIGLX: Testing pixelFormatIndex 1 [ 1668.773] GL_VERSION: 2.1.0 - Build 8.15.10.2869 [ 1668.773] GL_VENDOR: Intel [ 1668.773] GL_RENDERER: Intel(R) 4 Series Internal Chipset [ 1668.773] (II) AIGLX: enabled GLX_SGI_make_current_read [ 1668.773] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 1668.773] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 1668.773] (II) AIGLX: enabled GLX_SGIX_pbuffer [ 1668.773] (II) 51 pixel formats reported by wglGetPixelFormatAttribivARB [ 1668.773] (II) AIGLX: Set GLX version to 1.3 [ 1668.789] (II) 6 fbConfigs [ 1668.789] (II) ignored pixel formats: 0 not OpenGL, 6 RBGA float, 3 RGBA unsigned float, 0 unknown pixel type, 36 unaccelerated [ 1668.789] (II) GLX: Initialized Win32 native WGL GL provider for screen 0 [ 1669.678] winPointerWarpCursor - Discarding first warp: 840 525 [ 1669.678] (--) 3 mouse buttons found [ 1669.678] (--) Setting autorepeat to delay=500, rate=31 [ 1669.678] (--) Windows keyboard layout: "00000409" (00000409) "US", type 4 [ 1669.678] (--) Found matching XKB configuration "English (USA)" [ 1669.678] (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none" [ 1669.678] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" [ 1669.694] winMultiWindowXMsgProc - DISPLAY=:0.0 [ 1669.694] winInitMultiWindowWM - DISPLAY=:0.0 [ 1669.694] winProcEstablishConnection - winInitClipboard returned. [ 1669.694] winClipboardThreadProc - DISPLAY=:0.0 [ 1669.694] OS maintains clipboard viewer chain: yes [ 1669.694] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [ 1669.694] winClipboardProc - XOpenDisplay () returned and successfully opened the display. [ 1669.694] winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. </file> OK. Now for the difficulty. I recently (today) updated my cygwin system to include the newest xorg-server, xorg-server-common and xorg-server-dmx (the 1.17.1-2 versions) as well as xf86-video-dummy_0.3.7-3 xf86-video-nested-0.1.0-6 and xinit_1.3.4-5, and have found that xlaunch no longer seems capable of finding my .xlaunch-file. It starts X as before, but does not automatically spin up the xterm that my .xlaunch-file requests. I wind up having to start an xterm manually from the xwin "Applications" menu. In summary, I have changed _nothing_ except for the new X-stuff, and have this problem. The log-file from xwin does not seem radically different: <file: C:/cygwin/var/log/xwin/xwin.0.log > Welcome to the XWin X Server Vendor: The Cygwin/X Project Release: 1.17.1.0 OS: CYGWIN_NT-6.1-WOW WC-BARRICK 1.7.34(0.285/5/3) 2015-02-04 12:12 i686 OS: Windows 7 Service Pack 1 [Windows NT 6.1 build 7601] (WoW64) Package: version 1.17.1-2 built 2015-02-23 XWin was started with the following command line: XWin :0 -multiwindow -clipboard -wgl ddxProcessArgument - Initializing default screens winInitializeScreenDefaults - primary monitor w 1680 h 1050 winInitializeScreenDefaults - native DPI x 120 y 120 [ 4313.630] (II) xorg.conf is not supported [ 4313.630] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information [ 4313.630] LoadPreferences: /home/gbarrick/.XWinrc not found [ 4313.630] LoadPreferences: Loading /etc/X11/system.XWinrc [ 4313.630] LoadPreferences: Done parsing the configuration file... [ 4313.646] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL [ 4313.646] winDetectSupportedEngines - Returning, supported engines 00000005 [ 4313.646] winSetEngine - Multi Window or Rootless => ShadowGDI [ 4313.646] winScreenInit - Using Windows display depth of 32 bits per pixel [ 4313.661] winAllocateFBShadowGDI - Creating DIB with width: 1680 height: 1050 depth: 32 [ 4313.661] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff [ 4313.661] winInitVisualsShadowGDI - Masks 00ff0000 0000ff00 000000ff BPRGB 8 d 24 bpp 32 [ 4313.661] MIT-SHM extension disabled due to lack of kernel support [ 4313.692] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel [ 4313.692] glWinSelectGLimplementation: Loaded 'cygnativeGLthunk.dll' [ 4313.708] (II) AIGLX: Testing pixelFormatIndex 1 [ 4313.724] GL_VERSION: 2.1.0 - Build 8.15.10.2869 [ 4313.724] GL_VENDOR: Intel [ 4313.724] GL_RENDERER: Intel(R) 4 Series Internal Chipset [ 4313.724] (II) AIGLX: enabled GLX_SGI_make_current_read [ 4313.724] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer [ 4313.724] (II) AIGLX: enabled GLX_SGI_swap_control and GLX_MESA_swap_control [ 4313.724] (II) AIGLX: enabled GLX_SGIX_pbuffer [ 4313.724] (II) 51 pixel formats reported by wglGetPixelFormatAttribivARB [ 4313.739] (II) AIGLX: Set GLX version to 1.3 [ 4313.739] (II) 6 fbConfigs [ 4313.739] (II) ignored pixel formats: 0 not OpenGL, 6 RBGA float, 3 RGBA unsigned float, 0 unknown pixel type, 36 unaccelerated [ 4313.739] (II) GLX: Initialized Win32 native WGL GL provider for screen 0 [ 4313.926] winPointerWarpCursor - Discarding first warp: 840 525 [ 4313.926] (--) 3 mouse buttons found [ 4313.926] (--) Setting autorepeat to delay=500, rate=31 [ 4313.926] (--) Windows keyboard layout: "00000409" (00000409) "US", type 4 [ 4313.926] (--) Found matching XKB configuration "English (USA)" [ 4313.926] (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none" [ 4313.926] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none" [ 4313.926] winInitMultiWindowWM - DISPLAY=:0.0 [ 4313.926] winMultiWindowXMsgProc - DISPLAY=:0.0 [ 4313.926] winProcEstablishConnection - winInitClipboard returned. [ 4313.926] winClipboardThreadProc - DISPLAY=:0.0 [ 4313.926] OS maintains clipboard viewer chain: yes [ 4313.926] winInitMultiWindowWM - XOpenDisplay () returned and successfully opened the display. [ 4313.926] winMultiWindowXMsgProc - XOpenDisplay () returned and successfully opened the display. [ 4313.926] winClipboardProc - XOpenDisplay () returned and successfully opened the display. [ 4328.575] executing 'xterm', pid 3100 [ 4328.746] (pid 3100 stderr) Warning: Missing charsets in String to FontSet conversion </file> The other notable problem to report is that my X-server now crashes after about 5-10 minutes of use. Since this issue does not get reported in xwin.0.log or xwin.0.log.old, I do not yet know how to provide more information. Is it possible that the new xinit is the cause of the problem? I noticed that there's some mention in the cygwin-x mailing list of the -listen -nolisten flags; but I do not know enough to figure out whether it's relevant to my issue. Also, should I really have all six of these X-packages for a cygwin system that does not use 3D/high-end video? Note: I installed the font packages font-isas-misc, font-jis-misc and font-daewoo-misc to try and obviate the xterm warning, but this does not change the nature of the problem. If everything that I reported seems to be OK, and my message does not strike any bells in people's brains, can you point me towards a test or further gathering of data that might help to reproduce and circumvent this minor difficulty? Thanks, George gee_barrick_at_kent_dot_edu P.S. Excuse verbosity of this report; I've tried to give complete description. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
next reply other threads:[~2015-02-24 18:13 UTC|newest] Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top 2015-02-24 18:13 GEORGE BARRICK [this message] 2015-02-24 19:36 ` Jim Reisert AD1C 2015-02-24 21:39 ` Jon TURNEY 2015-02-24 21:50 ` Jon TURNEY 2015-02-25 1:36 ` GEORGE BARRICK 2015-02-25 17:23 ` GEORGE BARRICK [not found] ` <54F2077C.9080802@dronecode.org.uk> 2015-03-01 14:06 ` GEORGE BARRICK 2015-02-25 13:26 ` Jim Reisert AD1C 2015-02-25 14:30 ` Jim Reisert AD1C 2015-02-25 17:22 ` Jon TURNEY 2015-02-24 21:44 ` Jon TURNEY
Reply instructions: You may reply publicly to this message via plain-text email using any one of the following methods: * Save the following mbox file, import it into your mail client, and reply-to-all from there: mbox Avoid top-posting and favor interleaved quoting: https://en.wikipedia.org/wiki/Posting_style#Interleaved_style * Reply using the --to, --cc, and --in-reply-to switches of git-send-email(1): git send-email \ --in-reply-to='CAKST5xOu6paHhw=upDLk26Xe7_8xKiLM=M5V1LSJ8SKix8WCUw@mail.gmail.com' \ --to=gbarrick@kent.edu \ --cc=cygwin-xfree@cygwin.com \ /path/to/YOUR_REPLY https://kernel.org/pub/software/scm/git/docs/git-send-email.html * If your mail client supports setting the In-Reply-To header via mailto: links, try the mailto: linkBe sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions for how to clone and mirror all data and code used for this inbox; as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).