[KLUG Members] gnumeric problem

[Adam Williams]

>Sage Adam Williams and his friend RoseMary wrote:
>>>I assume gnome-print is installed?  gnumeric uses gnome-print to
>>enumerate fonts,  it might be worth doing a force re-install of that
>>package.
>gnome-print WAS installed (I had checked it earlier) but --replacepkgs
>forced a new loading after which gnumeric HAD all the fonts I could hope
>for.  Sage indeed.

With GNOME,  sometimes packages are very inter-dependent.  Installation
order can be important, especially when upgrading a VERY old distribution.

>>Use "xlsfonts" on the command
>>line to see what fonts are available to the X server.  "gfontsel" lets
>>you browse the available fonts.
>Wonderful commands about which I had never heard... where does one learn
>of such apparently esoteric tools?

"X Windows System Users Guide", O'Reilly

There is xfontsel as well,  but I always shop for a GNOME replacement.
The old utilities get lost on things like TTF, and are all extemely ugly.
GEOS on the C-64 had better looking widgets than pre-Linux X.  They are
just so incredibly hideous.....

>>The USB port thing is interesting,  but I think a red herring.  That is
>>probably too many levels down to generate an error in producing output
>>from gnumeric.  Gnumeric should still produce the print job and pass it
>>to lpd,  and if the hardware level is munged you'd see the print job
>>sitting there with "lpq"
>lpq had given an error message before - normal now!

Fixing lo probably fixed this.

>>>since I have an ancient system and take care of ifconfig showing no lo, as
>>>well as the printing and gnumeric problems.
>>No lo?!  That should break lots of things.
>This may take care of many problems.
>>Does /etc/sysconfig/network-scripts/ifcfg-lo exists?
>Yes, but only as one line:
>BOOTPROTO=none
>>If not create it with the following content -
>>DEVICE=lo
>>IPADDR=127.0.0.1
>>NETMASK=255.0.0.0
>>NETWORK=127.0.0.0
>># If you're having problems with gated making 127.0.0.0/8 a martian,
>># you can change this to something else (255.255.255.255, for example)
>>BROADCAST=127.255.255.255
>>ONBOOT=yes
>>NAME=loopback
>BINGO!  after ifup lo, lo now shows up AND the printer works!!!
>>Then do "/etc/sysconfig/network-scripts/ifup lo" and see what happens.
>>Networking is enabled for your run level?  Do you have any other network
>>interfaces up?  Does NETWORKING=yes in /etc/sysconfig/network?
>Yes, it does, despite my belonging to no network other than the
>internet.

NETWORKING always need to be on,  it has nothing to do with being on a
"network".

>I believe this is the result of my having compiled NFS into my kernel in
>my RH6.2.  How do I fix that - a recompile of the kernel?

I doubt a kernel compile would cause this (the whacked lo that is).  That
is most likely caused by either a fouled package upgrade (and we have
other evidence this may have happened) or else control-panel foo-barr-ed
(which I have seen happen).

As for the USB thing,  if everything works I would just ignore it.  Next
time you recompile just make sure USB is disabled.

-- 
-----------------------------------------------------------
Ximian GNOME, Evolution, LTSP, and RedHat Linux + LVM & XFS
-----------------------------------------------------------