bogus font values are being returned

Hi wildfire,

Thanks for including an image to demonstrate the issue. Could you also please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log or Xorg.0.log.old file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

lspci -vvnn attached

Xorg.0.log attached

xorg.conf attached

May be related to #345189 ??

information was provided, setting this to confirmed, thanks.

[This is an automatic notification.]

Hi Anand,

This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?

Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
normal support channels, please see:

    http://www.ubuntu.com/support

If you are the original reporter and can still reproduce the issue on
Lucid, please run the following command to refresh the report:

  apport-collect 346793

If you are not the original reporter, please file a new bug report, so
we can work with you as the original reporter instead (you can reference
bug 346793 in your report if you think it may be related):

  ubuntu-bug xorg

If by chance you can no longer reproduce the issue on Lucid or if you
feel it is no longer relevant, please mark the bug report 'Fix Released'
or 'Invalid' as appropriate, at the following URL:

  https://bugs.launchpad.net/ubuntu/+bug/346793

Hi Bryce,

Ah. What timing.

The answer is - yes I could reproduce it. But I literally, and I mean about 30 minutes ago, just wiped the machine to try a fresh install of 10.04 in case it was something that had occurred due to a local font install and/or configuration issue.

With a default 10.04 LTS (well, as default as one can have when running on i8XX chipset) I do not see the problem.

So it was either a local font issue, or a local configuration issue. Which one it was, is, unfortunately, not something I can say anymore.

Thanks,
Anand