I am trying to use my company's remote help system. It relies on a Java plugin in a web browser. When I go to the company support web site, all browsers iincluded with Mageia 2 Beta 1 -- Firefox, Konqueror and Chromium -- show me a blank window. I get the same results whether I have "sun java" installed or not. In other words, the default Mageia install give you OpenJDK 1.7. Mageia also offers "Sun Java 1.6 (the package claims to be build 26). When you go to the Oracle Java site and click on "Do I have Java" it returns that you are running build 21. I have also attempted to configure which Java I use with the "alternatives" command. That did not help either. Java as a plugin for Mageia 2 Beta 1 seems to be broken. You can see the problem for yourself by going to: support // at // editshare.com You should get a Java login window, but the page just comes up blank. I do not have this problem on other Linux distros such as Mandriva 2011 or Unbuntu 12.04 Beta 1. Try it on OS X or Windows too. No problem.
is icedtea-web installed ?
Keywords: (none) => NEEDINFO
Yes it is. I also looked at the icedtea configuration and it all seems correct.
what is the exact url ? I see nothing in the website
can be a duplicate of https://bugs.mageia.org/show_bug.cgi?id=4578 I will try in a vm when rpm works again
Hi Manuel, Sorry, I messed up on the url. The url is: support.editshare.com I do not think this problem is a duplicate of #4578. On two different systems where I have installed Mageia 2 Beta 1 64-bit... /usr/lib64/mozilla/plugins/libjavaplugin.so is a symlink to /etc/alternatives/libjavaplugin.so.x86_64. And /etc/alternatives/libjavaplugin.so.x86_64 is itself a symlink pointing to /usr/lib64/IcedTeaPlugin.so I do not have a directory /usr/lib/mozilla/plugins as this is a 64-bit installation. Interestingly, if I install sun-java-1.6.0 and run "alternatives --config java" and select the sun java instead of openjdk, the symlink in /usr/lib64/mozilla/plugins/libjavaplugin.so continues pointing to /etc/alternatives/libjavaplugin.so.x86_64. And /etc/alternatives/libjavaplugin.so.x86_64 continues pointing to /usr/lib64/IcedTeaPlugin.so. So, running "alternatives" on java does not seem to affect the mozilla plugin. Also, even though I have openjdk installed, with or without sun-java installed, if I go to a "Do I have Java" web site with Firefox or Chromium or Konqueror, it reports that I have sun java 1.6.0-version 21. That's odd, because when I install sun-java from Mageia, supposedly this is version 26?
Indeed nothing seems working out of the box with the pre-beta2
Keywords: NEEDINFO => (none)Priority: Normal => release_blockerAssignee: bugsquad => dmorganecSource RPM: (none) => icedtea-web
CC: (none) => ennael1
Confirmed not working pre-beta2
can you update and check you have 1.2.1 version installed. You should be able to check it's working fine now: http://www.java.com/en/download/testjava.jsp
Please excuse this question but what do you mean by "update and check I have 1.2.1 version installed"? 1.2.1 of what package?
icedtea-web The update was pushed to Core Release a few hours ago.
CC: (none) => davidwhodgins
I updated but it's not working for me, or at least it's not solving the problem opening up my company's "remote help" application. As I mentioned in the original report, please go to "support.editshare.com". Your browser should open up a remote help login screen. This works fine with Mandriva 2011 with Sun Java. Works fine with Windows and OS X. I can't get it to work with Mageia 2. I enabled logging in the Iced Tea control panel and this is what I get when I try to log into the above site: java.lang.SecurityException: Changing the SecurityManager is not allowed. at net.sourceforge.jnlp.runtime.JNLPSecurityManager.checkPermission(JNLPSecurityManager.java:270) at java.lang.System.setSecurityManager0(System.java:290) at java.lang.System.setSecurityManager(System.java:281) at com.aem.shelp.applet.TinyApplet.init(TinyApplet.java:102) at sun.applet.AppletPanel.run(AppletPanel.java:436) at java.lang.Thread.run(Thread.java:679) In the Iced Tea configuration, I allow users to override security warnings.
decreasing priority as it's working partly and can be fixed through updates
Priority: release_blocker => High
Hi, I have an update from the company that sells the Simple Help remote support application. It sounds like the problem is in IcedTea and that there isn't anything Mageia can do about it. Here is the company's description of the problem: --------------- Hi Andy, Yes, I installed Mageia and the issue is the same as other distributions I've tested. The problem isn't an OpenJDK one, but rather an IcedTea one. Since SimpleHelp's binaries are all signed, SimpleHelp should be trusted by the browser's Java plugin. Importantly, additional binaries downloaded at runtime should also be trusted. In IcedTea this is not the case: so SimpleHelp's launcher applet is trusted, but the components it downloads on demand are not. As a result, the entire session is untrusted too. IcedTea does not handle this well at all, and from tracking comments I think it isn't really implemented. Hence the plethora of exceptions you see. The best way to handle it is to have the launcher applet download and save the components to disk, and spawn a second application that runs them (outside of the browser). It is an important change, and not one we can make in 3.12 (as it is GAing), but we are going to do a point release directly afterwards where we address only this issue. Thanks, George --------- So, you should probably mark this bug as "wont fix" or something like that.
Thought I would mention that I got Simple Help working on Ubuntu 12.04. Originally, I had the same issue as I had here. Doesn't work with Iced Tea and OpenJDK. However, I was able to install Oracle Java 1.7 from their dev repo and run "update-java" and when I selected Oracle-JAVA 1.7, it worked. Unlike when I tried installing Oracle Java 1.6 on Mageia and running update-java on Mageia, where Firefox continue to use some sort of built-in Java plugin. I think there is a problem with Mageia that does not exist with Ubuntu.
Hi, This bug was filed against cauldron, but we do not have cauldron at the moment. Please report whether this bug is still valid for Mageia 2. Thanks :) Cheers, marja
This bug is still current with Mageia 2. I was able to get the Oracle Java plugin working in Firefox by installing the Oracle Java 1.7 RPM offered on the Oracle Java web site and manually creating a symlink in /usr/lib64/mozilla/plugins: libnpjp2.so -> /usr/java/jre1.7.0_04/lib/amd64/libnpjp2.so so at least I am able to get my work done. However, after installing the RPM -- which unfortunately is a Fedora RPM -- the normal procedure for running update-alternatives does not work. As far as Mageia 2 is concerned, it does not think I have ANY Java installed: [root@localhost plugins]# update-alternatives --config java No alternatives for java. I do have Java installed as you can see: [root@localhost plugins]# /usr/bin/java -version java version "1.7.0_04" Java(TM) SE Runtime Environment (build 1.7.0_04-b20) Java HotSpot(TM) 64-Bit Server VM (build 23.0-b21, mixed mode) So, this is still a big mess in Mageia 2. The problems are: 1. I have a web application that does not work with OpenJDK 2. The only Oracle Java RPMs available are for Fedora, because Mageia 2 does not package Oracle Java. 3. The Fedora RPM for Oracle Java 1.7 puts files into paths that Mageia 2 does not understand, so "update-alternatives" doesn't work. A clever Linux hacker can figure this out and put the plugin in the correct place, but this would be very difficult for most Mageia users.
Version: Cauldron => 2
We can not do much about Oracle's java as we do not support it. What if you install open java from Mageia's repos and try to use this one for java command? Or do you need this one to also be Oracle's version?
CC: (none) => sander.lepik
As I said at the beginning of this bug report -- and at several places in the middle -- OpenJDK does not work with the remote help browser plugin. I understand Mageia's decision to not support Oracle Java. However, this decision is going to cause problems for users.
>I understand Mageia's decision to not support Oracle Java. it's not our decision see: https://wiki.mageia.org/en/Mageia_2_Release_Notes#Sun_Java
Note that java is used for running java programs from local files. It is not used for web browsers. In Mageia, only icedtea-web, which in turn uses openjdk is supported. Using update alternatives with oracle java would require something similar to (but with the correct paths and version numbers) ... update-alternatives --install /usr/lib/mozilla/plugins/libjavaplugin.so libjavaplugin.so /usr/lib/jvm/java-1.6.0-sun-1.6.0.26/jre/lib/i386/libnpjp2.so 1600 update-alternatives --config libjavaplugin.so I think it's simpler to just specify manually creating the symlink, directly.
I propose that Mageia just provide instructions that are as clear as you have here about installing Oracle JAVA JDK or JRE on Ubuntu. http://forums.team-nocturnal.com/showthread.php/772 It looks like there is an ubuntu ppa repo that gives you a revised update-alternatives package that understands the paths that get used when you follow the instructions in the forum. This is beyond my understanding of how to do. But I can tell you I followed the instructions for Ubuntu and it "just worked". To make the web plugin work for Mageia 2, I looked at my Ubuntu system to see what symlinks got created at /usr/lib/mozilla/plugins/libnpjp2.so (Ubuntu doesn't use "lib64 for 64-bit installs -- they use "lib" and "lib32") and I just made sure to find the equivalent file and symlink to it inside Mageia 2's /usr/lib64/mozilla/plugins directory. Not very sophisticated, but it worked for me.
Please look at the bottom of this mail to see whether you're the assignee of this bug, if you don't already know whether you are. If you're the assignee: We'd like to know for sure whether this bug was assigned correctly. Please change status to ASSIGNED if it is, or put OK on the whiteboard instead. If you don't have a clue and don't see a way to find out, then please put NEEDHELP on the whiteboard. Please assign back to Bug Squad or to the correct person to solve this bug if we were wrong to assign it to you, and explain why. Thanks :) **************************** @ the reporter and persons in the cc of this bug: If you have any new information that wasn't given before (like this bug being valid for another version of Mageia, too, or it being solved) please tell us. @ the reporter of this bug If you didn't reply yet to a request for more information, please do so within two weeks from now. Thanks all :-D
Keywords: NEEDINFO => (none)CC: (none) => marja11Version: 2 => CauldronWhiteboard: (none) => MGA2TOO
Too old. Upstream issue
Status: NEW => RESOLVEDCC: (none) => nicResolution: (none) => WONTFIX