Will someone please take a look at this and help me fix the fix font?

OSR 5.06

I get this message after trying startx at the # from the console"


failed to set default font path '/usr/lib/X11/fonts/misc/,/usr/lib/X11/
fonts/Speedo/,/usr/lib/X11/fonts/Type1/,/usr/lib/X11/fonts/75dpi/,/usr/
lib/X11/fonts/100dpi/'
Fatal server error:
could not open default font 'fixed'
giving up.
xinit: I/O error (errno 5): unable to connect to X server

waiting for X server to shut down .........

xinit: X server slow to shut down, sending KILL signal.

Help appreciated.

wj

On 20 Dec, 19:34, willjay <jim.highsm...@gmail.com> wrote:
> Will someone please take a look at this and help me fix the fix font?
>
> OSR 5.06
>
> I get this message after trying startx at the # from the console"
>
> failed to set default font path '/usr/lib/X11/fonts/misc/,/usr/lib/X11/
> fonts/Speedo/,/usr/lib/X11/fonts/Type1/,/usr/lib/X11/fonts/75dpi/,/usr/
> lib/X11/fonts/100dpi/'
> Fatal server error:
> could not open default font 'fixed'
> giving up.
> xinit: I/O error (errno 5): unable to connect to X server
>
> waiting for X server to shut down .........
>
> xinit: *X server slow to shut down, sending KILL signal.
>
> Help appreciated.
>
> wj

