To replicate bug, start Gnumeric without a file, enter characters in a cell
(I used "ab"), then try and change font to Bitstream Charter.  Gnumeric
crashs and the following is left on the screen:

% gnumeric
Message: Successfully registered `OAFIID:GNOME_Gnumeric_GridFactory'
Gdk-ERROR **: BadValue (integer parameter out of range for operation)
  serial 7495 error_code 2 request_code 45 minor_code 0
Gdk-ERROR **: BadFont (invalid Font parameter)
  serial 7496 error_code 7 request_code 47 minor_code 0

You wrote:

I am unable to reproduce this problem on a system with identical library
setup (except for having libesd-alsa0 rather than libesd0 installed).

Can you provide the files in your /etc/gnome/fonts directory?

TIA,
Ray

You wrote:

I am unable to reproduce this problem on a system with identical library
setup (except for having libesd-alsa0 rather than libesd0 installed).

Can you provide the files in your /etc/gnome/fonts directory?

TIA,
Ray

Thank you for the additional information you have supplied regarding
this problem report.  It has been forwarded to the developer(s) and
to the developers mailing list to accompany the original report.

Your message has been sent to the package maintainer(s):
 Vincent Renardias <vincent@debian.org>

If you wish to continue to submit further information on your problem,
please send it to 117430@bugs.debian.org, as before.

Please do not reply to the address at the top of this message,
unless you wish to report a problem with the Bug-tracking system.

Darren Benham
(administrator, Debian Bugs database)

Ray,

Per your request, I've attached is a tarball with the files from my
/etc/gnome/fonts directory.

Jim
    ------------------- Optional Methods -----------------------
Dr James A. Lupo                          (303) 423-2652
9667 Independence Dr.                     lupoja@qwest.net
Westminster  CO  80021-6845               jalupo@regis.edu

Ray,

Per your request, I've attached is a tarball with the files from my
/etc/gnome/fonts directory.

Jim
    ------------------- Optional Methods -----------------------
Dr James A. Lupo                          (303) 423-2652
9667 Independence Dr.                     lupoja@qwest.net
Westminster  CO  80021-6845               jalupo@regis.edu

Hi Jim,

Hmm... the only one referring to Charter is the gnome-print-x11 one, which
is identical to mine (except for timestamps).

I have to admit that gnumeric's font handling is one of its deeper mysteries
for me. Is there any other font with which you cou can trigger the problem
on your system?

Ray

Ray,

I worked through the list of fonts presented by Gnumeric, and
"Bitstream Charter" is the only one that fails.  I've done some
experimenting with various font selectors to see how they respond to
selecting the font, and was able to elicit the same type of error:

   % gfontsel
   Gdk-ERROR **: BadValue (integer parameter out of range for operation)
     serial 2098 error_code 2 request_code 45 minor_code 0
   Gdk-ERROR **: BadFont (invalid Font parameter)
     serial 2099 error_code 7 request_code 47 minor_code 0

   % gtkfontsel
   Gdk-ERROR **: BadValue (integer parameter out of range for operation)
     serial 1701 error_code 2 request_code 45 minor_code 0
   Gdk-ERROR **: BadFont (invalid Font parameter)
     serial 1702 error_code 7 request_code 47 minor_code 0

   % xfontsel
   X Error of failed request:  BadValue (integer parameter out of range \
           for operation)
     Major opcode of failed request:  45 (X_OpenFont)
     Value in failed request:  0x440004b
     Serial number of failed request:  1219
     Current serial number in output stream:  1220

Make me wonder if the files that specify "Bitstream Charter" are
munged.  Its clearly not just a Gnumeric problem!  All the xfonts-*
packages were included in the "unstable" updates I completed
downloading Saturday morning.  Gnumeric was completely broken at that
point, but was fixed with updates I downloaded just after midnight.

That's the most likely explanation (although it could e.g. be caused as well
by a not-restarted or corrupted X font server).

That's a relief for me :-)

A bit of hackery (dpkg -S `grep -hri charter /etc/X11/fonts | sed -e s'/ .*$//' | xargs locate -- `)
suggests that all Bitstream Charter fonts (both in the Speedo and the
PostScript format) are from the `xfonts-scalable' package. You could try if
your problem goes away when you fetch that package from a mirror, verify its
MD5 checksum (b62bc20685d28a0ef9bf97d2cc9ca458 for
xfonts-scalable_4.1.0-9_all.deb) and install it with "dpkg -i".

HTH,
Ray

Reinstalled the xfonts-scalable_4.1.0-9.deb (MD5 checksum matches),
and the problem still exists.  I'm puzzled by why the font selectors show
"bitstream charter" and "charter".  The full name of the "charter" entry
is:

   -bitstream-charter-medium-r-normal-*-*-140-*-*-p-*-iso8859-9

The "charter" entry is just the "family" name.  Why "bitstream charter"
shows "foundary" and "family" is a mystery and is probably the cause
of the problems.  When I use xfontsel, and set foundary to "bitstream",
it activates "bitstream charter", "charter", "courier" and "terminal" in
the families selection listing.  That doesn't seem right at all.

Ray,

Identified the problem.  Fonts from the Debian "gsfonts-other" package
include four that generate the following entries in the "fonts.dir" file:

  bchb.pfa -bitstream-bitstream charter-bold-r-normal--0-0-0-0-p-0-iso8859-1
  bchbi.pfa -bitstream-bitstream charter-bold-i-normal--0-0-0-0-p-0-iso8859-1
  bchr.pfa -bitstream-bitstream charter-medium-r-normal--0-0-0-0-p-0-iso8859-1
  bchri.pfa -bitstream-bitstream charter-medium-i-normal--0-0-0-0-p-0-iso8859-1

By manually changing them to the proper "-bitstream-charter-*" form, the
problems I noted with Gnumeric and all the font selectors go away!

Sorry to have bothered the Gnumeric list with this, but I couldn't figure
out where to get started on the problem.

reassign 117430 gsfonts-other
thanks

Good to hear.

That's strange. I don't understand why this fixes the problem. AFAICT it's
not caused by the spaces in the font name (there are quite a few fonts that
have that), nor by having the foundry name duplicated in the font name (some
urw fonts have that as well).

No problem. The trick now is to find out how to proceed. Torsten, could you
please check if there is anything strange about the bitstream charter font
files? If there isn't, my best guess is we're running into a weird problem
with gnome-print.

Ray