[ANNOUNCEMENT] New: libgsf-1.14.16-1
The following packages have been added to the Cygwin distribution: * libgsf-1.14.16-1 * libgsf1-devel-1.14.16-1 * libgsf1_114-1.14.16-1 * python-gsf-1.14.16-1 libgsf is a GNOME library which provides I/O abstraction for a variety of structured file formats, such as compressed archives and office document formats. 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] New: librsvg2-2.26.0-2
The following packages have been added to the Cygwin distribution: * gdk-pixbuf2.0-svg-2.26.0-2 * gtk2.0-engines-svg-2.26.0-2 * librsvg2-devel-2.26.0-2 * librsvg2_2-2.26.0-2 * rsvg-2.26.0-2 libRSVG is a very fast SVG rendering engine written in C. It currently support most of the SVG 1.2 specification, except the animation part. libRSVG is used in many projects for SVG rendering, most notably GNOME. 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/
Re: Questions regarding windows 7 installation
thanks Jason, I have already done that, but even after commenting out the exec xterm and running the xterm process from the drop down menu I get two X windows. One that starts and stays blank and then the actual Xterm window which has a white background. I don't mind running the Xterm automatically, it's the spurious cygwin windows that start and stay up. Just clutters up the desktop and you can't tell which is the usable Xterm. DePriest, Jason R. wrote: On Mon, Jan 11, 2010 at 6:32 PM, Jerry Lowry wrote: I have installed Cygwin 1.7 twice on my windows 7 laptop. Each time it installs fine but when I try to run the X server it leaves three different X windows open as well as an Xterm itself. Is this the default behavior on 1.7? I really would like to get just the X icon in the task bar and nothing else until I start an Xterm. But even the Xterm opens two windows. Anyone have any ideas as to the problem I am seeing? -- Try modifying your /etc/X11/xinit/xinitrc file I commented out the last line which had an 'exec xterm' in it and the xterm no longer runs automatically. -Jason -- 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/ -- 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/
bug report/suggested temp. patch: handling bursts of sent keys
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: XWin Server Not Starting
I too had the same problem and I looked through some of the other posts. Simon Jean-Francois posted the solution and Andy Koppe posted a followup. Just as Andy has suggested, I got a in-use message box because I had a bash shell running. http://www.cygwin.com/ml/cygwin-xfree/2009-12/msg00098.html http://www.cygwin.com/ml/cygwin-xfree/2009-12/msg00099.html -- 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/
try to startx
Dear cygwin x programer: I try the suggestion of mailing list to fix startx problem, - /bin/sh disappeared: this was fixed with ln -s /bin/bash /bin/sh Another problem related to fonts was fixed by mkfontdir --- but it still not work, and I try to reinstall bash at base category then retry above my startx still not work please help, Eric -- 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: XWin Server Not Starting
Well I figured that I would start over. So, I downloaded the cygwin files again to a local disk. Installed everything from the local disk. I found that this time the install did not put any programs in the Cyginw-X folder at all. So I deleted the cygwin download and picked a different mirror site. I found that the number of folders got bigger and this time when I installed, the Cygwin-X folder is populated. ( The first site I used was OSU, anyway to ping them to have them upgrade the mirror with all of the folders?) After the install I started the X server. Worked okay, except that when the xterm started it still leaves a blank X windows hanging around. Have yet to investigate this, just finished the install. I then started the cygwin dos window and it returned this error: 1 [main] bash 3660 C:\Xwin\bin\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x85, top 0x8B, reserve_size 389120, allocsize 393216, page_const 4096 2 [main] bash 2848 child_info::sync: wait failed, pid 3660, Win32 error 1812 1861 [main] bash 2848 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 2 [main] bash 2584 C:\Xwin\bin\bash.exe: *** fatal error - couldn't allocate heap, Win32 error 487, base 0x85, top 0x8B, reserve_size 389120, allocsize 393216, page_const 4096 301671318 [main] bash 2848 child_info::sync: wait failed, pid 2584, Win32 error 1812 301672949 [main] bash 2848 fork: child -1 - died waiting for longjmp before initialization, retry 0, exit code 0x100, errno 11 I killed the windows after these errors. I was hoping to check see if 'sh' was installed, but will look at the xterm instead. Started the Xterm and got the following error: /usr/bin/xterm: Could not exec /bin/bash: Bad address looks like bash needs to be reinstalled or fixed. Will do the reinstall and report back. thanks Bob Whitehurst wrote: I too had the same problem and I looked through some of the other posts. Simon Jean-Francois posted the solution and Andy Koppe posted a followup. Just as Andy has suggested, I got a in-use message box because I had a bash shell running. http://www.cygwin.com/ml/cygwin-xfree/2009-12/msg00098.html http://www.cygwin.com/ml/cygwin-xfree/2009-12/msg00099.html -- 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/ -- 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: try to startx
On 12/01/2010 15:53, eric lin wrote: Dear cygwin x programer: I try the suggestion of mailing list to fix startx problem, For the *third* time, when you provide us with ALL of the information EXACTLY as detailed here, then we may be able to help you: Problem reports: http://cygwin.com/problems.html Until then, please stop wasting both your time and ours. Yaakov Cygwin/X -- 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/
BitDefender prevents installation and execution of Cygwin and Cygwin-x
After upgrading to WinXP last month (I don't like to rush in to things) cygwin, cygwin-x, and NX-Client ceased to function. (To make a long story short, I had changed to BitDefender at the same time, but had forgotten that). I blamed the problem on the OS upgrade, not realizing that the problem was with the AV software. I tried everything I could think of, to the point where I deleted all files associated with both cygwin and NX, then searched the registry and deleted all references to Cygnus, cygwin and nx-client, all to no avail. I then re-installed only cygwin (the default minimum) but got the same symptoms: Error messages in the /etc/postinstall script processes which translated to 0xC00D (access violation) occurred on each an every entry in the script. I finally found a web entry that suggested that this error could be caused by AV software (although it did not mention BitDefender by name). In desperation, I erased all cygwin files yet again, put BD in GAME mode, and re-installed the default cygwin. The install was successful so I added cygwin-x which also installed and ran successfully. I thought I'd push my luck so I also installed NX-client. It worked as well! Since I didn't like to leave my systems in Game (very permissive) mode, I switched BD back to its normal operating mode. All the cygwin stuff stopped working. Back to Game mode. Everything works. Sent nasty-gram to BitDefender (not really nasty, but let them know of the problem and asked for solution). I had the same problem on machines running Vista and Win7 (which also recovered in BD Game mode) so I think the problem is wide-spread. I'm posting this in the hope that it helps others who may be beating their heads against the wall. Don Ziesig -- 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: Can't start xterm from Cygwin/X icon in system tray
After re-installing Cygwin from scratch, I have determined that this environment variable is/was causing the problem: CYGWIN=tty Once I removed it, I was able to create an X term from the icon in the system tray. - Jim On Wed, Dec 30, 2009 at 10:07 AM, I wrote: I have a very strange situation. At work, I am running Win XP SP3. I installed all the latest Cygwin (1.7.1) + Xorg updates, including startxwin.exe. Everything works perfectly. At home, I am running Windows 7 Professional, 64-bit. I am unable to start an xterm from the Cygwin/X icon in the system tray (right-click, select xterm). Both setups have the same line in .XWinrc: xterm EXEC xterm I am starting the X server the same way: D:\Cygwin\bin\run.exe /usr/bin/bash.exe -l -c /usr/bin/startxwin.exe I do not have a ~/.startxwinrc file. The xterm that is supposed to be created when the server starts doesn't start either. The symptom is that xterm.exe is shown running in the task manager, but there is no Xterm window on the desktop. As a work-around, I created a shortcut on my desktop to start an xterm: D:\Cygwin\bin\run.exe /usr/bin/xterm -display localhost:0 That works perfectly, but is not an optimum solution (I try to have as few desktop icons as possible). There is nothing in the /var/log/Xwin log that indicates why an xterm would start but not open a window. Any ideas? -- Jim Reisert AD1C, jjreis...@alum.mit.edu, http://www.ad1c.us -- 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/
