Re: Gnome hangs

José Rafael Carrero León wrote:
i've tried with the enforcing=0 option and i still get a system hang, i also checked the network
configuration and everything it's fine

this problem is becoming really annoying :(

That eliminates the mesa lib problem which was development related and the possibility gnome was locking due to an improper reference to localhost.

Where exactly does gnome lock up? Does it lockup at the splash screen on a certain ICON? Does it lock up when it is loaded? Do you only get a mouse cursor and a blank screen?

Anyway, if you cannot ctl-alt-Fn to a virtual terminal or ctl-alt-backspace in order to kill gnome, you probably might get some information by the below.
After the crash, reboot the computer into runlevel 3.
While in runlevel 3, check the /var/log/Xorg.0.log log for any information on why you have the lockup condition. Alternatively, you might find information in /var/log/Xorg.0.log.old from the KDE GUI related to the bombed session.

The /var/log/Xorg.0.log is session related and will be overwritten when you start a new X session.

If you find anything interesting in the log. It might help to pinpoint why you get this lockup.

Jim

--
You never hesitate to tackle the most difficult problems.

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: Can not see my desktop in vnc session that is started up from local display.
    ... I opened the terminal from local gnome desktop, and executed the "vncserver:1", the vncserver is started up, but I can't see the desktop in this vncsession, only the X server is displayed. ... However, I remotely login to the server, and from the terminal of this ssh session, I executed the same command as above to start up the vnc service, then I can see the desktop in the vncsession. ... I meant not to add the gnome-session at the end of the xstartup script. ...
    (Debian-User)
  • Re: Can not see my desktop in vnc session that is started up from local display.
    ... I opened the terminal from local gnome desktop, and executed the "vncserver ... session, I executed the same command as above to start up the vnc service, ... I see you're starting a Gnome session; I hope that you're not doing that from within another Gnome session for the same user account. ... and the sockets I see don't have any display numbers in their names. ...
    (Debian-User)
  • Re: GNOME is f*cked seven ways from Sunday
    ... > the window managers. ... but I don't rant about the whole Gnome project because of it. ... - gconf management tools woefully undocumented (an improving ... > window managers should be aware of gnome session mangement sucks, ...
    (Debian-User)
  • Re: setssionetc and sessionexit ignored under gnome?
    ... I suppose you could copy the first phase gnome startup file ... but you would have to remember to undo that if&when Sun fixes that "bug", ... run when running a non-CDE session (not just GNOME, ... folks migrating from Windows!). ...
    (comp.unix.solaris)
  • Re: MM B&V "ManyShortLivedThreads" lock up
    ... but the usage of "Update", if I don't replace it by and "Invalidate; Application.ProcessMessages;", the B&V will systematically lockup whenever I run it via a Terminal Services session and minimize that session. ... In a TS session the lockup will happen in between random benches, but rarely more than 2-3 benches after having minized the window, under regular XP, I've noticed that I get random lockups, if I minimize the B&V or have another window take the whole screen in front of it, ManyShortLivedThreads seems to be the point at which it happens, but it's hard to tell if it's actually during the benchmark or just after... ...
    (borland.public.delphi.language.basm)