How to debug XWin starting only sometimes?

How to debug XWin starting only sometimes?

[Leon Meier]

When starting "XWin Server" though the windows shortcut, it sometimes 
won't start; other times it will.

The shortcut command line is

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

which is executed in directory cygwin64.

The current contents of .xsession-errors is

[
** Message: couldn't connect to dbus session bus: Verbindung ist geschlossen
** Message: couldn't connect to dbus session bus: Verbindung ist geschlossen
** Message: couldn't connect to dbus session bus: Verbindung ist geschlossen
Socket /tmp/fam-admin/fam- has wrong permissions
]

As you can imagine, the directory /tmp/fam-admin contains no files at all.

Starting startxwin from mintty actually succeeds (always or at least 
more often than starting through the shortcut).

The only suspicious lines found in /var/log/xwin/XWin.0.log are

[  1106.609] pixelFormat 36: has 1 overlay, 0 underlays which aren't 
currently handledgetAttrValue failed to find attr 0x2039, using default 
value 0
[  1106.609] getAttrValue failed to find attr 0x203b, using default value 0
...
[  1106.609] pixelFormat 71: has 1 overlay, 0 underlays which aren't 
currently handledgetAttrValue failed to find attr 0x2039, using default 
value 0
[  1106.609] getAttrValue failed to find attr 0x203b, using default value 0
...
[  1294,453] SetupSysMenu: GetSystemMenu() failed for HWND 0x2027a
[  1309,640] IsOverrideRedirect: Failed to get window attributes
[  1311,687] OS has icon alpha channel support: yes
[  1353,109] SetupSysMenu: GetSystemMenu() failed for HWND 0x50374
[  1359,250] SetupSysMenu: GetSystemMenu() failed for HWND 0x50330
[  1367,859] winTopLevelWindowProc - WM_DESTROY - WM_WM_KILL
[  1378,000] SetupSysMenu: GetSystemMenu() failed for HWND 0x1c0466


In /var/log/xwin/XWin.0.log.old we see

[   775,375] winMultiWindowXMsgProc - Fatal error 1 on xcb connection

In /var/log/xwin/XWin.1.log we see

[  1523,000] winMultiWindowXMsgProc - Fatal error 1 on xcb connection

In /var/log/xwin/XWin.1.log.old we see

[  1583,187] winMultiWindowXMsgProcErrorHandler - ERROR: BadMatch 
(invalid parameter attributes)

Any hints who may be the culprit and/or how to debug the issue?

Thanks in advance,
Leon

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: How to debug XWin starting only sometimes?

[Ian Lambert via cygwin]

On May 1, 2017 11:19:59 AM EDT, Leon Meier <Leon.Meier> wrote:
>
>Starting startxwin from mintty actually succeeds (always or at least 
>more often than starting through the shortcut).


This has been my experience as well. Not much recently, but now and then the black X appears, but the xdg-menu does not. Kill everything, start over, and it works. I don't use the start menu X shortcut, only mintty, then startxwin.


-- 
Sent from my Android device with K-9 Mail. Please excuse my brevity.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: How to debug XWin starting only sometimes?

[Jon Turney]

On 01/05/2017 16:19, Leon Meier wrote:
> When starting "XWin Server" though the windows shortcut, it sometimes
> won't start; other times it will.

Sorry to hear that you are having this problem.

[...]
> Any hints who may be the culprit and/or how to debug the issue?

It might be useful to compare the logs between an successful and 
unsuccessful startup attempt.  The differences might be a useful clue.

 > In /var/log/xwin/XWin.0.log.old we see
 >
 > [   775,375] winMultiWindowXMsgProc - Fatal error 1 on xcb connection

I'm guessing that perhaps this was from an unsuccessful previous run? 
In which case I would be interested to see the whole log.

-- 
Jon Turney
Volunteer Cygwin/X X Server maintainer

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: How to debug XWin starting only sometimes?

[Леон Майер]

