Ubuntu 8.04, why does logging back in cause black screen?

Asked by george_rutkay

History:

Dell Optiplex GX260, 2 gig RAM, Pentium 4 2.5GHz, On-board Intel 82845 video chipset, 64 meg video RAM.

Tried running 8.10 but had this problem where the screen would go black when logging in, and 915resolution isn't supported. The epitome of uselessness!

So I went back - BACK - to 8.04 which had run well enough previously.

Only difference this time? Now I have "Normal releases" enabled in the Update manager, as opposed to "Long Term support releases" which I had in the 8.04 installation before I tried 8.10.

Now this dumb black screen issue has come up under this installation of 8.04 using "Normal releases". I don't know why.

When it does occur, I hit Ctrl+Alt+F1 and login to the text screen. The message on the screen says "No resume image", whatever that means. I cannot get the display manager to run. When I type StartX it comes back saying Fatal error for something.

What's going on? How do I solve this so it logs back into the normal desktop screen?

Do I have to wipe the drive and reinstall 8.04 again? (I really hate doing that, such a waste of my time).

Question information

Language:
English Edit question
Status:
Solved
For:
Ubuntu Edit question
Assignee:
No assignee Edit question
Solved by:
george_rutkay
Solved:
Last query:
Last reply:
Revision history for this message
george_rutkay (yaktur) said :
#1

Anybody?

Revision history for this message
george_rutkay (yaktur) said :
#2

It happened again, while I was outside fixing my wife's car, she tried to log-in and get e-mails and it went to black screen!

Here's the message I got when I Ctrl+Alt+F1 and login at command line:

"Fatal Server error: Server is already active for display 0
If the server is no longer running, remove /tmp/XO.lock and start again

Invalid MIT-MAGIC-COOKIE-1 keygiving up

xinit: Resource temporarily unavailable (errno 11): unable to connect to X server.
xinit: No such process (errno 3): server error"

What the heck is going on with this darned thing? It's insane or something! How do I fix this? Do I un-do whatever system updates (and if so, just HOW do I do that?)!

HELP?

PS: At command line I figured out that I can reboot the machine by typing sudo reboot, then entering my password. Rebooting ALWAYS solves this problem, but it shouldn't be necessary!

Revision history for this message
george_rutkay (yaktur) said :
#3

I've been told that there's a software conflict between the graphics chipset and some of the updates. My only solution would be to reinstall the system once again.

Arrggghh!!! This is so dumb, software shouldn't be like this!

So I've reinstalled now.