Thanks: using of recent qt4 after update of XWin server
Yaakov, thanks for the promptly fix! The dependecy appears to be not so obosolete as I assumed :) Andrey -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
screen pixel density VS startxwin.exe
Dear all, For many years now, I used to set my screen pixel density to 90 pixels per inch, instead of the default 75 ppi, in the startxwin.bat file. My startxwin.bat used to be executed, then, at windows startup, to get a full functional Cygwin-X environment (at 90 ppi, by the way). Here is the commandline I did put in my startxwin.bat file: [...] run XWin -multiwindow -clipboard -dpi 90 [...] Then, I recently upgraded my Cygwin-X installation from 1.5.x to 1.7.x, and now the startxwin.bat script disappeared, replaced by the startxwin.exe binary. That did not trouble me much. Nevertheless, I'm not able to set my screen pixel density anymore, or at least, I did not found the way (config file, commandline argument, ...) to set it again. I tried, as target of XWin Server shortcut: `run C:\cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe -- -dpi 90' ^^^ In order to specify particular server options, append a double dash (−−) to the startxwin command line (after any client and arguments) followed by the desired server options., as it is said in the `man 1 startxwin'. Nevertheless, my option seems not to reach the server arguments, because, the screen pixel density of my Cygwin-X session remains stuck to 75ppi (as `xdpyinfo' reports). I also heard about a file called ~/.xserverrc to alter the way the Xserver is launched. But I did not found anything detailed about its content and how it shall be addressed. Finally, I also tried, through xrandr-1.3, to set the physical size of the screen (using --fbmm widthxheight) or the screen pixel density (using --dpi dpi). I was able to get a 90ppi screen pixel density *one time*, but was unable to reiterate. Then I'm wondering if I did not misread any output, thinking the screen pixel density changed, while it was not altered at all. Therefore, can anyone please give me a hint, on how to set again, my screen pixel density? Thanks a lot, to you all. Regards, -- Alexandre Beaugy -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: bug report/suggested temp. patch: handling bursts of sent keys
Hi.
I don't appear to have gotten any response to my message sent to
this list January 12 (copied below). Do I have the right list? Am I
supposed to use a different mechanism to report bugs with the Cygwin X
server? Please help.
- Thanks,
Mark
Background:
I use Nuance's Dragon NaturallySpeaking voice recognition software
to control remote Linux systems from a Windows box. I open up xterms
and emacs windows on a local Cygwin X server. Occasionally the voice
recognizer makes a mistake, which has to be corrected. The mechanics of
how this is done are unimportant; what matters is how Dragon applies the
correction. It does this by sending a large burst of keystrokes via
something like SendKeys. (E.g., many (shift) arrow keys to select the
text to be changed, a backspace to delete it, then the replacement
text.)
Unfortunately, there is a bug in the current released Cygwin X
server that causes it to drop sent keystrokes when the burst exceeds a
given size (roughly 64 or 128 keys depending on the version). This
breaks correction, and forces painful manual fix up of the text. Note
that what is really dropped are key events so the system can get into
the state where the shift key remains pressed or a key starts repeating
forever because the key up event was dropped.
Problem/temporary patch:
I investigated and found that the problem appears to be that the X
event queue (miEventQueue) in hw/mi/mieq.c is statically allocated with
a ridiculously small value (512). When keyboard bursts come in, this
queue overflows, causing the problem. If I set this queue to a more
reasonable value of 5120:
mieq.c:62:#define QUEUE_SIZE 5120/* was 512 */
then 10 times larger key bursts can be accommodated without problem.
This value is probably still too small in practice so it would be safer
to go with a larger value like 25000.
I characterize this as a temporary patch because ideally either the
queue would be made dynamic with no upper bound in size, or some kind of
flow control would be implemented so the code that receives Windows key
events does not overflow the event queue.
Reproducing the problem:
Dragon NaturallySpeaking costs money, so I will instead describe how
to demonstrate the problem using AutoHotkey, which is a free download
from http://www.autohotkey.com/. Download that program then create and
run the following script, burst.ahk:
cut here for burst.ahk
#space::
Send ** ** ** **
**{enter}** ** ** **
**{enter}** ** ** **
**{enter}** ** ** **
**{enter}** ** ** ** **{enter}
=
Finally, type the Windows key and space together while focus is on an X
application. The bug is not present, the following will be typed:
** ** ** ** **
** ** ** ** **
** ** ** ** **
** ** ** ** **
** ** ** ** **
On the other hand, if the bug is present you'll get something more like:
** ** ** ** **
** ** ** ** **
***
- Mark
--
Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple
Problem reports: http://cygwin.com/problems.html
Documentation: http://x.cygwin.com/docs/
FAQ: http://x.cygwin.com/docs/faq/
RE: X11 assertion fails
Carl R. Crawford sent the following at Tuesday, January 19, 2010 11:01 AM I just upgraded to the latest version of X11. A program that previously worked fine now reports the following error: Applications that do not use this toolkit work fine. I did not recompile the xview library. Someone please correct me if I'm wrong. As I understand it, applications compiled under cygwin 1.5 need to be recompiled for the current version, 1.7, which is what you have. I apologize for the lack of a link t a message in the archives or other documentation. Good luck. - Barry Disclaimer: Statements made herein are not made on behalf of NIAID. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: bug report/suggested temp. patch: handling bursts of sent keys
On 01/19/2010 01:17 PM, Mark Lillibridge wrote: Hi. I don't appear to have gotten any response to my message sent to this list January 12 (copied below). Do I have the right list? Am I supposed to use a different mechanism to report bugs with the Cygwin X server? Please help. Thanks for the information you've provided. This is the correct list for Cygwin X issues. I can't engage you on this topic because I'm not knowledgeable about the area you investigated. However, a couple of questions come to my mind about what you've found: 1. Is this Cygwin-specific? 2. If not, what's the upstream solution? This information might help you decide if your issue is better reported upstream. It may also help developers here decide how to solve the problem. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
Re: X11 assertion fails
On 01/19/2010 01:22 PM, Buchbinder, Barry (NIH/NIAID) [E] wrote: Carl R. Crawford sent the following at Tuesday, January 19, 2010 11:01 AM I just upgraded to the latest version of X11. A program that previously worked fine now reports the following error: Applications that do not use this toolkit work fine. I did not recompile the xview library. Someone please correct me if I'm wrong. As I understand it, applications compiled under cygwin 1.5 need to be recompiled for the current version, 1.7, which is what you have. This is not a requirement, though it is a recommendation. -- Larry Hall http://www.rfk.com RFK Partners, Inc. (508) 893-9779 - RFK Office 216 Dalton Rd. (508) 893-9889 - FAX Holliston, MA 01746 _ A: Yes. Q: Are you sure? A: Because it reverses the logical flow of conversation. Q: Why is top posting annoying in email? -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
xserver bug?
I've noticed that with XWin 1.7.3 (and perhaps earlier versions; not sure), the key combination CTRL-SHIFT-0 (zero) doesn't generate any events. CTRL-SHIFT-1 thru -9, alphabetic keys, no problem -- just not zero. This came up as I was testing the new rxvt-unicode release; it has a special ISO14755 entry mode, where you hold down CTRL-SHIFT and type the unicode value (in hex) of the codepoint you want, and then release the CTRL-SHIFT keys -- urxvt inserts the correct character. This works -- as long as the unicode value doesn't contain 0. e.g. CTRL-SHIFT 3-b-2 gives 'beta' CTRL-SHIFT 2-0-a-c should be the Euro symbol, but the '0' never has any effect. As I said, you can verify this behavior (this missing 0 events) using xev, so it's not specific to rxvt-unicode. Is this a bug, or a designed behavior, in XWin? -- Chuck -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
[ANNOUNCEMENT] Updated: python-xdg-0.18-1
The following package has been updated for the Cygwin distribution: *** python-xdg-0.18-1 PyXDG is a python library to access freedesktop.org standards. Currently supported are: * Base Directory Specification * Menu Specification * Desktop Entry Specification * Icon Theme Specification * Recent File Specification * Shared-MIME-Database Specification This is an update to the latest upstream version. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO == If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
[ANNOUNCEMENT] Updated: desktop-file-utils-0.15-3
The following package has been updated for the Cygwin distribution: *** desktop-file-utils-0.15-3 This package provides several utilities for working with FreeDesktop.org .desktop menu files. The previous release was broken due to a UAC incompatibility in an earlier libtool release; this release has been rebuilt with the current libtool and actually works now. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO == If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
[ANNOUNCEMENT] Removed: GNOME 1.4 libraries
The following packages have been REMOVED from the Cygwin distribution: *** gdk-pixbuf-0.22.0-4 *** gdk-pixbuf-devel-0.22.0-4 *** gdk-pixbuf-doc-0.22.0-4 *** gnome-libs-1.4.2-3 *** gnome-libs-devel-1.4.2-3 *** gnome-libs-doc-1.4.2-3 *** libart_lgpl-1.4.2-3 *** libgnome-1.4.2-3 *** libgnomecanvaspixbuf-0.22.0-4 *** libgnomesupport-1.4.2-3 *** libgnomeui-1.4.2-3 *** libgnorba-1.4.2-3 *** libgtkxmhtml-1.4.2-3 *** libIDL-0.5.17-2 *** libxml-1.8.17-3 *** libxml1-1.8.17-3 *** libxml-devel-1.8.17-3 *** libzvt-1.4.2-3 *** ORBit-0.5.17-2 *** ORBit-devel-0.5.17-2 The GNOME 1.4 libraries were added to the distro in 2005 for the benefit of GNOME programs that had yet to be ported to the then relatively-new GNOME 2.x. Going on five years later, GNOME 3.0 is around the corner, and development of the last known GNOME 1.4-based holdout was finally stopped last year. These packages are completely obsolete, should no longer be used, and have therefore been removed from the distro. If you previously installed these packages, they will remain installed on your system until you uninstall them, which I recommend you do ASAP. After getting the latest setup.ini from cygwin.com, they will all be shown in the Misc category. Yaakov Cygwin/X CYGWIN-XFREE-ANNOUNCE UNSUBSCRIBE INFO == If you want to unsubscribe from the cygwin-xfree-announce mailing list, please use the automated form at: http://cygwin.com/lists.html#subscribe-unsubscribe If this does not work, then look at the List-Unsubscribe: tag in the email header of this message. Send email to the address specified there. It will be in the format: cygwin-xfree-announce-unsubscribe-you=yourdomain@cygwin.com If you need more information on unsubscribing, start reading here: http://sourceware.org/lists.html#unsubscribe-simple Please read *all* of the information on unsubscribing that is available starting at this URL. -- Unsubscribe info: http://cygwin.com/ml/#unsubscribe-simple Problem reports: http://cygwin.com/problems.html Documentation: http://x.cygwin.com/docs/ FAQ: http://x.cygwin.com/docs/faq/
