Awn

Eclipse launcher creates a separate task

Bug #205640 reported by Fedor Isakov
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Awn
Confirmed
Undecided
Unassigned

Bug Description

Just upgraded to Hardy 64bit, installed AWN from https://launchpad.net/~reacocard-awn/+archive (0.3.1.bzr207.5~hardy).

I noticed the Eclipse launcher would now create a separate task when Eclipse is launched. It wasn't the case with Gutsy and previous versions of AWN.

BTW, the system monitor applet now shows "java" as the eclipse process name, instead of "eclipse" as it used to.

Revision history for this message
moonbeam (rcryderman) wrote :

The fact that it is showing up as java would explain the behavior - I'm guessing that something was modified in the launching process for the newest Eclipse release. It is quite common to also see this type of problem with python apps (for example).

There should be some tools in place in the 0.6 milestone release to help alleviate these types of issues. Though they will not always be perfect... this is not intrinsically a bug in awn so much as it being inherently difficult to match up a launched process with a window. In this case what is probably happening is:

launcher spawns a process -> That process is a wrapper that spawns a 2nd process -> 2nd process opens the Elcipse window.

It proves difficult for awn to connect that 2nd process to the launcher.

The experimental standalone-launcher/taskmanager applet in awn-extras currently does have the necessary functionality to resolve this issue. Otherwise it probably won't be resolve before 0.6.

Changed in awn:
milestone: none → 0.6
status: New → Confirmed
Revision history for this message
Fedor Isakov (fisakov) wrote :

As mentioned here:

http://help.eclipse.org/help33/index.jsp?topic=/org.eclipse.platform.doc.isv/reference/misc/launcher.html

>Exceptions
>
> * linux.ppc, linux.x86_64, aix.ppc: The launcher is not able to load some older vms using the JNI invocation API. By default
>on these platforms the launcher will prefer to execute java in a separate process. To force the launcher to load the vm using
>JNI, specify a -vm option pointing directly to the vm's shared library (libjvm.so).

The fix is to specify the -vm parameter to eclipse launcher, e.g. prepend the following lines to eclipse.ini:

-vm
/usr/lib/jvm/java-6-sun/jre/lib/amd64/server/libjvm.so

I guess this closes the issue (that is, for Eclipse)

Revision history for this message
moonbeam (rcryderman) wrote :

I've marked this bug as a duplicate of 129753. It'll get closed in the bug tracker once the general issue gets resolved in a satisfactory manner. Thanks for the bug report and for researching the Eclipse fix.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.