I updated my fedora 18 64 bits last night. Since this update (I saw an update of swt in the list of updates), tuxguitar doesn't start anymore. When I start it via command line, I've got the following error message: tuxguitar Exception in thread "main" java.lang.NoClassDefFoundError: org/eclipse/swt/widgets/Control at org.herac.tuxguitar.gui.TGMain.main(TGMain.java:6) Caused by: java.lang.ClassNotFoundException: org.eclipse.swt.widgets.Control at java.net.URLClassLoader$1.run(URLClassLoader.java:366) at java.net.URLClassLoader$1.run(URLClassLoader.java:355) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:354) at java.lang.ClassLoader.loadClass(ClassLoader.java:423) at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:308) at java.lang.ClassLoader.loadClass(ClassLoader.java:356) Best regards, YC
Thanks for the report. This is due to a change in the eclipse-swt package: http://pkgs.fedoraproject.org/cgit/eclipse.git/commit/?h=f18&id=12661d4bfef3dccd6ba3efeebd0c9e2185fd9308 I talked to the Eclipse maintainers and they say that they were changing the jar file symlink location for the future Fedora releases and they accidentally modified it for Fedora 18. I am just adjusting to the new convention so that we don't need to deal with this again by the time Fedora 19 is released. I'm firing a build now. Stay tuned.
tuxguitar-1.2-12.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/tuxguitar-1.2-12.fc18
Package tuxguitar-1.2-12.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing tuxguitar-1.2-12.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-4127/tuxguitar-1.2-12.fc18 then log in and leave karma (feedback).
tuxguitar-1.2-12.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report.