How to debug XWin starting only sometimes?

Леон Майер leon.meier@yandex.ru
Wed May 3 22:44:00 GMT 2017


>  > 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



More information about the Cygwin mailing list