[clug-talk] Can't boot to kde or gnome
carlsonmark at gmail.com
Mon Oct 1 14:46:43 PDT 2007
On 9/30/07, Richard Carter <carter.r.a.l at gmail.com> wrote:
> However, if I choose "Console Login'" from the Menu tab login.succeeds and I
> get a message "You have new mail", which I don't understand.
"You have new mail" when you log in as root: this generally means that
your system has been running cron-jobs as root (often security-related
jobs such as checking for UID/GID changes, disk usage, etc.) To read
them, use the 'mail' command. At the mail prompt, (&), use 'n' to
read each message if you would like to. I use a .forward file in the
/root directory to send these messages to an email account I actually
use. It can be nice for boxes you don't look at often, to see if the
disk is filling up, or if there have been any ssh brute-force attacks,
On 10/1/07, Richard Carter <carter.r.a.l at gmail.com> wrote:
> Szemir; After I log in as root, startx starts the gnome desk top!!! But if
> I enter startx as robin lines from /var/log/Xorg.0.log (I think) are
> displayed none of which begin with EE although one line did say that the
> kernel was disabling IRQ #201. Using find I couldn't find a file called
The file is named .xession-errors, and it is usually in the home
directory of your user (/home/user/.xsession-errors)
'locate' is often more helpful than 'find' for finding files, if it is
installed, that is
> Gustin: I checked gdm.log and kde.log but I couldn't see any thing that
> looked l like an error. Xorg.0.log contained some warnings about missing
> fonts, the mode of the clock and the fact that AIGLX: 30 driver doesn't
> support some visuals but nothing beginning with EE I also checked
> /var/messages. This is a very big file most of which looked innocent
> although it did say that a message handler couldn't be found and that there
> was a bad irq.
> The problem with all this is that I don't really know what to look for in
> all these log files so I may well have missed something important. I wonder
> of the problem is that the kde login manager is corrupted?
> Any further suggestions?
Try a more basic window manager, such as twm. If your display manager
(where you are logging in from) is returning to itself, it is because
whatever it tried to run failed to do so. This is what happens when
you use ctrl-alt-backspace to exit from kde/gnome. So what you need
to do is find out what is causing it to fail. This could be in the
xorg log or .xsession-errors. It is usually easier to log in to the
console as your user, run startx, and go from there.
See if there is a /home/username/.xinitrc file and report back with
This is the #2 reason I don't use a display manager if I can help it.
Just one more thing to break. (#1 reason being it makes it difficult
to use other ttys in some circumstances.)
More information about the clug-talk