Red Hat Bugzilla – Bug 478489
Unison213 fails with message "Uncaught exception Gpointer.Null" (missing dependency)
Last modified: 2009-01-29 18:07:03 EST
Description of problem:Using Unison213 in gui mode give a fatal error:
"Uncaught exception Gpointer.Null"
This is caused by a missing dependency: font-schumacher-misc (which does not seem to be available as a fc10 package)
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. run unison213 in gui mode (the default) with an existing .prf file
fatal error described above
Unison window should open.
This is a missing dependency: If one installs font-schumacher-misc-1.0.0.tar.gz
the the problem is resolved.
I have tested this problem and fix in fc10 x86_64 with unison213. It is probably also a problem for other platforms. Possibly also for unison227 (which I don't use).
That doesn't make a lot of sense; why would unison suddenly start requiring this font that it never has before? I run it in gui mode (under F9 32-bit anyway) all the time and it doesn't need that....
I'm running unison213 on several fc9 machines with no problem. But the fc9 installs the schumacher fonts in the package xorg-x11-fonts-misc.
The problem appeared in a fresh install of fc10 on a new machine. I googled for a solution and found the font-schumacher solution. I discovered that fc10 does not install the fonts by default. Installing them fixed the problem.
Google for: font-schumacher unison and you will find many references.
That makes more sense. I'll look into why the font went away...
I checked the content of RPM xorg-x11-fonts-misc on both F9 and F10. They are identical. The rpm .spec file doesn't have any relevant changes. Also, the .spec file does contain:
and this appears to be used (I certainly see compiled versions of the sources in that file in the RPM for both F9 and F10)
Something else must be going on here...
Finally, running either unison-2.13 or unison-2.27 on F10 32-bit displays a GUI for me just fine.
Right -- stupid of me. xorg-x11-fonts-misc was not installed by the default F10 installation and I didn't notice. It should be a dependency for unison and that should fix the problem.
Great. That's an easy fix! Thanks.
unison213-2.13.16-12.fc10,unison227-2.27.57-10.fc10 has been submitted as an update for Fedora 10.
unison213-2.13.16-12.fc10, unison227-2.27.57-10.fc10 has been pushed to the Fedora 10 testing repository. If problems still persist, please make note of it in this bug report.
If you want to test the update, you can install it with
su -c 'yum --enablerepo=updates-testing update unison213 unison227'. You can provide feedback for this update here: http://admin.fedoraproject.org/updates/F10/FEDORA-2009-0439
unison213-2.13.16-12.fc10, unison227-2.27.57-10.fc10 has been pushed to the Fedora 10 stable repository. If problems still persist, please make note of it in this bug report.