fonts and .xinitrc

fonts and .xinitrc

[send, send, send, send junk, junk, junk, junk]

Hello Cygwin,

I hope I am using this list as it is intended to be used.  My name is Mark, and I have been using Cygwin for as long as I can remember (maybe 20 years now?).   I have only used X11 in Cygwin sporadically, and am having trouble getting a few things to work that I think should be fairly common.  I’ve been researching the FAQs and docs and stacks and forums and Googles and so on, and progress has been quite slow.

For example, when I run xinit and include a .xinitrc file in my home directory, it seems to immediately crash.    Also, fonts seem to be an issue for me now, requiring an xft: prefix to get working (which took me most of the day yesterday to finally hack back to some level of functionality).    

When I try to run cfg.py (which is just a program to create a visual control flow graph for a given Python program), all the text is “blanked out” with boxes.    I am theorizing that this is related to the graphviz library not being compatible with the new definitions of fonts.

Trying to debug this, I ran a “hello world”  for tkinter, and the default font was basically just a few pixels high (very small on my 4K monitor).   Also, the default font is unreadably small.   I have to choose enormous in the default window manager to see anything.

I’ve looked at the docs on initialization and configuration for both Cygwin and Linux in general (which I’m also quite rusty on), but cannot seem to get anything to work.   My next plan is to revert to older versions to see what worked in the past.   (I think the last time I really used X in Cygwin rxvt could run without launching X which from the docs seems to be maybe a decade or two ago? Lol.)  I have a string of laptops starting from when I designed graphics chips for Compaq  in the 80’s, so I have a bit of history all set up to easily remember how I worked with startup files, etc., previously.

I currently have the latest Cygwin packages installed on my brand new gaming laptop (MSI GF65 Thin).   Here is the output of xinit when I include an empty .xinitrc: 

x@MSI ~
$ touch .xinitrc

x@MSI ~
$ xinit

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.21.1.3
OS: CYGWIN_NT-10.0-19042 MSI 3.3.4-341.x86_64 2022-01-31 19:35 UTC x86_64
OS: Windows 10  [Windows NT 10.0 build 19042] x64
Package: version 21.1.3-1 built 2022-01-14

XWin was started with the following command line:

X :0

