I have GNOME, and it worked well before.
But yesterday, I couldn't enter GNOME, but I was sure X worked well.
When I try to start GNOME, it shows me that it is starting window
manager, but doesn't do anything more.
Does GNOME have logs? Is there any way to what is wrong with my GNOME?

[ Post a follow-up to this message ]

ZhengDa wrote:
> I have GNOME, and it worked well before.
> But yesterday, I couldn't enter GNOME, but I was sure X worked well.
> When I try to start GNOME, it shows me that it is starting window
> manager, but doesn't do anything more.
> Does GNOME have logs? Is there any way to what is wrong with my GNOME?

You most likely have to boot into Recovery Mode - if using 'gdm' as the
DM, you should be able to select it (or just Console Mode) from the
Login Screen

look at /var/log/messages - and other relevant log files in /var/log
like /gdm.log.0 -- I use KDE, so mine is at /var/log/kdm.log and
/var/log/kdm.log.0

perhaps;
$ sudo less /var/log/kern.log.0
to view a page full only at a time - use Up/Down -or- Enter to scroll
-- even PageUp/Down perhaps

kern.log(s) and syslog.log files need Root privileges, which is why
'sudo' prefixes the 'less' pager command in above example. If you're
logged in as root (text mode hopefully only), you don't need to use
'sudo'

and look for any /var/log/gdm log files you see in there - and use tail
-30 to view only the last 30 lines - as one might do when viewing the
kern.log file(s) above.

Try also;
$ dmesg | tail -30

which will display the last 30 lines of the dmesg output - use 'dmesg |
less' (or 'dmesg | more') instead to see the whole file from the
beginning.

What Distro(s) and Kernel version(s) and hardware ??

Unfortunately, I forget ATM how to view/open the Gzip archived log
files from within the Shell -- the ones that appear as
/syslog.0[1,2,3,4].gz -- again root/adm privs are needed - so use
'sudo' to prefix each command

[ Post a follow-up to this message ]

iforone wrote:
> [...]
> Unfortunately, I forget ATM how to view/open the Gzip archived log
> files from within the Shell -- the ones that appear as
> /syslog.0[1,2,3,4].gz [...]

zless syslog.1.gz

Or,

gzip -d -c syslog.1.gz | less

[ Post a follow-up to this message ]

Mumia W. wrote:
> iforone wrote: 
>
> zless syslog.1.gz
>
> Or,
>
> gzip -d -c syslog.1.gz | less

Sweet!
Thank you ...so;

$ sudo zless /var/log/daemon.log.0
works great, when not already in the /var/log Dir

and / or

$ sudo gzip -dc syslog.1.gz | less
when already 'cd' into that current Dir (/var/log)

IOW - For the OP (Orig Poster);
do this to 'cd' (Change Directory)
$ cd /var/log
then enter that command above ($ sudo gzip -dc syslog.1.gz | less) to
view the contents of the now "older" syslog.1.gz file -- or just place
the Full path in the command if you're at '~' (/home) as User (ex; $
sudo gzip -dc /var/log/syslog.1.gz | less).

The '$' sign (that precedes all my commands, in the examples)
designates User mode, and is NOT to be typed as part of the command --
whereas a '#' (in place of the $) would mean you are 'root' -- Note;
the "hash" (#) symbol (or pound '#') symbol is used in shell scripts to
denote Comments, which the Shell ignores, anything placed after a '#',
but only for that Line - so each line of any Comments (in a Shell
script and others) requires a '#' to precede the comments...whether at
the beginning of that line, or somewhere in the middle of that line,
after some command occurs. View the files in /etc/rc.d

As examples, both commands work equally as well -- I had tried 'zgrep'
briefly, but forgot the syntax and likely it wouldn't work(?), and yet
I'd think perhaps it could (to pluck out relevant info)...I need to
look in the 'man zgrep' pages.

Thanks Mumia ;-) for the reminder and enlightenment (why do I get the
urge to say Mumma-Mia, and crave Italian food all of a sudden ? :-) )

Regards

[ Post a follow-up to this message ]

iforone wrote:
> Mumia W. wrote: 
>
> Sweet!
> Thank you ...so;
>
> $ sudo zless /var/log/daemon.log.0
> works great, when not already in the /var/log Dir
>
> and / or
>
> $ sudo gzip -dc syslog.1.gz | less
> when already 'cd' into that current Dir (/var/log)
>
> IOW - For the OP (Orig Poster);
> do this to 'cd' (Change Directory)
> $ cd /var/log
> then enter that command above ($ sudo gzip -dc syslog.1.gz | less) to
> view the contents of the now "older" syslog.1.gz file -- or just place
> the Full path in the command if you're at '~' (/home) as User (ex; $
> sudo gzip -dc /var/log/syslog.1.gz | less).
>
> The '$' sign (that precedes all my commands, in the examples)
> designates User mode, and is NOT to be typed as part of the command --
> whereas a '#' (in place of the $) would mean you are 'root' -- Note;
> the "hash" (#) symbol (or pound '#') symbol is used in shell scripts to
> denote Comments, which the Shell ignores, anything placed after a '#',
> but only for that Line - so each line of any Comments (in a Shell
> script and others) requires a '#' to precede the comments...whether at
> the beginning of that line, or somewhere in the middle of that line,
> after some command occurs. View the files in /etc/rc.d
>
> As examples, both commands work equally as well -- I had tried 'zgrep'
> briefly, but forgot the syntax and likely it wouldn't work(?), and yet
> I'd think perhaps it could (to pluck out relevant info)...I need to
> look in the 'man zgrep' pages.
>
> Thanks Mumia ;-) for the reminder and enlightenment (why do I get the
> urge to say Mumma-Mia, and crave Italian food all of a sudden ? :-) )
>
> Regards

whooops!
I think I have most of what's written above correctly... but I
mistakenly left out the '~' when in the /home Dir -- so;
~$
is what you should see, after you localhost@localdomain name...like
this;

Username@MachineName:~$

would designate User mode in /home Dir, within any shell you open as a
User (replace $Username with what the actual Username is -- the Dollar
Sign preceding Username [$Username] in this instance/example designates
"default" or "current"..and is replaced/read by the Shell to mean
"Current User" , no matter what their Name is)

Sorry for my poor interpretation, and misunderstanding of how to
explain what I know...or think I understand

Regards

[ Post a follow-up to this message ]