Red Hat Bugzilla – Bug 183276
Last modified: 2007-11-30 17:11:25 EST
Description of problem:
Although gdm is able to start later, firstboot is dying.
Version-Release number of selected component (if applicable):
Version : 1.4.4
Release : 1
firstboot is dying.
firstboot should run, even if it has to fall back to vesa 640x480 to display
This might be related to the fact that I have a less-common screen size: 1920x1200.
Created attachment 125354 [details]
X.log from failed firstboot
Created attachment 125355 [details]
broken XConfig.test created by firstboot
Created attachment 125356 [details]
I don't like rhgb so I didn't install it. After installing rhgb, firstboot
worked fine. Looks like firstboot tries to start its own server if rhgb isn't
running. I would suggest that it do whatever rhgb is doing to configure server.
I've made some modifications to make starting without rhgb better. Please try
with FC5 and let me know if this is working for you.
Unfortunately, no. I'll upload the new XConfig.test and X.log in a moment.
Created attachment 125732 [details]
Created attachment 125733 [details]
I just did another yum update, but it didn't fix the problem. This appears to be
an selinux issue. After switching from enforcing to permissive mode firstboot
was able start an X server. I will attach an extract from my /var/log/messages.
Created attachment 126001 [details]
firstboot avc denied messages
You're still seeing an X server traceback, so something strange is going on in
the server itself.
I haven't seen anything like this recently, and the log files given aren't
detailed enough to find where the problem is.
Reporter, if you can still reproduce this issue with FC6 test3 or later, please
update this bug with the X log file from that.
Might as well just close this bug. I won't have time to test anything for a couple of months. If I see the problem again in the future, I'll open a new bug.
Closing based on comments.