>  > In /var/log/xwin/XWin.0.log.old we see
>  >
>  > [ 775,375] winMultiWindowXMsgProc - Fatal error 1 on xcb connection
>
> I'm guessing that perhaps this was from an unsuccessful previous run?
> In which case I would be interested to see the whole log.
I checked. The bad news is that neither .xsession-errors nor a log in /var/log/xwin/ are produced in /var/log/xwin on an *unsuccessful* attempt.

The *successful* attempt afterwards results in .xsession-errors containing

[
** Message: couldn't connect to dbus session bus: Verbindung ist geschlossen
** Message: couldn't connect to dbus session bus: Verbindung ist geschlossen
** Message: couldn't connect to dbus session bus: Verbindung ist geschlossen
Socket /tmp/fam-admin/fam- has wrong permissions
Failed to connect to socket /tmp/fam-admin/fam-
executing 'uxterm', pid 1512
]

and /var/log/xwin/XWin.0.log containing

[
[  9196.250] (II) AIGLX: enabled GLX_MESA_copy_sub_buffer
[  9196.250] (II) 503 pixel formats reported by wglGetPixelFormatAttribivARB
[  9196.250] pixelFormat 36: has 1 overlay, 0 underlays which aren't currently handledgetAttrValue failed to find attr 0x2039, using default value 0
[  9196.250] getAttrValue failed to find attr 0x203b, using default value 0
[  9196.250] pixelFormat 37: has 1 overlay, 0 underlays which aren't currently handledgetAttrValue failed to find attr 0x2039, using default value 0
[  9196.250] getAttrValue failed to find attr 0x203b, using default value 0
...
...(lots of similar lines differing only in one number)...
...
[  9196.250] pixelFormat 71: has 1 overlay, 0 underlays which aren't currently handledgetAttrValue failed to find attr 0x2039, using default value 0
[  9196.250] getAttrValue failed to find attr 0x203b, using default value 0
[  9196.250] (II) 468 fbConfigs
[  9196.250] (II) ignored pixel formats: 0 not OpenGL, 0 unknown pixel type, 35 unaccelerated
[  9196.250] (II) GLX: Initialized Win32 native WGL GL provider for screen 0
[  9196.578] winPointerWarpCursor - Discarding first warp: 960 540
[  9196.578] (--) 2 mouse buttons found
[  9196.578] (--) Setting autorepeat to delay=500, rate=31
[  9196.578] (--) Windows keyboard layout: "00000407" (00000407) "German", type 7
[  9196.578] (--) Found matching XKB configuration "German (Germany)"
[  9196.578] (--) Model = "pc105" Layout = "de" Variant = "none" Options = "none"
[  9196.578] Rules = "base" Model = "pc105" Layout = "de" Variant = "none" Options = "none"
[  9196.671] winInitMultiWindowWM - DISPLAY=:0.0
[  9196.671] winMultiWindowXMsgProc - DISPLAY=:0.0
[  9196.703] winInitMultiWindowWM - xcb_connect () returned and successfully opened the display.
[  9196.703] winProcEstablishConnection - winInitClipboard returned.
[  9196.703] winClipboardThreadProc - DISPLAY=:0.0
[  9196,703] winMultiWindowXMsgProc - xcb_connect() returned and successfully opened the display.
[  9196,703] OS maintains clipboard viewer chain: yes
[  9196,718] Using Composite redirection
[  9196,718] winClipboardProc - XOpenDisplay () returned and successfully opened the display.
[  9255,375] SetupSysMenu: GetSystemMenu() failed for HWND 0xb080c
]

Any ideas of how to debug next?

Thanks in advance.
Leon

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple

Re: How to debug XWin starting only sometimes? (Typo removed)

[Леон Майер]

> The bad news is that neither .xsession-errors nor a log in /var/log/xwin/ are produced in /var/log/xwin on an *unsuccessful* attempt.
The bad news is that neither .xsession-errors in the home directory nor a log in /var/log/xwin/ are produced on an *unsuccessful* attempt.

--
Problem reports:       http://cygwin.com/problems.html
FAQ:                   http://cygwin.com/faq/
Documentation:         http://cygwin.com/docs.html
Unsubscribe info:      http://cygwin.com/ml/#unsubscribe-simple