Re: Xorg and VNC Errors

From: Joseph Green (jgreen_at_8x8.com)
Date: 07/14/05

  • Next message: Gene Heskett: "Re: WARNING:DO NOT UPGRADE TO CORE 4" 
    Date: Thu, 14 Jul 2005 11:55:28 -0700
To: For users of Fedora Core releases <fedora-list@redhat.com>

    Joseph Green wrote:

    > My boss ran up2date on one of his FC3 systems (4x 2.66 GHz Xeon, 4GB
    > memory) which had been running fine until he did that. He didn't know
    > about yum, and I'm not exactly sure what was updated, but now when it
    > boots, the text scrolls out like normal, but when it gets to the
    > graphical part of the boot proccess, the screen goes black. There is
    > no login prompt displayed and it doesn't come back at all, it just
    > remains black (the monitor is not in power save mode either). When the
    > system seems to be up and running, I can still SSH into it, access the
    > website it is hosting, and use almost all of the terminal tools.
    > However, and I'm assuming that this has to do with the X issue, I can
    > not VNC into the box to get a remote desktop. This is the error I'm
    > getting from VNC:

    Some information that I had left out: for some reason I can't even
    switch to any of the consoles (ctrl+F2 or ctrl+alt+F2) on the machine
    either. 

    -- 
fedora-list mailing list
fedora-list@redhat.com
To unsubscribe: http://www.redhat.com/mailman/listinfo/fedora-list
  • Next message: Gene Heskett: "Re: WARNING:DO NOT UPGRADE TO CORE 4"

    Relevant Pages

    • Re: Xorg and VNC Errors
      ... >> memory) which had been running fine until he did that. ... >> about yum, and I'm not exactly sure what was updated, but now when it ... >> graphical part of the boot proccess, ... Since you can still ssh into it, ...
      (Fedora)
    • Re: VNC conection problem after upgrade FC5 [Temporally secure SOLUTION]
      ... yum -y remove vnc vnc-server ... I updated the remote server and the remote cliente (using yum) ... SConnection: ... Load "vnc" ...
      (Fedora)
    • Re: Mirror Driver Architecture
      ... we can't use them unless we publish our own source code (this is a commercial ... You only have to publish the parts that are derived from VNC. ... sharing memory with user mode would require pre-allocation of a memory ... synchronization, notification etc., whereas doing everything in kernel mode ...
      (microsoft.public.win32.programmer.kernel)
    • Re: what could "use up" X forwarding connections?
      ... If the socket is still there, ... due to lack of a resource, it might be memory. ... and perhaps vnc is no exception. ... only ssh -X forwarding that stops working. ...
      (Fedora)
    • Re: remote X vs VNC
      ... > drawback is that the VNC X Server actually runs on the Linux side and ... > takes up memory there. ...
      (comp.os.linux.embedded)