public inbox for cygwin-xfree@sourceware.org
help / color / mirror / Atom feed
From: Jon TURNEY <jon.turney@dronecode.org.uk>
To: cygwin-xfree@cygwin.com
Cc: angelo.graziosi@alice.it
Subject: Re: On xkb_* in /tmp
Date: Thu, 07 Jul 2011 13:04:00 -0000 [thread overview]
Message-ID: <4E15ABBA.7090008@dronecode.org.uk> (raw)
In-Reply-To: <4E14FD0F.6000200@alice.it>
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/
next prev parent reply other threads:[~2011-07-07 12:51 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-07 0:26 Angelo Graziosi
2011-07-07 12:51 ` Angelo Graziosi
2011-07-07 13:04 ` Jon TURNEY [this message]
2011-07-07 14:24 ` Angelo Graziosi
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=4E15ABBA.7090008@dronecode.org.uk \
--to=jon.turney@dronecode.org.uk \
--cc=angelo.graziosi@alice.it \
--cc=cygwin-xfree@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).