(II) xorg.conf is not supported
(II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
winUpdateDpi - primary monitor native DPI x 192 y 192
LoadPreferences: Loading /home/x/.XWinrc
LoadPreferences: Done parsing my personal configuration file...
winDetectSupportedEngines - RemoteSession: no
winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL
winDetectSupportedEngines - Returning, supported engines 00000005
winSetEngine - Using Shadow DirectDraw NonLocking
winScreenInit - Using Windows display depth of 32 bits per pixel
winWindowProc - WM_SIZE - new client area w: 3814 h: 2009
winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
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
(EE) AIGLX: No native OpenGL in modes with a root window
(II) IGLX: Loaded and initialized swrast
(II) GLX: Initialized DRISWRAST GL provider for screen 0
winPointerWarpCursor - Discarding first warp: 1907 1004
(--) 5 mouse buttons found
(--) Setting autorepeat to delay=500, rate=31
(--) Windows keyboard layout: "00000409" (00000409) "US", type 7
(--) Found matching XKB configuration "English (USA)"
(--) Model = "pc105" Layout = "us" Variant = "none" Options = "none"
Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none"
winProcEstablishConnection - winInitClipboard returned.
winClipboardThreadProc - DISPLAY=:0.0
winClipboardProc - xcb_connect () returned and successfully opened the display.
xinit: connection to X server lost

waiting for X server to shut down winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop.
winDeinitMultiWindowWM - Noting shutdown in progress
(II) Server terminated successfully (0). Closing log file.


x@MSI ~
$


Here is my XWin.0.log:

Welcome to the XWin X Server
Vendor: The Cygwin/X Project
Release: 1.21.1.3
OS: CYGWIN_NT-10.0-19042 MSI 3.3.4-341.x86_64 2022-01-31 19:35 UTC x86_64
OS: Windows 10  [Windows NT 10.0 build 19042] x64
Package: version 21.1.3-1 built 2022-01-14

XWin was started with the following command line:

X :0 

ddxProcessArgument - Initializing default screens
winInitializeScreenDefaults - primary monitor w 3840 h 2160
[ 23420.234] (II) xorg.conf is not supported
[ 23420.234] (II) See http://x.cygwin.com/docs/faq/cygwin-x-faq.html for more information
[ 23420.234] winUpdateDpi - primary monitor native DPI x 192 y 192
[ 23420.234] LoadPreferences: Loading /home/x/.XWinrc
[ 23420.234] LoadPreferences: Done parsing my personal configuration file...
[ 23420.234] winDetectSupportedEngines - RemoteSession: no
[ 23420.296] winDetectSupportedEngines - DirectDraw4 installed, allowing ShadowDDNL
[ 23420.296] winDetectSupportedEngines - Returning, supported engines 00000005
[ 23420.296] winSetEngine - Using Shadow DirectDraw NonLocking
[ 23420.312] winScreenInit - Using Windows display depth of 32 bits per pixel
[ 23420.343] winWindowProc - WM_SIZE - new client area w: 3814 h: 2009
[ 23420.390] winFinishScreenInitFB - Masks: 00ff0000 0000ff00 000000ff
[ 23420.390] MIT-SHM extension disabled due to lack of kernel support
[ 23420.390] XFree86-Bigfont extension local-client optimization disabled due to lack of shared memory support in the kernel
[ 23420.390] (EE) AIGLX: No native OpenGL in modes with a root window
[ 23420.390] (II) IGLX: Loaded and initialized swrast
[ 23420.390] (II) GLX: Initialized DRISWRAST GL provider for screen 0
[ 23420.562] winPointerWarpCursor - Discarding first warp: 1907 1004
[ 23420.562] (--) 5 mouse buttons found
[ 23420.562] (--) Setting autorepeat to delay=500, rate=31
[ 23420.562] (--) Windows keyboard layout: "00000409" (00000409) "US", type 7
[ 23420.562] (--) Found matching XKB configuration "English (USA)"
[ 23420.562] (--) Model = "pc105" Layout = "us" Variant = "none" Options = "none"
[ 23420.562] Rules = "base" Model = "pc105" Layout = "us" Variant = "none" Options = "none"
[ 23420.609] winProcEstablishConnection - winInitClipboard returned.
[ 23420.609] winClipboardThreadProc - DISPLAY=:0.0
[ 23420.609] winClipboardProc - xcb_connect () returned and successfully opened the display.
[ 23420.656] winClipboardProc - winClipboardFlushWindowsMessageQueue trapped WM_QUIT message, exiting main loop.
[ 23420.671] winDeinitMultiWindowWM - Noting shutdown in progress
[ 23420.671] (II) Server terminated successfully (0). Closing log file.

Thanks!
Mark



Sent from Mail for Windows

Re: fonts and .xinitrc

[Jon Turney]

On 15/03/2022 12:27, send, send, send, send junk, junk, junk, junk wrote:
> 
> For example, when I run xinit and include a .xinitrc file in my home directory, it seems to immediately crash.     >
> I currently have the latest Cygwin packages installed on my brand new gaming laptop (MSI GF65 Thin).   Here is the output of xinit when I include an empty .xinitrc:
> 
> x@MSI ~
> $ touch .xinitrc

 From 'man xinit'

        "An important point is that programs which are run by .xinitrc 
should be run in the background if they do not exit right away, so that 
they don't prevent other programs from starting up.  However, the last 
long-lived program started (usually a window manager or terminal 
emulator) should be left in the foreground so that the script won't exit 
(which indicates that the user is done and that xinit should exit)."

It seems you are getting exactly what you are asking for with an empty 
~/.xinitrc.

[1] also mentions this.

[1] https://x.cygwin.com/docs/ug/using.html#using-starting-startx

FW: fonts and .xinitrc

[send, send, send, send junk, junk, junk, junk]

Thank you so much Jon.   I had tried a few .xinitrc files and I’m not sure why they didn’t work, but based on your clarification, I copied /etc/X11/xinit/xinitrc to ~/.xinitrc and that worked.   Does anyone have any suggestions on how to debug my font issue in graphviz?

Thanks!
Mark

Sent from Mail for Windows

From: Jon Turney
Sent: Tuesday, March 15, 2022 8:15 AM
To: send, send, send, send junk, junk, junk, junk; The Cygwin Mailing List
Subject: Re: fonts and .xinitrc

On 15/03/2022 12:27, send, send, send, send junk, junk, junk, junk wrote:
> 
> For example, when I run xinit and include a .xinitrc file in my home directory, it seems to immediately crash.     >
> I currently have the latest Cygwin packages installed on my brand new gaming laptop (MSI GF65 Thin).   Here is the output of xinit when I include an empty .xinitrc:
> 
> x@MSI ~
> $ touch .xinitrc

From 'man xinit'

        "An important point is that programs which are run by .xinitrc 
should be run in the background if they do not exit right away, so that 
they don't prevent other programs from starting up.  However, the last 
long-lived program started (usually a window manager or terminal 
emulator) should be left in the foreground so that the script won't exit 
(which indicates that the user is done and that xinit should exit)."

It seems you are getting exactly what you are asking for with an empty 
~/.xinitrc.

[1] also mentions this.

[1] https://x.cygwin.com/docs/ug/using.html#using-starting-startx

Re: fonts and .xinitrc

[Brian Inglis]

On 2022-03-15 06:27, send junk wrote:
> I hope I am using this list as it is intended to be used.  My name is Mark, and I have been using Cygwin for as long as I can remember (maybe 20 years now?).   I have only used X11 in Cygwin sporadically, and am having trouble getting a few things to work that I think should be fairly common.  I’ve been researching the FAQs and docs and stacks and forums and Googles and so on, and progress has been quite slow.
> 
> For example, when I run xinit and include a .xinitrc file in my home directory, it seems to immediately crash.    Also, fonts seem to be an issue for me now, requiring an xft: prefix to get working (which took me most of the day yesterday to finally hack back to some level of functionality).
> 
> When I try to run cfg.py (which is just a program to create a visual control flow graph for a given Python program), all the text is “blanked out” with boxes.    I am theorizing that this is related to the graphviz library not being compatible with the new definitions of fonts.
> 
> Trying to debug this, I ran a “hello world”  for tkinter, and the default font was basically just a few pixels high (very small on my 4K monitor).   Also, the default font is unreadably small.   I have to choose enormous in the default window manager to see anything.
> 
> I’ve looked at the docs on initialization and configuration for both Cygwin and Linux in general (which I’m also quite rusty on), but cannot seem to get anything to work.   My next plan is to revert to older versions to see what worked in the past.   (I think the last time I really used X in Cygwin rxvt could run without launching X which from the docs seems to be maybe a decade or two ago? Lol.)  I have a string of laptops starting from when I designed graphics chips for Compaq  in the 80’s, so I have a bit of history all set up to easily remember how I worked with startup files, etc., previously.

Install package xinit and some packages matching "fonts" from:

	unifont-fonts urw-base35-fonts{,-legacy}
	ghostscript-fonts-other gnu-free-fonts
	{liberation,linux-libertine}-fonts
	{alef,bitstream-vera,dejavu,fontawesome,inconsolata,tinos}-fonts
	{caladea,cantarell,carlito,cousine,culmus}-fonts
	{overpass,oxygen,sj,symbola}-fonts
	noto-fonts-common
	adobe-source-{code,sans,serif}-pro-font

I just execute a shortcut (at Windows login) which runs:

C:\...\cygwin64\bin\run.exe --quote /usr/bin/bash.exe -l \
				-c "cd; exec /usr/bin/startxwin"
[split for clarity]

-- 
Take care. Thanks, Brian Inglis, Calgary, Alberta, Canada

This email may be disturbing to some readers as it contains
too much technical detail. Reader discretion is advised.
[Data in binary units and prefixes, physical quantities in SI.]