Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 115755 - X Window System Crash Firstboot, then everytime
Summary: X Window System Crash Firstboot, then everytime
Keywords:
Status: CLOSED DUPLICATE of bug 116937
Alias: None
Product: Fedora
Classification: Fedora
Component: firstboot
Version: rawhide
Hardware: i686
OS: Linux
medium
high
Target Milestone: ---
Assignee: Brent Fox
QA Contact:
URL:
Whiteboard:
: 115758 (view as bug list)
Depends On:
Blocks: FC2Blocker
TreeView+ depends on / blocked
 
Reported: 2004-02-15 19:33 UTC by Mark Tuttle
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:01:18 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
/var/log/messages (deleted)
2004-02-17 15:52 UTC, Mark Tuttle 		no flags Details
new /var/log/messages (deleted)
2004-02-23 01:18 UTC, Mark Tuttle 		no flags Details
View All

Description Mark Tuttle 2004-02-15 19:33:58 UTC 
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
Here is the error that occurs:

** (firstboot.py.1998): WARNING **: 'gtktextsearchflag' is not an 
enum type

Window manager warning: Failed to open connection to session manager, 
so window positions will not be saved: SESSION_MANAGER environment 
variable not defined


Version-Release number of selected component (if applicable):
Fedora Core 2 test1's version packaged

How reproducible:
Always

Steps to Reproduce:
1. Install Fedora Core 2 test1 with all packages
2. Run Fedora Core 2
3. Get the bug, and then turn off the computer
    

Actual Results:  The computer freezes afterwords, and you are locked 
out.

Expected Results:  You should have been able to booted into X Window 
System 

Additional info:

This happens everytime, and I cannot determine the source of the 
problem and/or how to fix it.
Comment 1 Mike A. Harris 2004-02-15 21:19:39 UTC 
*** Bug 115758 has been marked as a duplicate of this bug. ***
Comment 2 Brent Fox 2004-02-16 21:29:34 UTC 
Can you attach the /var/log/messages file?
Comment 3 Mark Tuttle 2004-02-17 15:52:27 UTC 
Created attachment 97751 [details]
/var/log/messages

Here is /var/log/messages
Comment 4 Brent Fox 2004-02-20 01:24:18 UTC 
The /var/log/messages doesn't contain any firstboot messages...that is
surprising to me.  Firstboot will usually write out some error
messages when it runs.  Perhaps this file was from a day or so after
firstboot had been run?  Try grepping for firstboot in
/var/log/messages* and see if the older logs are still around.
Comment 5 Mark Tuttle 2004-02-23 01:18:57 UTC 
Created attachment 97936 [details]
new /var/log/messages

I reformatted my hard drive and installed Fedora Core 2 test1 again. I ran
Fedora (firstboot) until it froze to the same spot again. I then popped CD 1 in
my computer and restarted. Using Fedora's rescue program, I copied the messages
file to a floppy and uploaded it here again.
Comment 6 Brent Fox 2004-03-04 18:37:45 UTC 
I'm trying to figure out if the crash is related to firstboot or XFree86.

A couple of questions:

1) Did the installer work in graphical mode?  Or did you use text mode?

2) After rebooting after the installation is finished, do you see the
graphical bootup screen?  This should happen before the firstboot
program gets run.  All you should see on the screen is a computer icon
and a progress bar as the system is starting up.
Comment 7 Mark Tuttle 2004-03-04 20:45:55 UTC 
1) Did the installer work in graphical mode?  Or did you use text 
mode?

Answer: No, I can only install Fedora in text mode, not graphical. If 
I was to install it in graphical, I would only get as far as the X 
mouse pointer and patterned backround

2) After rebooting after the installation is finished, do you see the
graphical bootup screen?  This should happen before the firstboot
program gets run.  All you should see on the screen is a computer icon
and a progress bar as the system is starting up.

Answer: Yes, I see the graphical bootup screen working, and it almost 
finishes actaully. When it is about 90 percent done, (while still in 
graphical) the console maximizes on screen and errors out at:

** (firstboot.py.1998): WARNING **: 'gtktextsearchflag' is not an 
enum type

Window manager warning: Failed to open connection to session manager, 
so window positions will not be saved: SESSION_MANAGER environment 
variable not defined
Comment 8 Brent Fox 2004-03-04 21:40:53 UTC 
Ok, the fact that the graphical installer doesn't work makes this bug
sound like a dupe of bug 116937.

*** This bug has been marked as a duplicate of 116937 ***
Comment 9 Greg Hogan 2004-03-06 02:32:28 UTC 
I had this exact problem.  It was a problem with the radeon xfree86
driver and my radeon 9800.  The man page for the radeon driver only
claims support up to r350 (9700) cards. Not r360 (9800) cards.  Maybe
not radeon 9600's either.  But adding "ChipID 0x4E46" to my XF86Config
makes the driver think I have a 9700 and x works right again.  From
what I've read, only certain drawing operations trigger the lock up.
Comment 10 Red Hat Bugzilla 2006-02-21 19:01:18 UTC 
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.
Note You need to log in before you can comment on or make changes to this bug.