I was running Veusz and am not sure exactly what I did but it caused the system to throw up a bug dialog.
Now Veusz is terminally brain damaged...any operation results in a bug dialog. Unfortuately, Veusz squirrels away some sort of information on the system. So deleting and reinstalling Veusz (i.e., on a mac trashing and then moving a new copy of the Veusz.app to the applications folder) doesn't help. The reinstalled version remains non functional. Note that it isn't just a particular user .vsz file that is corrupt. Veusz is non function even before it loads any user files. I noticed that the names of previously opened data files survives Veusz being deleted and reinstalled. So history is being kept in some place that survives reinstallation. This is a colossally bad idea. Only info stored in user data files should survive reinstallation. I can't locate the file (it might be a .plist file with a generic name instead of a Veusz name? Tell me that you don't actually modify an existing non Veusz system file!!!). I guess this computer can never never ever ever run Veusz again!!! If there is a fix it would be nice to know about it I strongly suggest that you change the way you do this so that no bugs can be become viruses (i.e., no bug crashing the system can change the behavior of subsequent runs of the system). If you need/want to store history store it where it will be deleted when the app is deleted. -- Fahiem Bacchus Professor of Computer Science University of Toronto
_______________________________________________ Veusz-discuss mailing list [email protected] https://mail.gna.org/listinfo/veusz-discuss
