Red Hat Bugzilla – Bug 196519
MagicPoint not updated for FC5 layout
Last modified: 2007-11-30 17:11:35 EST
Description of problem:
MagicPoint is not adjusted to layout of "modular X server" with
such result that /usr/X11R6/bin/mgp is not even in a standart path
not mentioning even such locations like /usr/X11R6/lib/X11/mgp/
instead of /usr/share/X11/mgp/ or manpages in /usr/X11R6/man/man1/
Version-Release number of selected component (if applicable):
Hi, I'm unorphaning MagicPoint / taking over as new maintainer
This is fixed in the current devel tree CVS version of the MagicPoint package,
but this cannot be build yet as it needs freetype1 which is awaiting review, if
you want to help expidite the progress of this bug, please review freetype1, see
If you want to try out the new MagicPoint you can find it and the required
freetype1 has been approved now, and a new MagicPoint with this fixed is
building as I type, closing.
> ... a new MagicPoint with this fixed is building ...
This was a while ago and on mirrors there is still the
same MagicPoint-1.11b-2.fc5 from 2005-08-05.
There are new, at least sources, for MagicPoint-1.11b-4.fc6 and
MagicPoint-1.11b-4.fc7 but nothing of that sort for FC5.
Erm FC-5 is almost EOL and this bug does not cause any functional bug, it is
merily a packaging bug. IOW I'm not going to fix this for FC-5, closing again.
> ... and this bug does not cause any functional bug
$ which mgp
/usr/bin/which: no mgp in (... long path skipped ...)
$ /usr/X11R6/bin/mgp /usr/share/doc/MagicPoint-1.11b/sample/default.mgp
Core was generated by `/usr/X11R6/bin/mgp
Program terminated with signal 11, Segmentation fault.
AFAICS that is caused by not found resources. Yes, I know that
things should be more robust than that. I also happen to know
how to work around but this is not the point (magic or not :-).
Ah, I didn't know that it was actually broken on FC-5. I've build the FC-6 /
devel version for FC-5 now too, it should show up on a mirror near you soon.
> Ah, I didn't know that it was actually broken on FC-5.
It should be possible to work around by providing suitable
symlinks - if you are knowledgable enough. But "out-of-the-box"
it does what you see.
An update did show up and now it works. Thanks!