Bug 455145
| Summary: | GDM crashes on startup | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | Espen Stefansen <libbe> | ||||
| Component: | gdm | Assignee: | jmccann | ||||
| Status: | CLOSED WORKSFORME | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | urgent | Docs Contact: | |||||
| Priority: | low | ||||||
| Version: | 9 | CC: | beland, cschalle, rstrode | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | All | ||||||
| OS: | Linux | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2009-03-10 21:12:24 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: | |||||||
| Attachments: |
|
||||||
|
Description
Espen Stefansen
2008-07-12 19:17:56 UTC
Created attachment 311648 [details]
crash-log for gdm
Does anyone know what causes this? Because of this, I can't start in graphical mode. I must start in runlevel 3 and use startx. I'm not a gdm expert, but it seems likely that there is something about your configuration or hardware in particular that is triggering this crash. The first thing to do is to apply the latest system updates (e.g. with "yum update") if you haven't already, and see if the problem is fixed. Normally with crashes a backtrace is necessary for the developers to pin down the cause, but that is more difficult to do with gdm, since it happens before login. It might be more productive to try resetting the various packages you mentioned to their default configurations, one by one. If you would like to help find the cause of the problem, the best thing might be to do the following for each RPM, one by one: save the output of rpm -V, remove the RPM, move its configuration files and cached data aside (for later examination), reinstall the RPM, and retest. If you can find some local state that triggers the crash, that intelligence might be helpful in making the program more robust. You also have the option of upgrading to Fedora 10, to see if a newer version will be more robust in the face of whatever local state is triggering the crash in Fedora 9. If you merely wish to be rid of this problem (if you aren't already) and don't care to track down the source, a really fresh install of Fedora 9 or 10 (you may wish to format the partition to ensure that no old state is retained, but you will need to save personal data somewhere else, and reconfigure the system from scratch) will probably fix it (unless it is due to hardware peculiarity, not saved state). --- Fedora Bugzappers volunteer triage team https://fedoraproject.org/wiki/BugZappers This was fixed in an later update to gdm, so i'm closing this one. |