Bug 4852
| Summary: | X server does not start | ||
|---|---|---|---|
| Product: | [Retired] Red Hat Linux | Reporter: | paulh |
| Component: | distribution | Assignee: | David Lawrence <dkl> |
| Status: | CLOSED ERRATA | QA Contact: | |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 6.0 | ||
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | i386 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | Bug Fix | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 1999-09-13 20:39:14 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
Please install the GNOME errata (available via http://www.redhat.com/support/) - they fix a lot of problems with GNOME. |
I hace installed RH6 on a variety of machines and have experienced a no. of situations where the Gnome desktop does not atart : 1. Typing 'startx' as root results in a warning message about the Gnome File Manager running as root. Clicking OK in this widget results in the File manager attempting to start. The FM core dumps and the warning msgs reappears. One is then stuck in an indefinite loop. The desktop icons never appear. THis error can disappear spontaneously when next logging in or when changing the screen resolution. It can also reappear ... 2. Booting into runlevel 5 does not always work. The nice graphical login screen appears but when attempting to login, the screen flashes a couple of times and the login screen reappears. I could not find any msgs in the system to indicate what the problem could be. Typing 'startx' from runlevel 3 was OK. 3. Typing 'startx' resulted in the msg : 'Authentication' failed. Logging out and back in *usually* (but not always) fixes this problem. Waiting a while or rebooting also fixes the problem. In one severe case, we found the directory /var/lock/console was missing. recreating the directory fixed the problem.