After installing the latest FC5 kernel(2.6.16-1.2122_FC5) and versions of the compiler(gcj (GCC) 4.1.1 20060525 (Red Hat 4.1.1-1)) and doing a fresh checkout, frysk aborts right out of the box when I try to activate it. Here is the traceback: java.lang.NoSuchMethodException: <init> at java.lang.Class.getConstructor(libgcj.so.7) at frysk.gui.monitor.ObjectFactory.getObject(FryskGui) at frysk.gui.monitor.ObjectFactory.loadObject(FryskGui) at frysk.gui.monitor.ObservableLinkedList.load(FryskGui) at frysk.gui.monitor.LiaisonPoint.load(FryskGui) at frysk.gui.monitor.observers.ObserverRoot.load(FryskGui) at frysk.gui.monitor.ObjectFactory.loadObject(FryskGui) at frysk.gui.monitor.observers.ObserverManager.loadObservers(FryskGui) at frysk.gui.monitor.observers.ObserverManager.<clinit>(FryskGui) at java.lang.Class.initializeClass(libgcj.so.7) at frysk.gui.monitor.CustomObserverDialog.<init>(FryskGui) at frysk.gui.monitor.WindowManager.initLegacyProcpopWindows(FryskGui) at frysk.gui.Gui.<init>(FryskGui) at frysk.gui.Gui.gui(FryskGui) at frysk.gui.FryskGui.main(FryskGui) frysk.gui.monitor.observers.ObserverManager@f50dc8: ObserverManager.loadObservers() Exception while loading Exit_Notifiction_Observer java.lang.NullPointerException at frysk.gui.monitor.ObjectFactory.loadObject(FryskGui) at frysk.gui.monitor.ObservableLinkedList.load(FryskGui) at frysk.gui.monitor.LiaisonPoint.load(FryskGui) at frysk.gui.monitor.observers.ObserverRoot.load(FryskGui) at frysk.gui.monitor.ObjectFactory.loadObject(FryskGui) at frysk.gui.monitor.observers.ObserverManager.loadObservers(FryskGui) at frysk.gui.monitor.observers.ObserverManager.<clinit>(FryskGui) at java.lang.Class.initializeClass(libgcj.so.7) at frysk.gui.monitor.CustomObserverDialog.<init>(FryskGui) at frysk.gui.monitor.WindowManager.initLegacyProcpopWindows(FryskGui) at frysk.gui.Gui.<init>(FryskGui) at frysk.gui.Gui.gui(FryskGui) at frysk.gui.FryskGui.main(FryskGui) Exception in thread "main" java.lang.ExceptionInInitializerError at java.lang.Class.initializeClass(libgcj.so.7) at frysk.gui.monitor.CustomObserverDialog.<init>(FryskGui) at frysk.gui.monitor.WindowManager.initLegacyProcpopWindows(FryskGui) at frysk.gui.Gui.<init>(FryskGui) at frysk.gui.Gui.gui(FryskGui) at frysk.gui.FryskGui.main(FryskGui) Caused by: java.lang.NullPointerException at frysk.gui.monitor.UniqueHashMap.add(FryskGui) at frysk.gui.monitor.observers.ObserverManager.addTaskObserverPrototype(FryskGui) at frysk.gui.monitor.observers.ObserverManager.loadObservers(FryskGui) at frysk.gui.monitor.observers.ObserverManager.<clinit>(FryskGui) at java.lang.Class.initializeClass(libgcj.so.7) ...5 more
Hmmm, ok, commenting out the "print" stmts in frysk.gui.monitor.ObjectFactory.getObject I get this output before the stacktrace(I modded the "print stmts so I could tell which one was which): =========================================== 1st ObjectFactory.getObject() frysk.gui.monitor.observers.ExitNotificationObserver 3 rd ObjectFactory.getObject() class frysk.gui.monitor.observers.ExitNotificationObserver =========================================== =========================================== 1st ObjectFactory.getObject() frysk.gui.monitor.StatusWidget$TimelineAction 2nd ObjectFactory.getObject() frysk.gui.monitor.StatusWidget$TimelineAction Looks like the blowup has something to do with "StatusWidget$TimelineAction" since the last line above is inside a "try/catch" block.
Well, after deleting ~/.frysk and restarting frysk all appears to work ok. Just be forewarned that some problem was introduced between versions here that caused this. Evidently there was some incompatibility introduced somewhere about this.