X11 apps failing after upgrade

Jon TURNEY jon.turney@dronecode.org.uk
Tue Dec 2 21:34:00 GMT 2008


James Ferguson wrote:
> My client machine is Solaris.  Everything worked fine before the update.
> I'm running the installed startxwin.bat startup (with xterm REM'd out).
> 
> I can display xclock fine.  xterm appears up, but as soon as I hit a key
> it crashes with:
> 
>   $ xterm
> xterm:  warning, error event received:
> X Error of failed request:  BadAlloc (insufficient resources for
> operation)
>   Major opcode of failed request:  136 (XKEYBOARD)
>   Minor opcode of failed request:  16 (XkbSetNamedIndicator)
>   Serial number of failed request:  117
>   Current serial number in output stream:  130

This appears to be an issue with connecting to the Cygwin/X server from X 
clients from older X versions running on Solaris

See the thread at [1]

This thread references [2] (and it can also be found at [3]), which would 
suggest this is not a cygwin specific issue, but seems to be something that 
has changed in the X.Org 1.5.x server.

Those bugs reference some Solaris patches, which, as far as I can tell, 
upgrade X to a later version.  Applying those is the only solution I know of 
at this time.

I did some searching, but I can't find a X server patch for this issue.  If 
you find a patch that someone else has written, please let me know!

This is on my list of issues to investigate, but it is not straightforward for 
me to duplicate as I don't have a Solaris server to hand.

[1] http://cygwin.com/ml/cygwin-xfree/2008-11/msg00141.html
[2] https://bugs.launchpad.net/ubuntu/+source/xorg/+bug/292973
[3] https://bugzilla.redhat.com/show_bug.cgi?id=458373

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



More information about the Cygwin-xfree mailing list