[edgy, libmagick] any display command (shell w/o additional arguments, magickcore, magick++ etc) fails because of missing fonts making especially c/c++ API's useless as one cannot change settings there

[solution found] The below happens only when updating from previous Ubuntu versions keeping your xorg.conf unchanged. After updating to Edgy, my xorg.conf's "Files" section carried FontPath's to /usr/share/X11/fonts/... whereas on Edgy fonts are in /usr/share/fonts (thus in /usr/share/fonts/X11/...). Correcting xorg.conf solved the problem! Still -- somehow for those updating from Dapper to Edgy it is not obvious that xorg.conf must be changed!

I am developing some R (r-cran in ubuntu) language package using Magick++ interface. Since updating to Edgy I could not use any of display functions of MagickCore, Magick++, MagickWand because all of them fail on the same error throwing me out of the program: display
display: unable to load font `-*-helvetica-medium-r-normal--12-*-*-*-*-*-iso8859-1'.
The above message was generated on the command line using shell display, but it is exactly the same in all API's (well, Magick++ and MagickWand use DisplayImages of MagickCore directly). In the shell one can override the settings by using 'display -font fixed *', which works. In the API's setting image.font("fixed") or similar does not affect the result at all. I tried different versions, repositories, of libmagick (plus all other files) -- dapper, dapper-security, edgy but all on Edgy Ubuntu -- all fail with the same error, but all of them are 6.2.4.5 versions. Similar problem was reported on debian stable 6.0.6. I ended up killing the precompiled binaries and installing ImageMagick6.2.9 from source from their original site -- this solved the problem. Thus it does not look like and inherent Edgy problem, but rather the way the package was compiled (dependencies?). In any case, installation from source works w/o any issues.

Well, if you forget about my particular problem and think of server applications, ImageMagick is a must, so I would consider this problem as very high priority!

Note: the original reporter indicated the bug was in package 'libmagick'; however, that package was not published in Ubuntu.