Results 1 to 3 of 3

Thread: Since installing the latest Ubuntu 10.04 kernel I can only boot through failsafeX

  1. #1
    Join Date
    Dec 2007
    Location
    Sitting on my bed
    Beans
    273
    Distro
    Ubuntu 10.04 Lucid Lynx

    Since installing the latest Ubuntu 10.04 kernel I can only boot through failsafeX

    Since installing the latest Ubuntu 10.04 kernel I can only boot through failsafeX

    The log says:

    Fatal server error: Sever already active for display 0

    Then it advises me to remove tmp/.x0-lock which I did

    also says

    (WW) xf86 CloseConsole KDSETMODE failed: Bad file descriptor
    (WW) xf86 CloseConsole VT_GETMODE failed: Bad file descriptor
    (WW) xf86 CloseConsole VT_GETSTATE failed: Bad file descriptor

    Any ideas would be appreciated

  2. #2
    Join Date
    Jun 2010
    Location
    London, England
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Since installing the latest Ubuntu 10.04 kernel I can only boot through failsafeX

    This is an installation of Ubuntu Server, is it not? Please confirm. Ubuntu 10.04 desktop edition reached end of life May 2013.

    Regards.
    It is a machine. It is more stupid than we are. It will not stop us from doing stupid things.
    Ubuntu user #33,200. Linux user #530,530


  3. #3
    Join Date
    Mar 2010
    Location
    USA
    Beans
    Hidden!
    Distro
    Ubuntu Development Release

    Re: Since installing the latest Ubuntu 10.04 kernel I can only boot through failsafeX

    Not really. The whole error the OP is describing is usually like this:
    Code:
    Fatal server error:
    Server is already active for display 0
        If this server is no longer running, remove /tmp/.X0-lock
        and start again.
    Where the error is from XServer, where X session 0 has a temp file open and the file is locked, therefore it thinks that graphics session either active (running), being used by another user, other than current... or that file may be left held in a locked state by an error. This error also occurs when a user tries to start X as root, or change an X related setting as root (another user), when that X session is still active. Therefore being denied, because. of permissions.

    If they installed something and it gets this error, then whatever they were trying to do, previous to this error, tried to do something with X, and was deinied. So this error can come up if a UserID from a program, doesn't have permissions... so:
    Code:
    OffendingID=(<To be determined>)
    [ -z "$DISPLAY" ] && startx && {sleep 5; DISPLAY=0:0 setsid $OffendingID; }
    Where "OffendingID" would have to be researched and found in the sys log... At logiin (the graphical login) that OffendingID might be the supplied UserName... So the OP, in this instance should replace that first command with this (substituting "userName" with his own UserID:
    Code:
    [ -z "$DISPLAY" ] && startx && {sleep 5; DISPLAY=0:0 setsid userName }
    When a OP tells me they installed something, and then when they boot, they got an X permissions denial message... When they install something, it is using root permission for that... Sometimes the /home/userName/.Xauthority file get corrupted or most usually, the permissions of that get changed to root instead of the user. Diagnose with
    Code:
    ls -l /home/userName/.Xauthority
    and insure it says userName (your own) root... and not root root... If it says "... root root", I'll explain another way to correct that...

    Question to the OP is, why 10.04 LTS, which is now not supported and past it's End Of Life (EOL)? Why not something supported?
    Last edited by MAFoElffen; January 4th, 2015 at 06:26 PM.

    Concurrent coexistance of Windows, Linux and UNIX...
    Ubuntu user # 33563, Linux user # 533637
    Sticky: [all variants] Graphics Resolution- Upgrade /Blank Screen after reboot
    UbuntuForums system-info Script

Tags for this Thread

Bookmarks

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •