From: Marco Atzeri <marco.atzeri@gmail.com>
To: cygwin@cygwin.com
Subject: XtoW 20160323-1 feedback
Date: Thu, 24 Mar 2016 21:37:00 -0000 [thread overview]
Message-ID: <56F45E05.4090302@gmail.com> (raw)
In-Reply-To: <announce.56F2ABA6.9000301@dronecode.org.uk>
[-- Attachment #1: Type: text/plain, Size: 1870 bytes --]
On 23/03/2016 15:43, Jon Turney wrote:
>
> The following packages have been updated in the Cygwin distribution:
>
> *** XtoW-20160323-1
>
On W7 - Cygwin X86_64
- first run of urxvt ignore font size settings from
.Xdefaults / .Xresources.
The second run uses it.
- xwin-xdg-menu and urxvt doesn't work very well
xwin-xdg-menu takes 23% of CPU time running 1 urxvt process
~46 for 2 urxvt and ~53 % with 3.
No negative effect running multiples xterm's
- UK Keyboard layout not recognized. Keys seem a US like
- Changing Windows Keyboard Layout to DE has no effect
- startxtow output has different info than log file
attached both.
Logging the full output I noticed
--------------------------------------------
DwmEnableBlurBehindWindow failed: 80263001, 0
-----------------------------------------------
This is continuously repeated every time a key is pressed
in the fist urxvt but not in the second lunched as "urxvt &"
Closing urxvt processes produces:
--------------------------------------------
DwmEnableBlurBehindWindow failed: 80263001, 0
_xcwm_atoms_set_wm_state: XID 0x00600009 state 0
xwinclip: winClipboardProc - X connection ready, pumping X event queue
xwinclip: winClipboardFlushXEvents - XFixesSetSelectionOwnerNotify
xwinclip: MonitorSelection - PRIMARY - Going from owned to not owned.
xwinclip: MonitorSelection - PRIMARY - Now owned by XID 0
xwinclip: winClipboardFlushXEvents - No window, returning.
Error received in event loop.
Error code: 3
ID: 0x00600009
Major opcode: 18
Minor opcode: 0
Error received in event loop.
Error code: 3
ID: 0x00600009
Major opcode: 18
Minor opcode: 0
Error received in event loop.
Error code: 3
ID: 0x00600009
Major opcode: 10
Minor opcode: 0
Error received in event loop.
Error code: 148
ID: 0x00a00007
Major opcode: 142
Minor opcode: 2
-------------------------------------------------
[-- Attachment #2: startxtow.log.xz --]
[-- Type: application/octet-stream, Size: 2108 bytes --]
[-- Attachment #3: Xorg.0.log.xz --]
[-- Type: application/octet-stream, Size: 2648 bytes --]
[-- Attachment #4: Type: text/plain, Size: 218 bytes --]
--
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 prev parent reply other threads:[~2016-03-24 21:37 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <50D34EDE.3010608@dronecode.org.uk>
[not found] ` <51FF75EA.3080101@dronecode.org.uk>
2016-03-23 14:59 ` [ANNOUNCEMENT] Updated: XtoW 20160323-1 (experimental) Jon Turney
2016-03-24 9:12 ` Marco Atzeri
2016-03-24 13:04 ` Jon Turney
2016-03-24 21:37 ` Marco Atzeri [this message]
[not found] ` <56F2ABA6.9000301@dronecode.org.uk>
2023-05-21 15:40 ` [ANNOUNCEMENT] " 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=56F45E05.4090302@gmail.com \
--to=marco.atzeri@gmail.com \
--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).