xfs - gui - recent updates

Gregory P. Ennis PoMec at PoMec.Net
Tue Jan 17 20:34:33 UTC 2006


On Tue, 2006-01-17 at 14:00 -0600, john bray wrote:
> On Tue, 2006-01-17 at 10:08 -0600, Gregory P. Ennis wrote:
> > On Mon, 2006-01-16 at 23:25 -0500, Tony Nelson wrote:
> > > At 4:15 PM -0600 1/16/06, Gregory P. Ennis wrote:
> > > >On Mon, 2006-01-16 at 12:03 -0600, Gregory P. Ennis wrote:
> > > >> On Mon, 2006-01-16 at 12:55 -0500, Jack Aboutboul wrote:
> > > >> > On Mon, 2006-01-16 at 11:09 -0600, Gregory P. Ennis wrote
> > > >> > > Other observations that I have made include the X.org.0.log entry of:
> > > >> > >
> > > >> > > Could not init font path element unix/:7100, removing from list!
> > > >> > >
> > > >> > > Fatal server error:
> > > >> > > could not open default font 'fixed'
> > > >> > >
> > > >> > > I have also noticed that the xfs daemon is not running and when I try to
> > > >> > > start it manually I get a "Segmentation Fault" error.
> > > >> > >
> > > >> > > Has anyone else reported problems related to these updates.  Can any of
> > > >> > > you help me.
> > > >> > >
> > > >> >
> > > >> > Greg,
> > > >> >
> > > >> > Do you use any non en-US locales with your machine?
> > > >> >
> > > >> > Jack
> > > >> >
> > > >> Jack,
> > > >>
> > > >> I am not sure what you mean by 'locales', but I do have Spanish, Greek,
> > > >> and Hebrew on both of these units in addition to English.  However, I
> > > >> also have these fonts installed on outer FC4 units that are still
> > > >> working.
> > > >>
> > > >> Greg
> > > >>
> > > >
> > > >Jack or others on the List,
> > > >
> > > >Any more ideas about this problem.  Do you think removing the Greek,
> > > >Hebrew, and Spanish fonts would resolve things, or how about removing
> > > >xfs and reinstalling it?
> > > 
> > > Try creating a new user, log out, and log in as that user.  If that fixes
> > > the problem, try copying hidden files and directories (names starting with
> > > ".") from your broken user to the new user until it breaks.
> > > ____________________________________________________________________
> > > TonyN.:'                       <mailto:tonynelson georgeanelson com>
> > >       '                              <http://www.georgeanelson.com/>
> > > 
> > Tony,
> > 
> > Both systems do not allow me to even get to the gui login screen. The
> > login screen is presented but it is not identifiable. It appears as the
> > resolution has been changed to something different than the monitor will
> > allow.  
> > 
> > However, I will try your method by using a terminal interface and
> > staring startx.  Thanks for you help!!!!
> > 
> > Thanks Again!
> > 
> > Greg
> > ----------------------------------------------------------------
> > 
> > Tony,
> > 
> > I tried creating a new user account, and doing a login on a terminal windown.  When I started 'startx' I received the same errors.
> > 
> > I had a third machine develop the same symptoms of not displaying a gui login screen.  I am able to see the gui boot up process but when each system tries to switch to the gui login the display presents itself with some screwy lines.
> > 
> > This all looks like the resolution has changed, but I have not changed any of the resolutions.
> > 
> > Is there a way to change the resolution from a terminal window.  I would like to try to change the resolution to the same as the default for the boot up gui process.
> > 
> > Sure would appreciate anyone's help.  
> > 
> > Greg Ennis
> > 
> > 
> 
> this seems similar to what i've been going through.  there appears to be
> no interest from redhat in helping with/fixing it.  there are a number
> of us caught on it, and nothing seems to be forthcoming.  see:
> https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=169238
> 
> i think this is all the same problem.  moving back to old x releases
> appears to be one of the only solutions.
> 
> i too see a flash of the gui login (gdm greeter) screen and then it
> crashes.  i've done a bit of investigation, but am at a loss for where
> to look further, at this point.  there appears to be something related
> to gdm (and kdm based on the bug report) starting x which causes it.
> 
> my current workaround is to boot into RL 3, login, and then run startx
> manually.  which, for me, works.  but it sure is a drag.
> 
> john
> 

John,

It is sure nice to know I am not the only one with the problem.  I
registered a bug report as well :
https://bugzilla.redhat.com/bugzilla/show_bug.cgi?id=178073

We have 3 desktop units that are disabled so far, and I have told
everyone else to abstain from rebooting their systems.  Unfortunately
using startx at the command line did not work for me on any of these
units I get errors related to not being able to find the fonts.  In
checking for xfs I find that it is not running and will not start at the
command line.  

I'll bet our problems are related and it would not surprise me if RH
merges my Bug Report with yours.

If you figure something out in the meantime please let me know, and I
will do the same for you.

Greg





More information about the fedora-list mailing list