GDM doesn't start at boot time (I need to run it from terminal)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
gdm (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: gdm
LUCID installation running well since May 19th (3 days ago). Since that day, at boot time, every day, GDM stopped to start automatically. Then I need to login at terminal and run "sudo gdm".
I'm not expert of this stuff. I only got this ouptut /var/log/daemon.log (see attached LOG file). It seems to be a bug appeared since 3 days ago, and not before.
Furthermore, when GDM is later up and running, at login screen language-session option is no more available: the option menus are not visible any more.
Any help will be appreciated. Many thanks in advance.
Ciao from Italy.
CM
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: gdm 2.30.0-0ubuntu5
ProcVersionSign
Uname: Linux 2.6.32-22-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Fri May 21 08:20:26 2010
ExecutablePath: /usr/sbin/
ProcEnviron:
LANGUAGE=
PATH=(custom, no user)
LANG=it_IT.UTF-8
SHELL=/bin/bash
SourcePackage: gdm
XsessionErrors:
(polkit-
(gnome-
I have what seems to be the same issue. When the computer is turned on, the splash screen does not come up; instead it boots as though I had pressed Ctrl-F1 with a Console screen. Then, gdm fails to start, and either leaves me at tty1 of tty7. I have to log into the Console session, and then run "sudo gdm start." After this, gdm works correctly, and I can log on.
I believe this started happening after some kernal updates. I found a solution to this problem at this website: news.softpedia. com/news/ How-to- Fix-the- Big-and- Ugly-Plymouth- Logo-in- Ubuntu- 10-04-140810. shtml
http://
This source fixes it so that gdm starts and brings up the login screen.
This system is from a standard install with mostly default settings from a live cd, Ubuntu 10.04 desktop.
The only non-standard parts of my computer are:
AMD 64 bit processor
intergrated nvidia video card: geForce 7200
I have done nothing to grub except as outlined in the softpedia.com article, and that after the problem.