Re: On xkb_* in /tmp
On 07/07/2011 01:25, Angelo Graziosi wrote: Il 07/07/2011 2.12, Angelo Graziosi ha scritto: After the last upgrade to xorg-server I find in /tmp: ... 316 Jul 7 02:06 xkb_H2DcsY ... 316 Jul 7 02:06 xkb_PTGhAv Is this to be expected? Now I have seen that /tmp is filling od xkb_* files each time I login (i.e. XWin starts)... :( Thanks for reporting this. 1.10.2-1 has a change to write the keymap to a temporary file and use system() to run xkbcomp, rather than write it to a pipe and fork() xkbcomp (to avoid fork() failures preventing the X server from starting), using code that already exists for this purpose on for xming. But it seems I had failed to add the patch that xming has to ensure that these temporary files are cleaned up correctly. I'll fix this and update the X server, but in the meantime you should be able to remove these temporary files once the server has started with no ill effects :-) -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: Cygwin X + HP-UX 11.11 + italian keyboard = AltGr not working
On 06/07/2011 15:26, Danilo Turina wrote:
On 06/07/2011 16.02, Jon TURNEY wrote:
On 06/07/2011 09:15, Danilo Turina wrote:
having recently replaced my old keyboard (that had a US layout) with an
italian one, I'm having a problem with Cygwin X when running HP-UX clients:
AltGr does not work and this prevents me to use characters like [ { }
], etc.
I'm up to date with Cygwin and Cygwin X at the moment (1.7.9(0.237/5/3)
2011-03-29 10:10 i686 Cygwin for Cygwin and 1.10.2.0 for XWin).
These are the steps to reproduce the problem:
1) start Cygwin X
2) disable access control (xhost +)
3) access via telnet/ssh a HP-UX machine
4) open an xterm from the HP-UX machine in Cygwin X
5) in the newly opened xterm try to use AltGr (AltGr + è (i.e. the
key
at the right of P), should produce {, while AltGr + Shift + è should
produce {)
I'm missing here what is actually produced. Nothing? or the unmodified è?
The unmodified è (well, sort of, because when I press è on the keyboard I
see on the terminal I (I think because of some other problem of the terminal
with non-ASCII chars) and if I press AltGr+è I yet see I, so it's just
like pressing AltGr has no effect at all).
6) fall on the floor crying in desperation
This is perfectly normal for people having to deal with XKB :-)
Notice that when using a client from a Linux machine all works properly.
A googled a lot and found a lot of information but only few of it applied
(=helped) to my specific case. I tried to mess with xmodmap and kbd config
files and also with other stuff, but nothing seemed to solve the problem.
I think a solution is contained in this old mailing list post [1], use
XKB_DISABLE=1 and adjust the keyboard map so that AltGr is Mode_switch and
the
keys have the expected mapping in group 2, activated via Mode_switch.
Note that just reassigning AltGr to Mode_switch is not enough, you'll need to
remap appropriately the keys which generate different characters with AltGr
e.g. something like:
xmodmap -e clear mod5
xmodmap -e clear mod3
xmodmap -e keycode 113 = Mode_switch Multi_key
xmodmap -e add mod3 = Mode_switch
xmodmap -e keycode 34 = egrave eacute bracketleft braceleft
(and so on for the other keys which need to generate different characters
with
AltGr)
I already encountered some like that while searching the internet but didn't
work.
I tried what you wrote here but didn't work either...
Just to be clear, you probably have to do all this before you start the xterm
you are going to be working in.
Can I see the xev output when you try that setup?
Is there anything that I can do to go deeper into the analysis of this
problem? xev seems not of any help, since it returns the same results both for
Xming where all works and Cygwin X where I have the problem.
Yes, that's rather mystifying.
You might consider using wireshark, xmon or xscope to examine the protocol
interactions between client and server (not sure if all of these can decode
XKB extension protocol) to see if there is any difference there.
It seems that XKB_DISABLE is checked for inside libX11 (at least since R6.6,
the oldest version in freedesktop.org git), so you might want to identify what
version is on your HP-UX host and try to understand how it behaves. It might
also be worthwhile to look forward in the version history to see if there's
been a fix made for this behavior?
Lastly, I notice that HP-UX 11.11 is apparently still in support, so you might
actually ask HP to fix it :-)
--
Jon TURNEY
Volunteer Cygwin/X X Server maintainer
--
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: On xkb_* in /tmp
Il 07/07/2011 14.51, Jon TURNEY ha scritto: I'll fix this and update the X server, but in the meantime you should be able to remove these temporary files once the server has started with no ill effects :-) Thanks a lot! Ciao, Angelo. -- 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/
X on win 7
Hello, I have a new Dell Dimension M6600 with Windows 7 SP 1. I have disabled the Windows firewall and added rules to allow programs in cygwin and cygwin\bin to run. I am using cygwin 1.7.9 (I also use older cygwins on many 32-bit Windows machines). On this machine, X runs badly: often very slowly, and frequently with crashes as well. A couple of times I was forced to reboot the machine -- Windows appeared unresponsive. I did try rebaseall, but did not help (in fact had to reinstall cygwin). I have seen some posts on this topic, but no definitive workaround. Any help welcome. Daniel Bienstock -- 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: X on win 7
On 7/7/2011 10:24 AM, Daniel Bienstock wrote: Hello, I have a new Dell Dimension M6600 with Windows 7 SP 1. I have disabled the Windows firewall and added rules to allow programs in cygwin and cygwin\bin to run. I am using cygwin 1.7.9 (I also use older cygwins on many 32-bit Windows machines). On this machine, X runs badly: often very slowly, and frequently with crashes as well. A couple of times I was forced to reboot the machine -- Windows appeared unresponsive. I did try rebaseall, but did not help (in fact had to reinstall cygwin). I have seen some posts on this topic, but no definitive workaround. Sounds like a case of BLODA to me. http://cygwin.com/faq/faq.using.html#faq.using.bloda -- Larry _ 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/
[ANNOUNCEMENT] Updated: xorg-server-1.10.2-2
The following packages have been updated in the Cygwin distribution: *** xorg-server-1.10.2-2 *** xorg-server-dmx-1.10.2-2 These packages contain XWin and the other X.Org X11 servers. The following cygwin-specific changes have been made since 1.10.2-1: * Ensure the temporary file used when invoking xkbcomp is always removed * Handle the virtual key code generated by the Fn key on IBM Lenovo laptops so it doesn't also function as delete 536fffbf6141813f0f285db094c88493 *xorg-server-1.10.2-2.tar.bz2 b19b337d052cde107a2ec1bdd35e710e *xorg-server-dmx-1.10.2-2.tar.bz2 01c6c04d58fa005ecb5702db1c2dfe58 *xorg-server-1.10.2-2-src.tar.bz2 -- Jon TURNEY Volunteer Cygwin/X X Server maintainer -- 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: Re: X on win 7
On 7/7/2011 10:24 AM, Daniel Bienstock wrote: | Sounds like a case of BLODA to me. | | http://cygwin.com/faq/faq.using.html#faq.using.bloda I looked at the BLODA list, and I don't believe I have any of *those* programs running on my machine. Is there a way I can identify the culprit? Thanks in advance. Dan -- 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: Re: X on win 7
On Thu, 2011-07-07 at 21:13 -0400, Daniel Bienstock wrote: On 7/7/2011 10:24 AM, Daniel Bienstock wrote: | Sounds like a case of BLODA to me. | | http://cygwin.com/faq/faq.using.html#faq.using.bloda I looked at the BLODA list, and I don't believe I have any of *those* programs running on my machine. Is there a way I can identify the culprit? Thanks in advance. Windows Defender, a default component of Win7, is BLODA, so I'd start by permanently disabling the WinDefend service. (We should probably note that in BLODA itself.) 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/
RE: Re: X on win 7
Turned off WinDefend, but problem continues. The Windows Task Manager shows a huge list of services running, like Application Experience, which could be interfering. But I have no idea which are safe to turn off. I can send in a jpeg with that list, if that was helpful (and if the site accepts jpge attachments) -- 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/
