RE: gnome startup error

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



On Mon, 2003-05-19 at 17:59, Bob Mclaughlin wrote:
> Joe,
> I did a mkdir /tmp and it's in.  Tried startx and, among
> other things, I get a Fatal server error: could not open
> default font 'fixed'
> Bob
> 

Have you checked your .xsession-errors file for any messages? From the
console, in your regular user account, run "less ~/.xsession-errors"
If it says anything about an .ICEauthority file, do the following:

ls -l ~/.ICEauthority

if it shows the file is owned by root, do the following:

su -
<enter root password>
chown <username>:<usergroup> ~<username>/.ICEauthority
exit

In your case, "usergroup" should be the same as "username".

> >-----Original Message-----
> >From: shrike-list-admin@xxxxxxxxxx
> >[mailto:shrike-list-admin@xxxxxxxxxx]On Behalf Of
> >Bob Mclaughlin
> >Sent: Monday, May 19, 2003 7:45 PM
> >To: shrike-list@xxxxxxxxxx
> >Subject: RE: gnome startup error
> >
> >
> >Joe,
> >I think the only unusual thing is it had a power
> >interruption when setting idle.  Could the tmp directory be
> >a sub under another directory and ls -l /tmp not have found
> >it?  Also, what is the command to make a directory?
> >Bob
> >
> >>-----Original Message-----
> >>From: shrike-list-admin@xxxxxxxxxx
> >>[mailto:shrike-list-admin@xxxxxxxxxx]On Behalf Of Joe
> >>Sent: Monday, May 19, 2003 7:07 PM
> >>To: shrike-list@xxxxxxxxxx
> >>Subject: Re: gnome startup error
> >>
> >>
> >>Bob Mclaughlin wrote:
> >>
> >>>Joe,
> >>>I'm sure Jeremy will come back with the next step and
> >>>reasons for reboot.  Anyhow, the perms in / are all
> >>>drwxr-xr-x except lost+found and root.  I get -
> >>No such file
> >>>or directory for ls -l /tmp.  What d'ya think?
> >>>
> >>
> >>Ouch - without a /tmp directory you'll be hard
> >>pressed to do just about anything meaningful.
> >>
> >>The present crisis may be averted by recreating
> >>/tmp and giving it permissions 1777 -
> >>
> >>The big question is, how did it get nuked? and
> >>whatever nuked /tmp, what else might it have
> >>nuked?
> >>
> >>After recreating /tmp, try the command
> >>
> >>rpm -Va | tee rpmva.out
> >>
> >>and see what packages have damaged or
> >>missing pieces....
> >>
> >>If /tmp was the only problem, you should
> >>be able to start X again.
> >>
> >>Joe
> >>
> >>
> >>
> >>
> >>--
> >>Shrike-list mailing list
> >>Shrike-list@xxxxxxxxxx
> >>https://www.redhat.com/mailman/listinfo/shrike-list
> >>
> >
> >
> >
> >--
> >Shrike-list mailing list
> >Shrike-list@xxxxxxxxxx
> >https://www.redhat.com/mailman/listinfo/shrike-list
> >
-- 
Michael Knepher <limbo@xxxxxxxxxxxxxx>




[Index of Archives]     [Fedora Users]     [Centos Users]     [Kernel Development]     [Red Hat Install]     [Red Hat Watch]     [Red Hat Development]     [Red Hat Phoebe Beta]     [Yosemite Forum]     [Fedora Discussion]     [Gimp]     [Stuff]     [Yosemite News]

  Powered by Linux