I installed .44pre4 by Autopackage on Ubuntu 6.06 Dapper Drake under KDE with the latest security and stability including kernel updates. When I chose manage 3rd party applications and remove Inkscape like I did for .44pre3, my computer locked up on me and I had to do a hard reboot. After rebooting, I checked then and it no longer appeared in the list under 3rd party applications. Then I changed the .package file to make it executable and then double clicked on it. My screen locked up temporarily as it spent several minutes initializing. Then my dock disappeared. I saw it said it was installing various components and then it said it was done. My dock was still gone! Luckily I was able to log out by right clicking on the desktop. I logged back in, launched Inkscape and it seems to work fine. That is the last time I use Autopackage!!!
Benjamin Huot wrote:
I installed .44pre4 by Autopackage on Ubuntu 6.06 Dapper Drake under KDE with the latest security and stability including kernel updates. When I chose manage 3rd party applications and remove Inkscape like I did for .44pre3, my computer locked up on me and I had to do a hard reboot. After rebooting, I checked then and it no longer appeared in the list under 3rd party applications. Then I changed the .package file to make it executable and then double clicked on it. My screen locked up temporarily as it spent several minutes initializing. Then my dock disappeared. I saw it said it was installing various components and then it said it was done. My dock was still gone! Luckily I was able to log out by right clicking on the desktop. I logged back in, launched Inkscape and it seems to work fine. That is the last time I use Autopackage!!!
Certainly your choice and I can respect that. But it would be very helpful to everyone, if you would report your troubles to the autopackage developers and work with them to find a solution.
It amazes me that tons of people will report bug after bug to Inkscape, but very often people chuck autopackage after the first glitch and decide never to use it again. And worse they often speak out loudly against it. IMHO, if you have a problem and fail to report it you are to blame for the problems of the next person.
Let's work together to build up the free software community as a whole.
Aaron Spike
Aaron Spike wrote:
Benjamin Huot wrote:
I installed .44pre4 by Autopackage on Ubuntu 6.06 Dapper Drake under KDE with the latest security and stability including kernel updates. When I chose manage 3rd party applications and remove Inkscape like I did for .44pre3, my computer locked up on me and I had to do a hard reboot. After rebooting, I checked then and it no longer appeared in the list under 3rd party applications. Then I changed the .package file to make it executable and then double clicked on it. My screen locked up temporarily as it spent several minutes initializing. Then my dock disappeared. I saw it said it was installing various components and then it said it was done. My dock was still gone! Luckily I was able to log out by right clicking on the desktop. I logged back in, launched Inkscape and it seems to work fine. That is the last time I use Autopackage!!!
Certainly your choice and I can respect that. But it would be very helpful to everyone, if you would report your troubles to the autopackage developers and work with them to find a solution.
It amazes me that tons of people will report bug after bug to Inkscape, but very often people chuck autopackage after the first glitch and decide never to use it again. And worse they often speak out loudly against it. IMHO, if you have a problem and fail to report it you are to blame for the problems of the next person.
Let's work together to build up the free software community as a whole.
Aaron Spike
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
I didn't mean to put down autopackage. I just didn't want others to encounter the same problems.
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).
I will certainly report it to autopackage. I thought the problem was that the Inkscape servers were overtaken by the hordes of eager testers :-)
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
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.
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.
I suggest that you not give up using autopackage.
Well should I no longer use gedit, because I know a way how this program can crash the whole x-server?
https://launchpad.net/distros/ubuntu/+source/xserver-xorg/+bug/47122/+index
Maybe you are able to reproduce it too. It would be nice if you try to reproduce it.
Florian Köberle wrote:
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.
I suggest that you not give up using autopackage.
Well should I no longer use gedit, because I know a way how this program can crash the whole x-server?
https://launchpad.net/distros/ubuntu/+source/xserver-xorg/+bug/47122/+index
Maybe you are able to reproduce it too. It would be nice if you try to reproduce it.
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
I am in the process of troubleshooting it with the developer's guidance.
http://autopackage.org/forums/viewtopic.php?p=1619#1619 also under "autopackage crashes kde" from the main menu
On Sun, Jun 18, 2006 at 10:55:55AM -0700, Benjamin Huot wrote:
Florian K?berle wrote:
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.
I suggest that you not give up using autopackage.
Well should I no longer use gedit, because I know a way how this program can crash the whole x-server?
https://launchpad.net/distros/ubuntu/+source/xserver-xorg/+bug/47122/+index
Maybe you are able to reproduce it too. It would be nice if you try to reproduce it.
I am in the process of troubleshooting it with the developer's guidance.
http://autopackage.org/forums/viewtopic.php?p=1619#1619 also under "autopackage crashes kde" from the main menu
Thanks for doing this! Looks like you've verified that the issue goes away with the new Autopackage 1.0.10?
Bryce
Bryce Harrington wrote:
On Sun, Jun 18, 2006 at 10:55:55AM -0700, Benjamin Huot wrote:
Florian K?berle wrote:
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.
I suggest that you not give up using autopackage.
Well should I no longer use gedit, because I know a way how this program can crash the whole x-server?
https://launchpad.net/distros/ubuntu/+source/xserver-xorg/+bug/47122/+index
Maybe you are able to reproduce it too. It would be nice if you try to reproduce it.
I am in the process of troubleshooting it with the developer's guidance.
http://autopackage.org/forums/viewtopic.php?p=1619#1619 also under "autopackage crashes kde" from the main menu
Thanks for doing this! Looks like you've verified that the issue goes away with the new Autopackage 1.0.10?
Bryce
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
It looks like that to me, but I don't know anything about programming. I would like for the developer to know what caused the problem, so it isn't reintroduced later on. Maybe this as far as I can help just being a user, but if I could pinpoint the issue more precisely I will continue the troubleshooting.
On Sun, Jun 18, 2006 at 11:30:13AM -0700, Benjamin Huot wrote:
Bryce Harrington wrote:
http://autopackage.org/forums/viewtopic.php?p=1619#1619 also under "autopackage crashes kde" from the main menu
Thanks for doing this! Looks like you've verified that the issue goes away with the new Autopackage 1.0.10?
It looks like that to me, but I don't know anything about programming. I would like for the developer to know what caused the problem, so it isn't reintroduced later on. Maybe this as far as I can help just being a user, but if I could pinpoint the issue more precisely I will continue the troubleshooting.
Yes, it would be best if the developer can determine the root cause, although sometimes that can be tricky. One thing you could do is offer to be willing to try out any experimental versions of autopackage over the next month or so, to help them pinpoint it. If nothing else, if you could simply try out each inkscape autopackage release on your system, then at least you'd be able to catch this regression if it occurs again.
Bryce
On Sat, Jun 17, 2006 at 10:08:49PM -0500, 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.
Just to emphasize what Aaron has said - our Inkscape community has a long history of cooperating with the Autopackage developers. Indeed, we were one of the first applications that autopackage supported. In turn, the Autopackage project supported Inkscape when we were very young and new, before we'd been taken up by any of the distros. Autopackage helped a *lot* of users get over a huge range of installation hiccups, and thus has contributed greatly to its success (and helped boost autopackage's success in turn.)
So by nature, us Inkscapers come from a long history of working to help Autopackage by testing and reporting bugs. It's a part of our culture and something we need to pass along to all new Inkscapers.
Bryce
Bryce Harrington wrote:
On Sat, Jun 17, 2006 at 10:08:49PM -0500, 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.
Just to emphasize what Aaron has said - our Inkscape community has a long history of cooperating with the Autopackage developers. Indeed, we were one of the first applications that autopackage supported. In turn, the Autopackage project supported Inkscape when we were very young and new, before we'd been taken up by any of the distros. Autopackage helped a *lot* of users get over a huge range of installation hiccups, and thus has contributed greatly to its success (and helped boost autopackage's success in turn.)
So by nature, us Inkscapers come from a long history of working to help Autopackage by testing and reporting bugs. It's a part of our culture and something we need to pass along to all new Inkscapers.
Bryce
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
thanks for explaining the connection
Hi Benjamin,
Your symptoms sound a *lot* like one of the following:
- Imminent hardware failure; most likely memory or cpu - Driver/kernel problem - Overheating
Autopackage cannot by itself cause a hard lock or random applications to crash (which is what happened when your dock disappeared).
Also you are the only person who has reported this as a problem. If you can show that it is indeed autopackage which causes the problem then we shall debug this further. The 1.0.10 release did not contain any changes that could have affected this problem ....
thanks -mike
Mike Hearn wrote:
Hi Benjamin,
Your symptoms sound a *lot* like one of the following:
- Imminent hardware failure; most likely memory or cpu
- Driver/kernel problem
- Overheating
Autopackage cannot by itself cause a hard lock or random applications to crash (which is what happened when your dock disappeared).
Also you are the only person who has reported this as a problem. If you can show that it is indeed autopackage which causes the problem then we shall debug this further. The 1.0.10 release did not contain any changes that could have affected this problem ....
thanks -mike
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
It definitely could have been kernel related as I have just upgraded the kernel as Adept notified me of a whole bunch of Ubuntu updates including several kernel ones and I accepted all the updates. I already had to reinstall and compile Vmware.
Benjamin Huot wrote:
Mike Hearn wrote:
Hi Benjamin,
Your symptoms sound a *lot* like one of the following:
- Imminent hardware failure; most likely memory or cpu
- Driver/kernel problem
- Overheating
Autopackage cannot by itself cause a hard lock or random applications to crash (which is what happened when your dock disappeared).
Also you are the only person who has reported this as a problem. If you can show that it is indeed autopackage which causes the problem then we shall debug this further. The 1.0.10 release did not contain any changes that could have affected this problem ....
thanks -mike
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
It definitely could have been kernel related as I have just upgraded the kernel as Adept notified me of a whole bunch of Ubuntu updates including several kernel ones and I accepted all the updates. I already had to reinstall and compile Vmware.
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
Are you a programmer? of Autopackage? because I have not had any other crashes of anything.
Benjamin Huot wrote:
Benjamin Huot wrote:
Mike Hearn wrote:
Hi Benjamin,
Your symptoms sound a *lot* like one of the following:
- Imminent hardware failure; most likely memory or cpu
- Driver/kernel problem
- Overheating
Autopackage cannot by itself cause a hard lock or random applications to crash (which is what happened when your dock disappeared).
Also you are the only person who has reported this as a problem. If you can show that it is indeed autopackage which causes the problem then we shall debug this further. The 1.0.10 release did not contain any changes that could have affected this problem ....
thanks -mike
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
It definitely could have been kernel related as I have just upgraded the kernel as Adept notified me of a whole bunch of Ubuntu updates including several kernel ones and I accepted all the updates. I already had to reinstall and compile Vmware.
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
Are you a programmer? of Autopackage? because I have not had any other crashes of anything.
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
got my answer from your homepage
"I am employed part-time as a developer for CodeWeavers, Inc http://www.codeweavers.com/, where I work on the Windows emulation subsystem http://winehq.com/ of Linux.
I am also the lead designer and maintainer of autopackage http://autopackage.org/, a distribution neutral mechanism for packaging Linux software."
On Sun, 18 Jun 2006 16:59:20 -0700, Benjamin Huot wrote:
Are you a programmer? of Autopackage? because I have not had any other crashes of anything.
I am, yes. Because it doesn't crash with other things doesn't necessarily mean it's a fault in autopackage, though this is rather suspicious. The problem has disappeared for you now though? So maybe it was a random spurious failure.
thanks -mike
Mike Hearn wrote:
On Sun, 18 Jun 2006 16:59:20 -0700, Benjamin Huot wrote:
Are you a programmer? of Autopackage? because I have not had any other crashes of anything.
I am, yes. Because it doesn't crash with other things doesn't necessarily mean it's a fault in autopackage, though this is rather suspicious. The problem has disappeared for you now though? So maybe it was a random spurious failure.
thanks -mike
Inkscape-user mailing list Inkscape-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/inkscape-user
I agree with that - I realize it is not always that simple. I think (again not from a programmer's perspective but from a user) that there are so many different types of software that are interrelated on Linux developed by so many different groups, it must not be uncommon for there to be unforseen interactions between software.
On Mon, 19 Jun 2006 09:04:13 -0700, Benjamin Huot wrote:
I agree with that - I realize it is not always that simple. I think (again not from a programmer's perspective but from a user) that there are so many different types of software that are interrelated on Linux developed by so many different groups, it must not be uncommon for there to be unforseen interactions between software.
Yes, indeed. Ironically autopackage is largely about handling unforeseen interactions :)
participants (5)
-
Aaron Spike -
Benjamin Huot -
Bryce Harrington -
Florian Köberle -
Mike Hearn