I was looking at this a little bit. It looks like the apps are sitting
there eating up memory till they get OOM-killed (OOM==out of memory, of
course). You can check this by running 'dmesg' and looking for
errors.
I did some further ltracing on a few programs. "metacity" seems to go
till it gets to "pango_context_get_language" and then
"pango_context_get_matrics", and then sits till I killed it.
"gnome-session" didn't give anything so clear, but seemed to be opening
a font, reading a lot of bytes, and then moving on, forever.
For S&G I checked fluxbox too, which hung in XftFontOpenName, still
eating away memory.
The really funny thing is if I log in via a fail-safe session, root
*can* start gnome-session.
On Thu, 2006-02-02 at 11:28 -0600, Brian Millett wrote:
I need some good advice on how to debug this problem.
I have yum updated rawhide today (2/2/2006) on a x86 toshiba laptop
and I still have a kind of broken gnome that broke 2/1/2006.
What I mean is that as my current user, I try to startx from runlevel
3 and it goes for a while and then dies and I am back at the command
prompt. I can add a new user and login as that user and can startx
just fine as a new virgin user. But from my old user, gnome will not
start.
I do not have any error messages in /var/log/messages
nor /var/log/Xorg.0.log nor any where else that I can think of.
How do I debug this? Can X be started in a verbose debug mode?
I'd like to file a bugzilla, but on what? System is hosed is not a
menu item, nor very helpful.
Thanks.
--
fedora-test-list mailing list
fedora-test-list(a)redhat.com
To unsubscribe:
https://www.redhat.com/mailman/listinfo/fedora-test-list