Blank screen After Login from Gdm

[bbauto]

Binary package hint: gdm

I have previously installed Ubuntu 8.04beta On a Kingston Traveller 8GB stick, with success. After upgrade the screen go blank after Login from GDM. Then i tried to make a fresh installation with Ubuntu 8.04 RC and 8.04 (from yesterday) with the same result...
My temporary workaround:
"Alt-Ctrl-F2" , "Login" by Textmode. "sudo rm /tmp/.X0-lock" , "startx" then it starts up OK, after that i "Enabled Automatic Login", under "System-->Administration-->Login Window".
My comuptor: Dell Latitude D520
(Also tried xserver-xgl).

[Corny (the-real-cornholio)]

Same problem here with Ubuntu 8.04 on a 8GB Patriot USB Stick. Beta and a fresh RC installation worked fine. After some updates of the RC installation i had the same problem. Ubuntu 8.04 Final doesn't work even if installed completely new. I have also tried to install the nvidia graphics driver.

- problem exists since a patch between RC an Final.

My machine is a AthlonX2 on nvidia 630a chipset and 7050 onboard graphics.

[Corny (the-real-cornholio)]

Tried to install on HDD now. Works without problems since now...
But i need it installed on my USB-Stick

[bbauto (berglund-bengt)]

Corny! Perhaps you can try my workaround until the bug is fixed? Since you got a USB-Stick like me, I imagine you don't need multiple Logins??
Everything else seems to work OK.

[blastus (jphone1620)]

Same issue here. bbauto I tried your workaround and it worked, however I cannot get to the Login Window to enable automatic logins. What happens is that there is a busy cursor and in the task bar it tries to load the Login Window. Then after some 30 seconds or so it disappears from the task bar and nothing happens. What's weird is that a few minutes later when I had tried to open Update Manager, I actually saw the Login Window appear very briefly but then my GNOME session was instantly aborted and I got dumped to a login screen (it was like I selected Quit then Logout.)

[bbauto (berglund-bengt)]

Blastus! Try Start in failsafe mode from Grub, and drop to textmode, do as above but before "startx" type "sudo dpkg-reconfigure xserver-xorg" you can also try install "sudo apt-get install xserver-xgl" but not sure on that.

[drrck (dmuilenburg)]

Same for me, I used the instructions above to switch sessions and was able to login. Then I changed my default theme to a different one. Thanks for the tips, hopefully this one gets figured out. I'm using an 8GB Kingston Data Traveler as well.

[Johan Christiansen (johandc)]

I can confirm this problem with a clean install of hardy on an 8Gb CompactFlash.
It seems to be a problem related to the storage medium!

[Feistybird (bryanjen-tw)]

Same for me, but it only happens when installing Ubuntu 8.04 on a USB stick.

bbauto's temporary workaround really helps

I'm reading the thread of Chinese Ubuntu Forums, and there are bunches of similar problems.

Some people suggested similar workaround as what bbauto's suggested, and it seems to work.

[bbauto (berglund-bengt)]

*** This bug is a duplicate of bug 218434 ***
    https://bugs.launchpad.net/bugs/218434

There is a proposed bugfix to 2.22.1-1ubuntu1, but don't know when it will be official.
follow the link above.

[MikeF (fleimike)]

I have a similar problem with an HP DL100 using an Adaptec raid card. CD boots fine, install goes well, log in and bang no screen just the blank solid color. My mouse works fine, just nothing on the screen. The same restart xwindows sequence works for me also. Thanks so much for posting it.

[billbear (ninth-9)]

This only happens on a usb stick.

My solution:
Boot into XP from my internal disk. Open VMware and create a virtual machine using the whole usb stick as its hard disk. The usb stick boots successfully in VMware because it is recognized as a HD rather than a usb stick in the virtual environment. Then update ubuntu. The bug's fixed by updating and the usb stick can boot a real machine now.

[talowery (talowery-us)]

This problem also happens on Ubuntu 7.10 with latest updates.

[achillez (mewert)]

I fixed my problem by changing the session (in the options field) to start a new Gnome session, and not to use my last session which must have been fubar'd somehow. This is a bit counter-intuitive, may want to change this on future releases.