You're a bit short of data here. Did X *ever* work? Is this a clean
install, or one on which people have done lots of patches? I'm seeing
the results right now of a machine that's had patches and local
modifications randomly installed on it. If possible, you should be
able to rlogin or slogin into it (if you've installed OpenSSH!) and be
able to look at the system.

On Dec 21, 3:52*am, Nico Kadel-Garcia <nka...@gmail.com> wrote:
> On 20 Dec, 19:34, willjay <jim.highsm...@gmail.com> wrote:
>
>
>
>
>
> > Will someone please take a look at this and help me fix the fix font?
>
> > OSR 5.06
>
> > I get this message after trying startx at the # from the console"
>
> > failed to set default font path '/usr/lib/X11/fonts/misc/,/usr/lib/X11/
> > fonts/Speedo/,/usr/lib/X11/fonts/Type1/,/usr/lib/X11/fonts/75dpi/,/usr/
> > lib/X11/fonts/100dpi/'
> > Fatal server error:
> > could not open default font 'fixed'
> > giving up.
> > xinit: I/O error (errno 5): unable to connect to X server
>
> > waiting for X server to shut down .........
>
> > xinit: *X server slow to shut down, sending KILL signal.
>
> > Help appreciated.
>
> > wj
>
> You're a bit short of data here. Did X *ever* work? Is this a clean
> install, or one on which people have done lots of patches? I'm seeing
> the results right now of a machine that's had patches and local
> modifications randomly installed on it. If possible, you should be
> able to rlogin or slogin into it (if you've installed OpenSSH!) and be
> able to look at the system.- Hide quoted text -
>
> - Show quoted text -

This server has been up and working for many years, it has a
commercial version of ssh installed and everything was working fine,
then all of a sudden startx fails to start. You can ssh into it and
console text is working as well as everything else. I may not have the
proper video drive installed.

How can you say "everything was working fine"
and "I think I don't have the right video driver installed" in the same
paragraph?

I any event, your error message doesn't even slightly hint at a
misconfigured video driver.

There are so many obvious questions which you haven't answered, which you
could certainly have asked and answered for yourself had you tried the
teeniest bit. If you have at least made a reasonable try at solving this
yourself, then where is the description of what you tried, and what you saw?
Lacking those I have to assume you are guilty of asking everyone in the
world to tie your shoes for you.

For example:
Have you looked in the paths shown in the error message?
Are there files there?
Do they look the same as on other, working OSR5 boxes. (names, sizes, dates,
perms)
Did you tell the customer to take the tape from the nightly backup the
previous night and the oldest backup tape they have, and put them to the
side and not let them get overwritten with new backups?
Have you consulted those tapes for differences in the /usr/lib/X11 tree on
the tape vs on the disk?
Have you even run "man startx" ?
"man startx" on a osr5 box points to "man Xsco" which says "Errors are
logged in the file /usr/adm/X*msgs" which btw, you could also find without
man's help, because on a sco osr5 box /var/adm is where many things are
logged, and looking in that dir, X0msgs is certainly a file that looks like
it has to do with X. So, have you looked to see what is in /usr/adm/X0msgs?
Is there any X1msgs X2msgs ? generally there should only be one X0msgs, if
there are others, then you are starting up multiple x servers on multiple
consoles, which generally you don't want.
The rest of those man pages suggest other ways to diagnose it further too,
like running the X binary or the xinit program manually with extra options
to show you in more detail why it's failing.

If you have actually done any of that, then why didn't you say so, and say
what you found?

I think the real question is, who cares that X doesn't work on a SCO OSR5
box?
OSR5's X is terrible and I can't imagine too many people used it.
I always disabled it on all my (customers) boxes.

Back before apache, there was one reason to use X at the console, to
configure the netscape http server. That hasn't been relevant in years.

Brian K. White brian@aljex.com http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!


----- Original Message -----
From: "willjay" <jim.highsmith@gmail.com>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Sunday, December 23, 2007 2:48 PM
Subject: Re: startx fails


On Dec 21, 3:52 am, Nico Kadel-Garcia <nka...@gmail.com> wrote:
> On 20 Dec, 19:34, willjay <jim.highsm...@gmail.com> wrote
> > Will someone please take a look at this and help me fix the fix font?
> > OSR 5.06
> > I get this message after trying startx at the # from the console"
> > failed to set default font path '/usr/lib/X11/fonts/misc/,/usr/lib/X11/
> > fonts/Speedo/,/usr/lib/X11/fonts/Type1/,/usr/lib/X11/fonts/75dpi/,/usr/
> > lib/X11/fonts/100dpi/'
> > Fatal server error:
> > could not open default font 'fixed'
> > giving up.
> > xinit: I/O error (errno 5): unable to connect to X server
>
> > waiting for X server to shut down .........
>
> > xinit: X server slow to shut down, sending KILL signal.
>
> > Help appreciated.
>
> > wj
>
> You're a bit short of data here. Did X *ever* work? Is this a clean
> install, or one on which people have done lots of patches? I'm seeing
> the results right now of a machine that's had patches and local
> modifications randomly installed on it. If possible, you should be
> able to rlogin or slogin into it (if you've installed OpenSSH!) and be
> able to look at the system.- Hide quoted text -
>
> - Show quoted text -

This server has been up and working for many years, it has a
commercial version of ssh installed and everything was working fine,
then all of a sudden startx fails to start. You can ssh into it and
console text is working as well as everything else. I may not have the
proper video drive installed.

On Sun, 23 Dec 2007, willjay wrote:

> On Dec 21, 3:52*am, Nico Kadel-Garcia <nka...@gmail.com> wrote:
>> On 20 Dec, 19:34, willjay <jim.highsm...@gmail.com> wrote:
>>
>>
>>
>>
>>
>>> Will someone please take a look at this and help me fix the fix font?
>>
>>> OSR 5.06
>>
>>> I get this message after trying startx at the # from the console"
>>
>>> failed to set default font path '/usr/lib/X11/fonts/misc/,/usr/lib/X11/
>>> fonts/Speedo/,/usr/lib/X11/fonts/Type1/,/usr/lib/X11/fonts/75dpi/,/usr/
>>> lib/X11/fonts/100dpi/'
>>> Fatal server error:
>>> could not open default font 'fixed'
>>> giving up.
>>> xinit: I/O error (errno 5): unable to connect to X server
>>
>>> waiting for X server to shut down .........
>>
>>> xinit: *X server slow to shut down, sending KILL signal.
>>
>>> Help appreciated.
>>
>>> wj
>>
>> You're a bit short of data here. Did X *ever* work? Is this a clean
>> install, or one on which people have done lots of patches? I'm seeing
>> the results right now of a machine that's had patches and local
>> modifications randomly installed on it. If possible, you should be
>> able to rlogin or slogin into it (if you've installed OpenSSH!) and be
>> able to look at the system.- Hide quoted text -
>>
>> - Show quoted text -
>
> This server has been up and working for many years, it has a
> commercial version of ssh installed and everything was working fine,
> then all of a sudden startx fails to start. You can ssh into it and
> console text is working as well as everything else. I may not have the
> proper video drive installed.
>
>

Do you need to start or re-start xfs ?

Brian K. White wrote (on Sun, Dec 23, 2007 at 04:24:45PM -0500):
>
> I think the real question is, who cares that X doesn't work on a SCO OSR5
> box?
> OSR5's X is terrible and I can't imagine too many people used it.
> I always disabled it on all my (customers) boxes.
>
> Back before apache, there was one reason to use X at the console, to
> configure the netscape http server. That hasn't been relevant in years.

Perhaps OP's solution is as simple as 'scologin disable'?

--
_________________________________________
Nachman Yaakov Ziskind, FSPA, LLM awacs@ziskind.us
Attorney and Counselor-at-Law http://ziskind.us
Economic Group Pension Services http://egps.com
Actuaries and Employee Benefit Consultants

On Dec 23, 4:24*pm, "Brian K. White" <br...@aljex.com> wrote:
> How can you say "everything was working fine"
> and "I think I don't have the right video driver installed" in the same
> paragraph?
>
> I any event, your error message doesn't even slightly hint at a
> misconfigured video driver.
>
> There are so many obvious questions which you haven't answered, which you
> could certainly have asked and answered for yourself had you tried the
> teeniest bit. If you have at least made a reasonable try at solving this
> yourself, then where is the description of what you tried, and what you saw?
> Lacking those I have to assume you are guilty of asking everyone in the
> world to tie your shoes for you.
>
> For example:
> Have you looked in the paths shown in the error message?
> Are there files there?
> Do they look the same as on other, working OSR5 boxes. (names, sizes, dates,
> perms)
> Did you tell the customer to take the tape from the nightly backup the
> previous night and the oldest backup tape they have, and put them to the
> side and not let them get overwritten with new backups?
> Have you consulted those tapes for differences in the /usr/lib/X11 tree on
> the tape vs on the disk?
> Have you even run "man startx" ?
> "man startx" on a osr5 box points to "man Xsco" which says "Errors are
> logged in the file /usr/adm/X*msgs" which btw, you could also find without
> man's help, because on a sco osr5 box /var/adm is where many things are
> logged, and looking in that dir, X0msgs is certainly a file that looks like
> it has to do with X. So, have you looked to see what is in /usr/adm/X0msgs?
> Is there any X1msgs X2msgs ? generally there should only be one X0msgs, if
> there are others, then you are starting up multiple x servers on multiple
> consoles, which generally you don't want.
> The rest of those man pages suggest other ways to diagnose it further too,
> like running the X binary or the xinit program manually with extra options
> to show you in more detail why it's failing.
>
> If you have actually done any of that, then why didn't you say so, and say
> what you found?
>
> I think the real question is, who cares that X doesn't work on a SCO OSR5
> box?
> OSR5's X is terrible and I can't imagine too many people used it.
> I always disabled it on all my (customers) boxes.
>
> Back before apache, there was one reason to use X at the console, to
> configure the netscape http server. That hasn't been relevant in years.
>
> Brian K. White * *br...@aljex.com * *http://www.myspace.com/KEYofR
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro *BBx * *Linux *SCO *FreeBSD * *#callahans *Satriani *Filk!
>
>
>
> ----- Original Message -----
> From: "willjay" <jim.highsm...@gmail.com>
>
> Newsgroups: comp.unix.sco.misc
> To: <dis...@jpr.com>
> Sent: Sunday, December 23, 2007 2:48 PM
> Subject: Re: startx fails
>
> On Dec 21, 3:52 am, Nico Kadel-Garcia <nka...@gmail.com> wrote:
> > On 20 Dec, 19:34, willjay <jim.highsm...@gmail.com> wrote
> > > Will someone please take a look at this and help me fix the fix font?
> > > OSR 5.06
> > > I get this message after trying startx at the # from the console"
> > > failed to set default font path '/usr/lib/X11/fonts/misc/,/usr/lib/X11/
> > > fonts/Speedo/,/usr/lib/X11/fonts/Type1/,/usr/lib/X11/fonts/75dpi/,/usr/
> > > lib/X11/fonts/100dpi/'
> > > Fatal server error:
> > > could not open default font 'fixed'
> > > giving up.
> > > xinit: I/O error (errno 5): unable to connect to X server
>
> > > waiting for X server to shut down .........
>
> > > xinit: X server slow to shut down, sending KILL signal.
>
> > > Help appreciated.
>
> > > wj
>
> > You're a bit short of data here. Did X *ever* work? Is this a clean
> > install, or one on which people have done lots of patches? I'm seeing
> > the results right now of a machine that's had patches and local
> > modifications randomly installed on it. If possible, you should be
> > able to rlogin or slogin into it (if you've installed OpenSSH!) and be
> > able to look at the system.- Hide quoted text -
>
> > - Show quoted text -
>
> This server has been up and working for many years, it has a
> commercial version of ssh installed and everything was working fine,
> then all of a sudden startx fails to start. *You can ssh into it and
> console text is working as well as everything else. I may not have the
> proper video drive installed.- Hide quoted text -
>
> - Show quoted text -


Brian,

I have found over the years, that you and quite a few others on this
group when you don't have the slightest clue as to the answer to a
question instead of just shutting up you spew garbage at the
question. I gave you the EXACT error message which is all I have to
give you. As usual instead of contributing you just bla bla bla.

Quite frankly if you see from my question that I have patched the
machine alot, and you are correct, I suspect that you have the answer
to my question at hand, but you choose instead just to be a jerk.

Some people just get old and NASTY away. So just shut up, and don't
respond because someone with a little more manners has already
answered my question, thank you very much.


Disgustingly
wj

I suspect all the other jerks on this group will come and respond to
take up for you but you know, all of you can just STFU

Brian K. White typed (on Sun, Dec 23, 2007 at 04:24:45PM -0500):
| I think the real question is, who cares that X doesn't work on a SCO OSR5
| box?
| OSR5's X is terrible and I can't imagine too many people used it.
| I always disabled it on all my (customers) boxes.

Just what do you judge terrible about it, Brian?

I flatter myself that I have been pretty productive over the last
decade runnning a dozen scoterms plus a browser under X-Window on OSR
5.0.[0.2.4.5.6.7] and now 6.0.0.

--
JP

Actually, I gave you all the exact things I would do myself to start
diagnosing that problem if I had ever had it.
I went through the bother of consulting a couple 5.0.5 and 5.0.6 boxes and
seeing what files are there and what exactly the man page says just so that
my response would be accurate and reasonable. For instance, maybe it would
have turned out that the man page was no help, then I would not have
expected you to have gotten any clues from it. I didn't expect anything out
of you that wasn't utterly reasonable to expect, not just in general, but
actually given your exact situation.

I'm such a jerk for spending a half hour of my time looking into your
problem for free.
Why couldn't I be nice and actually drive to your machine and fix the
problem myself instead of requiring you to do anything at all? Of course I
have no clue how to fix that problem, that's why I never posted a question
about that problem before. Of course I magically already know the answer and
am just withholding it because that is such a rewarding way to spend the day
doing that to strangers on usenet. Oh, BTW which of those two mutually
exclusive character flaws did you mean to assign to me? You said both, which
is ... ah, yeah so anyways...

Read what I said and not whatever emotional "he's being mean" crap you laid
over top of it. I was and am annoyed and so I sound it, big whup, but only
and exactly annoyed as what I said, and only and exactly for the reason I
stated. Any other thoughts or motivations are purely your own invention.

If you had ANSWERED ANY of the questions I posed, this laughable attempt at
a rebuke would have at least a shred of substance, and, based on those
answers I'd know what to suggest next, and would have done so, spending yet
more of my time looking at working boxes just out of curiosity. But, you
didn't. You just said "wahhhh meanie!"

Lastly, so, you somehow have it fixed now? Great!
Could you be bothered to drop a note here saying "fixed: it was this..." ?
That IS common courtesy towards all the people who took an interest in the
question. (which includes all the admittedly dwindling number of future
searchers with the same problem remember) As long as we're chastizing people
for not being considerate.

Brian K. White brian@aljex.com http://www.myspace.com/KEYofR
+++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!



----- Original Message -----
From: "willjay" <jim.highsmith@gmail.com>
Newsgroups: comp.unix.sco.misc
To: <distro@jpr.com>
Sent: Tuesday, December 25, 2007 10:07 AM
Subject: Re: startx fails


On Dec 23, 4:24 pm, "Brian K. White" <br...@aljex.com> wrote:
> How can you say "everything was working fine"
> and "I think I don't have the right video driver installed" in the same
> paragraph?
>
> I any event, your error message doesn't even slightly hint at a
> misconfigured video driver.
>
> There are so many obvious questions which you haven't answered, which you
> could certainly have asked and answered for yourself had you tried the
> teeniest bit. If you have at least made a reasonable try at solving this
> yourself, then where is the description of what you tried, and what you
> saw?
> Lacking those I have to assume you are guilty of asking everyone in the
> world to tie your shoes for you.
>
> For example:
> Have you looked in the paths shown in the error message?
> Are there files there?
> Do they look the same as on other, working OSR5 boxes. (names, sizes,
> dates,
> perms)
> Did you tell the customer to take the tape from the nightly backup the
> previous night and the oldest backup tape they have, and put them to the
> side and not let them get overwritten with new backups?
> Have you consulted those tapes for differences in the /usr/lib/X11 tree on
> the tape vs on the disk?
> Have you even run "man startx" ?
> "man startx" on a osr5 box points to "man Xsco" which says "Errors are
> logged in the file /usr/adm/X*msgs" which btw, you could also find without
> man's help, because on a sco osr5 box /var/adm is where many things are
> logged, and looking in that dir, X0msgs is certainly a file that looks
> like
> it has to do with X. So, have you looked to see what is in
> /usr/adm/X0msgs?
> Is there any X1msgs X2msgs ? generally there should only be one X0msgs, if
> there are others, then you are starting up multiple x servers on multiple
> consoles, which generally you don't want.
> The rest of those man pages suggest other ways to diagnose it further too,
> like running the X binary or the xinit program manually with extra options
> to show you in more detail why it's failing.
>
> If you have actually done any of that, then why didn't you say so, and say
> what you found?
>
> I think the real question is, who cares that X doesn't work on a SCO OSR5
> box?
> OSR5's X is terrible and I can't imagine too many people used it.
> I always disabled it on all my (customers) boxes.
>
> Back before apache, there was one reason to use X at the console, to
> configure the netscape http server. That hasn't been relevant in years.
>
> Brian K. White br...@aljex.com http://www.myspace.com/KEYofR
> +++++[>+++[>+++++>+++++++<<-]<-]>>+.>.+++++.+++++++.-.[>+<---]>++.
> filePro BBx Linux SCO FreeBSD #callahans Satriani Filk!
>
>
>
> ----- Original Message -----
> From: "willjay" <jim.highsm...@gmail.com>
>
> Newsgroups: comp.unix.sco.misc
> To: <dis...@jpr.com>
> Sent: Sunday, December 23, 2007 2:48 PM
> Subject: Re: startx fails
>
> On Dec 21, 3:52 am, Nico Kadel-Garcia <nka...@gmail.com> wrote:
> > On 20 Dec, 19:34, willjay <jim.highsm...@gmail.com> wrote
> > > Will someone please take a look at this and help me fix the fix font?
> > > OSR 5.06
> > > I get this message after trying startx at the # from the console"
> > > failed to set default font path
> > > '/usr/lib/X11/fonts/misc/,/usr/lib/X11/
> > > fonts/Speedo/,/usr/lib/X11/fonts/Type1/,/usr/lib/X11/fonts/75dpi/,/usr/
> > > lib/X11/fonts/100dpi/'
> > > Fatal server error:
> > > could not open default font 'fixed'
> > > giving up.
> > > xinit: I/O error (errno 5): unable to connect to X server
>
> > > waiting for X server to shut down .........
>
> > > xinit: X server slow to shut down, sending KILL signal.
>
> > > Help appreciated.
>
> > > wj
>
> > You're a bit short of data here. Did X *ever* work? Is this a clean
> > install, or one on which people have done lots of patches? I'm seeing
> > the results right now of a machine that's had patches and local
> > modifications randomly installed on it. If possible, you should be
> > able to rlogin or slogin into it (if you've installed OpenSSH!) and be
> > able to look at the system.- Hide quoted text -
>
> > - Show quoted text -
>
> This server has been up and working for many years, it has a
> commercial version of ssh installed and everything was working fine,
> then all of a sudden startx fails to start. You can ssh into it and
> console text is working as well as everything else. I may not have the
> proper video drive installed.- Hide quoted text -
>
> - Show quoted text -


Brian,

I have found over the years, that you and quite a few others on this
group when you don't have the slightest clue as to the answer to a
question instead of just shutting up you spew garbage at the
question. I gave you the EXACT error message which is all I have to
give you. As usual instead of contributing you just bla bla bla.

Quite frankly if you see from my question that I have patched the
machine alot, and you are correct, I suspect that you have the answer
to my question at hand, but you choose instead just to be a jerk.

Some people just get old and NASTY away. So just shut up, and don't
respond because someone with a little more manners has already
answered my question, thank you very much.


Disgustingly
wj

I suspect all the other jerks on this group will come and respond to
take up for you but you know, all of you can just STFU

willjay wrote (on Tue, Dec 25, 2007 at 07:07:01AM -0800):
> On Dec 23, 4:24*pm, "Brian K. White" <br...@aljex.com> wrote:
>
> Brian,
>
> I have found over the years, that you and quite a few others on this
> group when you don't have the slightest clue as to the answer to a
> question instead of just shutting up you spew garbage at the
> question. I gave you the EXACT error message which is all I have to
> give you. As usual instead of contributing you just bla bla bla.

"Have to"? "*Have to*"???

Kind sir, you seem to be confusing this NG with a paid support line.
Your receipt for payment, sir? Oh, wait, you didn't pay anything?
Then what were you expecting?

Brian did quite a lot more for you than he "had to." He gave you
several important leads, any of which could get a clueful person
to a successful outcome. Unfortunately, those who are less clueful
tend to miss the important stuff, given that Brian didn't package
his response in a paid-trouble-ticket kind of environment.

SO, in my book, Brian tried to help, and you spat on him in response.

I don't think, in the current SCO environment (shrinking mindshare,
disappearing gurus, less and less development, etc.) that it's wise
to alienate the few people that try to help, albeit somewhat
curmudgeonly. You, sir, however, know much more about EVERYTHING than
me, including manners and courtesy, so just ignore everything I've
spouted.

So, I have one more word for you:

*Plonk!*