Aaron Spike wrote:
Benjamin Huot wrote:
I didn't mean to put down autopackage. I just didn't want others to encounter the same problems.
As I said, the best way to prevent other people encountering this problem is to report it and work to repair it.
It is still early in development at this point, as far as I can tell. I am used to the stability of OS X, where nothing has crashed my system for over 2 years. I don't think a program should crash X-Windows and I do not want to risk losing data do to instability. Yes, I make frequent and multiple offsite backups of different kinds, but I don't want to lose any of my copies. If I could install from the command line, I would, as I think the gui is what has the problems, but I didn't see a way to install via the command line (meaning without a gui).
To install from the command line: bash inkscape*.package --prefix=/where/you/want/to/install
Now to be fair if a program can crash X windows, would be inclined to say there is a bug in X windows.
Aaron Spike
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
That sounds right - it probably is an X-windows problem - probably in one of the many updates Ubuntu told me to upgrade my machine with.
Now does the command line command launch a X-windows dialog, or does it just stay text only in the terminal? It wasn't clear from the autopackage website.