https://bugzilla.novell.com/show_bug.cgi?id=698927 https://bugzilla.novell.com/show_bug.cgi?id=698927#c0 Summary: Batik's squiggle (xmlgraphics-batik-squiggle) crashes on startup Classification: openSUSE Product: openSUSE 11.4 Version: Final Platform: x86 OS/Version: openSUSE 11.4 Status: NEW Severity: Major Priority: P5 - None Component: Other AssignedTo: bnc-team-screening@forge.provo.novell.com ReportedBy: nvbugs@hhecht.e4ward.com QAContact: qa@suse.de Found By: --- Blocker: --- User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.9.2.17) Gecko/20110420 SUSE/3.6.17-0.2.1 Firefox/3.6.17 Squiggle crashes on startup, apparently due to two problems. The first problem appears as follows: $ xmlgraphics-batik-squiggle Exception in thread "main" java.lang.NoClassDefFoundError: org/w3c/dom/ElementTraversal at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:631) at java.lang.ClassLoader.defineClass(ClassLoader.java:615) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:306) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:301) at java.lang.ClassLoader.loadClass(ClassLoader.java:247) at org.apache.batik.dom.GenericDOMImplementation.createDocument(Unknown Source) .. This seems to be due to a faulty classpath specified in the script file. Adding xmlgraphics-batik/ext.jar and xmlgraphics-batik/xml.jar to the BASE_JARS variable in /usr/bin/xmlgraphics-batik-squiggle fixes this problem, but this just unmasks the next problem: squiggle begins to start, but crashes after displaying the splash screen with the following partial stack trace: $ xmlgraphics-batik-squiggle 2>&1 | grep -v 'access allowed' access: access denied (java.awt.AWTPermission showWindowWithoutWarningBanner) java.lang.Exception: Stack trace at java.lang.Thread.dumpStack(Thread.java:1249) at java.security.AccessControlContext.checkPermission(AccessControlContext.java:364) at java.security.AccessController.checkPermission(AccessController.java:546) at java.lang.SecurityManager.checkPermission(SecurityManager.java:532) at java.lang.SecurityManager.checkTopLevelWindow(SecurityManager.java:1327) at java.awt.Window.setWarningString(Window.java:1196) at java.awt.Window.init(Window.java:376) at java.awt.Window.<init>(Window.java:433) at java.awt.Frame.<init>(Frame.java:403) at java.awt.Frame.<init>(Frame.java:368) at javax.swing.JFrame.<init>(JFrame.java:158) at org.apache.batik.apps.svgbrowser.JSVGViewerFrame.<init>(Unknown Source) .. Note that in the above, I added -Djava.security.debug=access,failure to the startup script. It seems the problem is that 1) squiggle is running with a SecurityManager (why?); 2) it is asking for a trivial permission, and being denied; 3) it dies, rather than just catching. 3) isn't really a SuSE problem, but I think 1 and 2 might be. Batik has not had a revision since 11.3 before, where these problems did not occur, so I assume the problem is somehow related to the obvious repackaging done for 11.4 (squiggle.sh became xmlgraphics-batik-squiggle at some point...). I don't really have a good guess as to why squiggle should run with a SecurityManager. If it did so in 11.3 too (it is not easy for me to check), perhaps there is a new problem with jar signing (if the signature is invalid, then I guess the SecurityManager will be unhappy)? If not, then the obvious solution is to stop running it with the SM. I will try to take a closer look when I have access to an 11.3 install, but perhaps whoever did the repackaging for 11.4 (and apparently didn't test) has a better idea of what might have changed and how to fix it. Marking as major because the package is essentially worthless as-is. Reproducible: Always -- Configure bugmail: https://bugzilla.novell.com/userprefs.cgi?tab=email ------- You are receiving this mail because: ------- You are on the CC list for the bug.