Re: xstart fails

2005-06-01 Thread Alexander Gottwald
On Tue, 31 May 2005, Catherine Beauheim wrote:

 
 Must be my day for frustrations.  I have reloaded, rebooted, loaded, 
 rebooted,cleaned out, reloaded, rebooted and still can't get the xwin to 
 start.  the message says to email this  address with the version
 6.8.2.0-2 with xwin command line as

 Fatal server error:
 could not open default font 'fixed'
 winDeinitMultiWindowWM - Noting shutdown in progress

make sure the xorg-x11-fnts package is installed and run font-update.
Does this print any errors?

bye
ago
-- 
 [EMAIL PROTECTED] 
 http://www.gotti.org   ICQ: 126018723


Re: Ctrl got stuck

2005-06-01 Thread Tobias Polzin
Hi Alexander, 

 It seems to appear more often under high load. But unfortunatly there is
not much we can do about it. 

Hm, usually my machine is not under high load, but it could be short load
peak, like directly after switch from one desktop to another...

 Windows reports alt-gr as simultanious presses of ctrl and alt and we have
to 
 detect whether it is alt-gr or the keys are really pressed together. Under
heavy
 load the timeouts (and timestamps) of the events may differ between press
and 
release events. That way you get a control press and an alt-gr release so
control
 gets stuck.

 the only solution is making the detection more robust.

I don´t know the implementation, but couldn´t it be a possibly approach to
improve the handling of mismatching release/press events? E.g. that a
Alt-Gr release releases Ctrl, too. It seems to me, that there is
something else wrong, as there seem to be three states:

State green: Everything works fine

State red: Ctrl got stuck (possibly by pressing Alt-Gr under heavy load and
releasing without heavy load, or the other way round)

State yellow: Everything except Alt-Gr works fine (Can be reached from
State red with pressing/releasing Ctrl, Pressing Alt-Gr switches to State
red)

Perhaps xfree get´s confused by a AltGr release without a press?

By the way: I wrote Show Cursor returns to State green. Already opening
the menu of the tray-icon returns to State green. Opening/Closing a new
window seems to be the point.

Regards, Tobias

-- 
Geschenkt: 3 Monate GMX ProMail gratis + 3 Ausgaben stern gratis
++ Jetzt anmelden  testen ++ http://www.gmx.net/de/go/promail ++


Xfig oddness as EPS is imported

2005-06-01 Thread Franz Haeuslschmid
Dear readers,

I'm running Xfig on top of up-to-date Cygwin installation.
Everything works as expected, however importing an EPS file as
picture object fails:


Could not parse EPS file with ghostscript: ±l^T^P'^C
ERROR from ghostscript:
AFPL Ghostscript 8.50:  Could not open the file 
D:\cygwin\tmp\xfig-pic001496.pix .
Error: /invalidfileaccess in --.outputpage--
Operand stack:
   3   --nostringval--   1   true
Execution stack:
   %interp_exit   .runexec2   --nostringval--   --nostringval--   
--nostringval--   2   %stopped_push   --nostringval--   --nostringval--   
--nostringval--   false   1   %stopped_push   1   3   %oparray_pop   1   3   
%oparray_pop   1   3   %oparray_pop   1   3   %oparray_pop   .runexec2   
--nostri
gval--   --nostringval--   --nostringval--   2   %stopped_push   
--nostringval--   2   3   %oparray_pop   --nostringval--   --nostringval--
Dictionary stack:
   --dict:1124/1686(ro)(G)--   --dict:0/20(G)--   --dict:74/200(L)--
Current allocation mode is local
Last OS error: Permission denied
AFPL Ghostscript 8.50: Unrecoverable error, exit code 1


Note that I am indeed using the `gs' script as suggested in
URL:http://article.gmane.org/gmane.os.cygwin/40831.  (For
aficionados of Usenet/Gmane:
news:[EMAIL PROTECTED].)

There is a file `xfig-pic001496.pix' in Cygwin's tmp folder,
however it has now owner.  That is, when I explore the file
properties (using the Explorer on my Windows XP Professional box)
there is _no_ tab for the security configuration for that special
file.  I then investigated the access permissions for
`D:\cygwin\tmp' -- I discovered a new user/group: NULL SID.  The
file magically disappears, when Xfig is closed.

I experienced this behavior previously, when I still used
Cygwin's version of ghostscript.  Therefore I assume that Xfig is
responsible for creating such files.


Any idea is appreciated,
Franz.



Re: Emacs problem with Cygwin 1.5.17-1 (CGF, a little comment)

2005-06-01 Thread Angelo Graziosi

http://cygwin.com/ml/cygwin-xfree/2005-05/msg00274.html

best regards
angelo.