this is a strange one. running 11.2 pae 32 bit kernel with all the most recent updates and gnome. This is a fresh install. I built the machine, and then installed all my repositories and software, and used the machine for about 2 days, and now when I log in it hangs on logging into gnome. it’s strange because the wireless notification about available wireless networks is in the top left corner of the screen, and nothing else happens. I can log in as root.
I also had this issue before I formatted the machine (that’s why I formatted)
Any help would be greatly appreciated.
Also if theres any further information that would be helpful, please let me know.
is metacity in icewm as well because it’s broken too. (although i’ve never tried to log into it before now, so it might be broken for unrelated reasons.)
reading the thread now, sounds like my exact symptoms.
i can’t believe i reformatted when i could have just downgraded metacity! it happened after a huge update pack… anyway hopefully they’ll fix it. If anyone knows when they’ve fixed the update, reply to this thread, that way I know I can let that update through on my systems.
Hi
Glad you have it functional again. I would keep an eye on the bug
555027 as that will give you a better picture (you can always add your
experience to it ).
–
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 2.6.27.42-0.1-default
up 17 days 15:46, 3 users, load average: 0.21, 0.10, 0.11
GPU GeForce 8600 GTS Silent - CUDA Driver Version: 190.53
a word to the wise: Linux is a very stable and predictable operating
system…that is to say, given the same conditions (good install,
good upgrade back to the same state) you can expect the SAME system…
that is, if you ‘suddenly’ can’t log in (or out, or browse or
whatever) if you start over and get to the same state you should
EXPECT the same fault…
now, i know SOME operating systems begin their repairs with a fresh
install…
this ain’t that system…it may well have killed itself in its overly
fragile ‘registry’ or whatever…
here you should never expect a reboot or reinstall to fix
anything…instead you should expect it to replicate the existing
condition…
now, there is an exception (always) if the USER did something that
killed the system then a reboot and or reinstall may fix the problem
for a while…UNTIL the user makes the same mistake again…
which brings me to: do NOT log into Gnome or KDE as root…as far as i
know there is no documented case where that is required [for
example, Malcom Lewis had you log out as root FIRST, and THEN proceeded]
yes, i know you were just trying to see if root could log in…but,
what did you learn…did you fix it…did it add to your knowledge
about what the fault was…or lead you to a solution…etc, etc, etc
