Can't use Java Sound (Gervill) synthesizer when launched by JNLP
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
icedtea-web (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
When I launch my Java Sound MIDI application using JNLP, the default (Java Sound Gervill) synthesizer can't be opened. It hangs trying to open it, without success.
When I launch the same application using a "java -jar AMK.jar" command, I can use it with no problem.
Here is my JNLP file used to launch it:
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
<jnlp codebase=
<information>
<homepage href=""/>
<icon href="file:
<icon href="file:
<offline-allowed/>
</information>
<security>
<all-permissions/>
</security>
<resources>
<j2se java-vm-
<jar eager="true" href="AMK.jar" main="true"/>
</resources>
<applicatio
</jnlp>
By the way, it has a JavaNativeInterface (JNI) library the code loads itself, which works fine when launched via JNLP. It just can't use the Gervill (default) synthesizer. It can use other synthesizers, and MIDI interfaces - just not the default synthesizer.
Version: 6b21.3-1ubuntu1 (quantal)
ProblemType: Bug
DistroRelease: Ubuntu 12.10
Package: icedtea-6-plugin 1.3-1ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu6
Architecture: i386
Date: Tue Oct 30 15:21:10 2012
InstallationDate: Installed on 2012-04-26 (186 days ago)
InstallationMedia: Lubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MarkForUpload: True
SourcePackage: icedtea-web
UpgradeStatus: Upgraded to quantal on 2012-10-20 (9 days ago)
Solved (maybe).
The problem appears to have gone away. I can now use the Java Sound (Gervill) synthesizer when I launch my application using a '.jnlp' file on my machine.
I was noticing it worked when launched from the Internet, so I decided to try it where the jnlp file is in a local file, and it worked this time.
My best explanation is that I had somehow managed to get the Gervill synthesizer into a bad state when I was trying to use it.
The other explanation, is that I am now using Open Java 7 (where I was using Open Java 6 before).
As far as I am concerned, nothing more needs to be done on investigation this problem, unless it somehow re-appears.
- Aere