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
