Dealing with the Light Blue Screen Of Doom

Hi! With my third consecutive post of the day, I’d like to speak about the login error usually seen on Gnome desktops, aka : ‘Light Blue Screen of Doom’. As far as I know, this bug is associated with Gnome and is usually because of faulty installation of gnome files and it was something that tormented me endlessly last week when I tried to install Debian 8 (Jessie)

Unfortunately, I never really fixed it myself. What started off as a problem with gnome quickly snowballed into something else that wiped my routing table, making sure I couldn’t even update the corrupted files properly. Although I came across a lot of bug reports in my quest to solve it, I never really found a solution.

Reinstallation seems to be only option left here, but there are a few checks you can make

  1. Call the terminal. Use Ctrl+Alt+F2, you should be able to get your command line.
  2. Login as root. This is extreme troubleshooting. You need ‘root’
  3. Check and see if ‘startx’ works. (Yay! problem solved if it does!)
  4. Try to see if the basic gnome packages are installed type ‘apt-get install’ with basic gnome packages like gnome-desktop-environment, gdm, gnome, etc.. to see if they are installed. If not, try to install them and then run the ‘startx’ command.
  5. If you can’t install them, or if they are already installed, try running the updating the system

    apt-get update
    apt-get upgrade
    apt-get dist-upgrade //If OS is at newest version
  6. If updating doesn’t work and gives ‘Failed to Fetch’ errors for all the source links, try pinging the network to make sure you have a connection.

  7. If you do have a connection, verify the sources :

    nano /etc/apt/sources.list
    deb jessie main contrib non-free
    #deb-src jessie main contrib non-free
    deb jessie/updates main contrib non-free
    #deb-src jessie/updates main contrib non-free
    deb testing main contrib non-free
    #deb-src testing main contrib non-free
    deb testing/updates main contrib non-free
    #deb-src testing/updates main contrib non-free
  8. If you have no connection, check your routing table with the command ‘netstat -nr’. If this routing table is completely empty, then… I’ve got some bad news for you. Reinstallation is your new friend. Try and see if you can copy your files using command line. ‘cp’ and ‘ls’ are basically your new best friends.

Here’s a guide to help change your OS. Hopefully, everything works out and you’re back to working in no time!

Related Posts

Comment ( 1 )
  1. anonima_commentatori
    June 6, 2016 at 2:36 pm

    As said in the other post, you’re mixing the stable and the testing repositories. Doing so your system surely breaks! if you want to stay with debian stable then use the debian stable repositories and nothing else. If you want only some packages from testing you should know how to manage this situation and enable the testing repositories when needed. But, again, this is a bad practice. Consider to use the debian backports repositories instead:

Leave a reply