Re: can't open display

From: Dennis Gilmore (dennis_at_ausil.us)
Date: 11/10/04

  • Next message: Nathan Oosthuizen: "Re: FC2 - Can't boot to FC after XP re-instal"
    To: For users of Fedora Core releases <fedora-list@redhat.com>
    Date: Tue, 9 Nov 2004 23:09:16 -0600
    
    
    
    

    Once upon a time Tuesday 09 November 2004 11:16 pm, phurd wrote:
    > Hey All,
    >
    > Up until unpgrading to FC3 I would ssh from machinea on machineb and then
    > run programs on machineb remotely from machinea. I get confused by X
    > client/server language. Since upgrading machinea from FC2 to FC3 I get
    > errors
    >
    > like:
    > : Gtk-WARNING **: cannot open display:
    >
    > Xt error: Can't open display:
    Reading the release notes would help the way ssh works has changed. try ssh
    -X machineb and it will work

    Dennis

    
    

    
    

    -- 
    fedora-list mailing list
    fedora-list@redhat.com
    To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
    


  • Next message: Nathan Oosthuizen: "Re: FC2 - Can't boot to FC after XP re-instal"

    Relevant Pages

    • Re: cant open display
      ... Dennis Gilmore wrote: ... >>Up until unpgrading to FC3 I would ssh from machinea on machineb and then ... >>run programs on machineb remotely from machinea. ... > Reading the release notes would help the way ssh works has changed. ...
      (Fedora)
    • Re: [Full-disclosure] Possible DOS issue in OpenSSH ssh client
      ... This consumes 50-100% of available CPU time on MachineB (depending on the ... bandwith between them). ... What did the ssh client do? ...
      (Full-Disclosure)
    • Re: consecutive rsync between three machines
      ... why do you suggest the option ssh -c and what is the ... (accessable through machineB). ... why not use the ssh option -c, instead of trying to do the echo pipe. ...
      (comp.os.linux.misc)
    • Re: consecutive rsync between three machines
      ... Because I misremembered the command. ... ssh B mkdir /tmp/rsync ... (accessable through machineB). ... why not use the ssh option -c, instead of trying to do the echo pipe. ...
      (comp.os.linux.misc)
    • [Full-disclosure] Possible DOS issue in OpenSSH ssh client
      ... During some testing I found a possible bug/issue with OpenSSH ssh client. ... This consumes 50-100% of available CPU time on MachineB (depending on the ...
      (Full-Disclosure)