Reproduce: 1) Start freemind from console 2) Use *any* map (a simple one with only one node is enough) 3) In the menu select File -> Export -> as PDF and put some filename into the dialog 4) No PDF will be written, but error messages in the console: STDERR: Exception in thread "AWT-EventQueue-0" STDERR: java.lang.NoClassDefFoundError: org/apache/avalon/framework/configuration/Configurable avalon-framework is installed, thus the error must be deeper inside the program.
Solution: The following jars need to be on the classpath to allow all exports to work: avalon-framework commons-logging.jar xmlgraphics-commons commons-io dom batik-all xml-commons-jaxp-1.3-apis-ext This can simply be added to $BASE_JARS in /usr/bin/freemind. (NB: Some other error messages still remain, but they are worth a different report.)
Keywords: (none) => PATCHTarget Milestone: --- => Mageia 2Summary: freemind fail on most exports: NoClassDefFoundError: org/apache/avalon/framework/configuration/Configurable => freemind fails on most exports: NoClassDefFoundError: org/apache/avalon/framework/configuration/Configurable
Created attachment 826 [details] patch adding require modules to classpath
Assigning to maintainer
CC: (none) => stormiAssignee: bugsquad => andre999
CC: (none) => andre999mga
Sorry, I should have indicated that I was working on it. The patch doesn't work on my system. My set-up is the default, except for the language and the default font + size. But it did create an empty .pdf file, which did not occur before the patch. The first 3 lines of output (to console) are: /usr/bin/build-classpath: error: Could not find dom Java extension for this JVM /usr/bin/build-classpath: error: Could not find xml-commons-jaxp-1.3-apis-ext Java extension for this JVM /usr/bin/build-classpath: error: Some specified jars were not found Followed by lots of typical jvm output which occured without the patch. I'll try looking through the class files to see what .jar files I think it should be including. Note that in my install, the following links are broken: /usr/share/lib/jarbundler-2.0.0.jar /usr/share/lib/jibx/bcel.jar /usr/share/lib/jibx/jaxme-js-0.3.jar Maybe that is part of the problem. I'll look at that too.
Assignee: andre999 => andre999mga
Created attachment 1006 [details] Patch to add missing classpaths @ Harmut Sorry for the delay. I got it working for me. Note that I added "xml-commons-apis-ext" in place of 2 others in your patch. Also note that your diff seems to have been made to an older version of freemind. Could you test this patch to see if it works for you ?
Status: NEW => ASSIGNED
@Andre: You patch allows creating a PDF using freemind-0.9.0-2.mga1. But there are still errors: 1) Error on startup: FATAL: An exception occured: java.lang.ClassNotFoundException: plugins.script.ScriptingRegistration 2) When exporting: Masses of font-problems. This seams to simply be a missing feature in the java classes. FATAL: Unable to load font file: file:/usr/local/share/fonts/type1/Bitstream/Futura/0138A___.pfb. Reason: Support for 'StartTrackKern' has not been implemented, yet! Font is not supported. 3) Garbage at the end: STDOUT: resolve data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABAAAAAPCAYAAADtc08vAAACYUlEQVR42mNkIBI0 ... more base64 data ..
This message is a reminder that Mageia 1 is nearing its end of life. In approximately 25 days from now, Mageia will stop maintaining and issuing updates for Mageia 1. At that time this bug will be closed as WONTFIX (EOL) if it remains open with a Mageia 'version' of '1'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Mageia version prior to Mageia 1's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Mageia 1 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Mageia, you are encouraged to click on "Version" and change it against that version of Mageia. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Mageia release includes newer upstream software that fixes bugs or makes them obsolete. -- Mageia Bugsquad
This bug no longer exists in Mageia 2.
Status: ASSIGNED => RESOLVEDResolution: (none) => WORKSFORME