From: Leon Meier <Leon.Meier@yandex.ru>
To: cygwin@cygwin.com
Subject: How to debug XWin starting only sometimes?
Date: Mon, 01 May 2017 15:20:00 -0000 [thread overview]
Message-ID: <3f551e8d-9f2a-27d4-119f-13f4a7ddb155@yandex.ru> (raw)
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
next reply other threads:[~2017-05-01 15:20 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-01 15:20 Leon Meier [this message]
2017-05-01 20:37 ` Ian Lambert via cygwin
2017-05-02 12:59 ` Jon Turney
2017-05-03 22:44 ` Леон Майер
2017-05-03 22:51 ` How to debug XWin starting only sometimes? (Typo removed) Леон Майер
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=3f551e8d-9f2a-27d4-119f-13f4a7ddb155@yandex.ru \
--to=leon.meier@yandex.ru \
--cc=cygwin@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: link
Be 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).