openjdk team mailing list archive
-
openjdk team
-
Mailing list archive
-
Message #00971
[Bug 235022] Re: SIGSEGV while uninstalling Adobe AIR application with Aptana running
> It's been awhile...guess I will do a quick follow-up then maybe
someone can close this?
closing the openjdk-6 task as won't fix. we don't have an adobe air
package in the distro, afaik.
you may want to check out newer openjdk-6 builds (6b11 in hardy-updates
or 6b12 in intrepid)
** Changed in: openjdk-6 (Ubuntu)
Status: Incomplete => Won't Fix
--
SIGSEGV while uninstalling Adobe AIR application with Aptana running
https://bugs.launchpad.net/bugs/235022
You received this bug notification because you are a member of OpenJDK,
which is subscribed to openjdk-6 in ubuntu.
Status in “openjdk-6” source package in Ubuntu: Won't Fix
Bug description:
Binary package hint: openjdk-6-jre
Ubuntu: 8.04 (generic kernel)
OpenJDK 6 JRE: 6b09-0ubuntu2
Adobe AIR & AIR SDK: alpha1 033108
Aptana Studio: 1.1.6.009905 (stand-alone)
Aptana Studio works fine, except for the embedded browser. I used a sample AIR project from Aptana, corrected the *.XML descriptor file for compatibility with my SDK, built it, installed it with AIR Application Installer, tested it (worked fine), re-executed *.AIR file & began to uninstall, then prior to notification of successful completion this error occurred. Aptana shut down, as did the AIR uninstaller. Afterwards, it appears like the application successfully uninstalled, as it's menu shortcuts are gone and the install directory is gone.
I do not know much about OpenJDK, so hopefully someone will be able to read my attached error file (it popped up on my Desktop after the error).
Random Thoughts:
Could AIR have tried to delete the file after uninstall?
Could having two applications, AIR Uninstaller and Aptana (the *.AIR file was being shown by Aptana in the Projects pane), both accessing a file at the same time cause my error in OpenJDK? If so, who's problem is it? They were both accessing it...OpenJDK seemed to have the problem with it...leads me to OpenJDK as the culprit.
References