Skip to content

Error in postscript(....)

6 messages · Marcus Eger, Peter Dalgaard

Marcus Eger
# 
Dear R'ers,

I wonder about the reason for the following error message:

Error in postscript(file = paste(getpath(file), getfname(file),
as.character(num),  : 
	X11 fatal IO error: please save work and shut down R

The R process locks completely, it is not possible to save anything.
Thanks for any help
   M. Eger


P.S.:
_                
platform i686-pc-linux-gnu
arch     i686             
os       linux-gnu        
system   i686, linux-gnu  
status                    
major    1                
minor    2.1              
year     2001             
month    01               
day      15               
language R
Peter Dalgaard
# 
Marcus Eger <marcus.eger at physik.uni-marburg.de> writes:
Argh. I think I saw a version of this on a laptop I borrowed in early
December and forgot about it when I couldn't reproduce the effect on
my other systems. I had it debugged far enough to see that it was
sending the main R loop into a spin where it was seemingly receiving
an X event but never handling it.

What did you do to deserve having your machine do this to you? Shutting
down an X11 window with "destroy" triggered the effect in my case. It
might be window manager dependent snce I've only ever seen it under
FVWM2.
Marcus Eger
#
Peter Dalgaard BSA wrote:
Yes, I 've got FVWM2 installed, but - as far as I know - I did not
destroy
any window or caused a similar event - though I am not totally sure.
The R process ran inside xemacs (21.2) with ESS on another debian 
machine (2.2) via secure shell.

+-------------------------------------------------------
| Marcus Eger
+-------- ><> -------------------------------------------
| E-Mail: eger.m at gmx.de (NEW)
|         marcus.eger at physik.uni-marburg.de (OLD)
| WWW:    http://neuro.physik.uni-marburg.de/~eger (NEW)
+--------------------------------------------------------
-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-.-
r-help mailing list -- Read http://www.ci.tuwien.ac.at/~hornik/R/R-FAQ.html
Send "info", "help", or "[un]subscribe"
(in the "body", not the subject !)  To: r-help-request at stat.math.ethz.ch
_._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._._
2 days later
Marcus Eger
# 
Is there a way to circumvent the problem or to solve it? I'd be very
glad to find a solution...
   M. Eger

  
    

      
      
    

  


  


      

    

    

      
      

        


  

        

      Peter Dalgaard
    

    

      
      #
    

  


  

      
Marcus Eger <marcus.eger at physik.uni-marburg.de> writes:

            

      
      
      
    

        
I'm still at a loss trying to explain how postscript() triggers an X11
error, but...

You might try to change (in devX11.c)

static int R_X11IOErr(Display *dsp)
{
    error("X11 fatal IO error: please save work and shut down R");
    return 0; /* but should never get here */
}

by inserting code that unregisters the X11 input handler, i.e.

int fd = ConnectionNumber(display);
        removeInputHandler(&R_InputHandlers,
                           getInputHandler(R_InputHandlers,fd));

and similarly in dataentry.c.

(BTW, I forget, did you try running under the debugger and see whether
it is the code in devX11.c or in dataentry.c that tickles this?)

  
    

      
      
    

  


  


      

    

    
4 days later

    

      
      

        


  

        

      Marcus Eger
    

    

      
      #
    

  


  

      
Thanks very much for your help. However,
I've followed Prof. Ripley's advice and changed my window manager.
I wished I had the time to debug the code and to dig into c ... 
   M. Eger

        
Peter Dalgaard BSA wrote: