ICEDTEA-WEB not launching

thisisnotme · 2022-04-11 23:47:44

I use connectwise support for work and have always been able to work using icedtea-web after updating this morning via yay
I noticed that all of the java versions roll to 18. vs 17.
this is from my pacman log

2022-04-11T14:41:33-0700] [PACMAN] Running 'pacman -S -y -u --config /etc/pacman.conf --'
[2022-04-11T14:41:33-0700] [PACMAN] synchronizing package lists
[2022-04-11T14:41:34-0700] [PACMAN] starting full system upgrade
[2022-04-11T14:43:03-0700] [ALPM] transaction started
[2022-04-11T14:43:03-0700] [ALPM] upgraded libffi (3.4.2-4 -> 3.4.2-5)
[2022-04-11T14:43:03-0700] [ALPM] upgraded gtk-update-icon-cache (1:4.6.2-1 -> 1:4.6.2-2)
[2022-04-11T14:43:03-0700] [ALPM] upgraded libgpg-error (1.44-1 -> 1.45-1)
[2022-04-11T14:43:03-0700] [ALPM] upgraded gtk4 (1:4.6.2-1 -> 1:4.6.2-2)
[2022-04-11T14:43:03-0700] [ALPM] upgraded jre-openjdk-headless (17.0.3.u3-1 -> 18-2)
[2022-04-11T14:43:03-0700] [ALPM] upgraded jre-openjdk (17.0.3.u3-1 -> 18-2)
[2022-04-11T14:43:03-0700] [ALPM] upgraded libaio (0.3.112-2 -> 0.3.112-3)
[2022-04-11T14:43:03-0700] [ALPM] upgraded libarchive (3.6.0-2 -> 3.6.1-1)
[2022-04-11T14:43:03-0700] [ALPM] upgraded libmfx (22.1.0-1 -> 22.3.0-1)
[2022-04-11T14:43:03-0700] [ALPM] upgraded libva (2.13.0-2 -> 2.14.0-1)
[2022-04-11T14:43:03-0700] [ALPM] warning: /etc/pacman.d/mirrorlist installed as /etc/pacman.d/mirrorlist.pacnew
[2022-04-11T14:43:03-0700] [ALPM] upgraded pacman-mirrorlist (20220227-1 -> 20220410-1)
[2022-04-11T14:43:03-0700] [ALPM] upgraded python-pyparsing (3.0.7-1 -> 3.0.8-1)
[2022-04-11T14:43:04-0700] [ALPM] upgraded telegram-desktop (3.6.1-1 -> 3.6.1-2)
[2022-04-11T14:43:04-0700] [ALPM] upgraded wpa_supplicant (2:2.10-3 -> 2:2.10-4)
[2022-04-11T14:43:04-0700] [ALPM] upgraded xorg-xdpyinfo (1.3.2-4 -> 1.3.3-4)
[2022-04-11T14:43:04-0700] [ALPM] transaction completed
[2022-04-11T14:43:04-0700] [ALPM] running '30-systemd-daemon-reload.hook'...
[2022-04-11T14:43:04-0700] [ALPM] running '30-systemd-update.hook'...
[2022-04-11T14:43:04-0700] [ALPM] running 'dbus-reload.hook'...
[2022-04-11T14:43:04-0700] [ALPM] running 'glib-compile-schemas.hook'...
[2022-04-11T14:43:04-0700] [ALPM] running 'gtk-update-icon-cache.hook'...
[2022-04-11T14:43:04-0700] [ALPM] running 'gtk4-querymodules.hook'...
[2022-04-11T14:43:04-0700] [ALPM] running 'texinfo-install.hook'...
[2022-04-11T14:43:04-0700] [ALPM] running 'update-desktop-database.hook'...

I cannot get anything rational from launching the ConnectWiseControl.Client.jnlp file
The current behavior is I get a splash screen and nothing else.
I dont see any events in dmesg
this is what happens if I launch from a shell

javaws ConnectWiseControl.Client.jnlp 
selected jre: /usr/lib/jvm/default-runtime
Warning!, Fall back in resolve_jar to hardcoded paths: 
/usr/share/java/js.jar
WARNING: package sun.applet not in java.desktop
WARNING: package com.sun.net.ssl.internal.ssl not in java.base
WARNING: package javax.jnlp not in java.desktop
Exception in thread "main" java.lang.UnsupportedOperationException: The Security Manager is deprecated and will be removed in a future release
        at java.base/java.lang.System.setSecurityManager(System.java:416)
        at net.sourceforge.jnlp.runtime.JNLPRuntime.initialize(JNLPRuntime.java:268)
        at net.sourceforge.jnlp.runtime.Boot.init(Boot.java:353)
        at net.sourceforge.jnlp.runtime.JnlpBoot.run(JnlpBoot.java:58)
        at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:274)
        at net.sourceforge.jnlp.runtime.Boot.run(Boot.java:63)
        at java.base/java.security.AccessController.doPrivileged(AccessController.java:318)
        at net.sourceforge.jnlp.runtime.Boot.main(Boot.java:214)

this is my java environment

archlinux-java status
Available Java environments:
java-18-openjdk (default)

I dont know what else would be helpful or how to track this to a specific package.
Any guidance would be greatly appreciated.

Thank you

mpan · 2022-04-12 01:25:46

Both JNLP and SecurityManager are being removed.⁽¹⁾ Software depending on it must be fixed. And this is by no means anything sudden or unexpected.

I do not know ConnectWise, but it seems that they knew about the issue, decided to not fix it and instead opted for forcing users to circumvent it. Of course the inevitable came.

What you can do is temporarily install both 17 and 18, enable 17 and see if that suffices for the time being. This is not a permanent solution, as 17 will become unsupported at some point. Even LTS versions expire. It will also require you to switch to 17 each time you want to run ConnectWise software.

If that doesn’t work, you may try containers (or an entire virtual machine) and running old dependencies, including version 17.
____
⁽¹⁾ In this particular case I guess it may actually be a bug or some kind of omission in the implementation, as it seems strange that it reports an exception related to removal of SecurityManager while still trying to perform a JNLP deployment. But the clock is ticking fast — it matters little if you need to address that today or “tommorow”.

Last edited by mpan (2022-04-12 01:58:23)

thisisnotme · 2022-04-12 15:00:13

So if im understanding you, java 18 dropped all support for applets and icedtea-web has been used to make them work as a work around.
I think that doesn't fully add up. I think there is more an incompatibility that needs a bug report. The release notes don't say that all support for applets has been dropped to my reading.
While installing an old version of java may fix it for now a better solution would be to make a full bug report.
Can anyone help with that?

mpan · 2022-04-12 16:35:02

That was a process spanning over a decade: it just culminated with the release of version 18. You might’ve missed that as a user, because that was of concern primarily for developers. The software vendors are expected to maintain their products and had years to do so. To give you the approximate timeline:

Late 2000s to early 2010s: realization that Java Applets have no future.
Since 2013: phasing out support in browsers.
2016: official deprecation of Java Applets.
Late 2010s: no major browser supports plugins needed to run Java Applets. This is the final warning sign for developers and users of poorly maintained software may start facing trouble. JNLP is offered as a temporary alternative.
2018: complete removal of web start by Oracle. This is the point, 5–10 years after it was known Applets are doomed, when no software vendor should rely on the technology. Since the Applets API itself is still technically present and JNLP part of IcedTea-Web of it is still being maintained, it provides a kind of cushion for those, who missed the deadline. But this is really the final call to fix things, stat.
2020: the Applets API removal is announced.
2021: SecurityManager removal is announced, as the feature has little use at this point.
2022: both features are finally nuked completely.

Do you see the wider picture now? Unless you are stuck with some abandoned program, you were not expected to experience any trouble.

At this point there are three LTS versions that are still at least partially supported: 8, 11 and 17. If you really want to, you may use either of those and the corresponding IcedTea-Web to still run legacy software. The presence of those is why you may be shrugged off by ConnectWise, if you try reporting the bug. So be prepared for that reaction.

If you still want to report a bug, above I provided the relevant links you may use to show them the situation.

codezero · 2022-04-12 20:15:58

Having this exact issue with the same vendor. Going to give reporting this to them a try.

lostpacket · 2022-04-13 17:04:45

Confirmed also having exact same issue, downgrading to 17 worked for time being.

Last edited by lostpacket (2022-04-13 17:11:31)

Slithery · 2022-04-13 18:01:32

Please refrain from the +1 posts people, thanks.
CoC - No empty posts

thisisnotme · 2022-04-13 23:37:26

Regardless of your history lesson, that is still not addressing what my question was. You're not providing help just lambasting the creator of some software and complaining about how the Java ecosystem evolves slowly.
I would also like to point out that the change log does not say this "2022: both features are finally nuked completely." based on what I could find.
Helpful and pertinent information would be, for now downgrade to this version of Java using these commands:

sudo pacman -S jre17-openjdk-headless jre17-openjdk

then change default to 17 via

sudo archlinux-java set java-17-openjdk

Lastly, here is how to gather useful information for the applet developer.

This is what my question was about, because I don't know how to do this part here.

Slithery · 2022-04-14 00:05:46

thisisnotme wrote:

Helpful and pertinent information would be, for now downgrade to this version of Java using these commands:
sudo pacman -S jre17-openjdk-headless jre17-openjdk

Unless you are using out of date mirrors then those packages no longer exist in the Arch repos...
https://archlinux.org/packages/?sort=&q=jre-17

@mpan posted the correct answer. This is an upstream issue that you need to take up with the software developers not a problem with Arch.

mpan · 2022-04-14 02:29:58

thisisnotme:
This is the temporary workaround I proposed in my first answer. The second post was a direct response to what you said: explaining why you might have missed the changes and giving you links needed to report the bug. So I do not see, what’s the problem or where did I complain about Java.

Both posts are in critical tone, because — as the user — you have right to know the situation. If the situation is ugly, it’s hard to tell stories of rainbows and unicorns. But certainly this was far from blatantly bashing the company.

Slithery:
One dash too many: jre8, jre11 and jre17.

hiavata · 2022-05-17 20:17:27

I've had the same issue for the last couple of days. Sure, downgrading to 17 resolved it for now, but I've raised the issue with their support to check if they have any plans on fixing this.

hiavata · 2022-05-18 09:17:18

I've got a reply that they've raised (now) the issue with their engineering. So. if anyone needs or would like to follow up with them:

SCP-37617- Unable to join Support sessions from Linux machine running openjdk 18

Arch Linux

#1 2022-04-11 23:47:44

ICEDTEA-WEB not launching

#2 2022-04-12 01:25:46

Re: ICEDTEA-WEB not launching

#3 2022-04-12 15:00:13

Re: ICEDTEA-WEB not launching

#4 2022-04-12 16:35:02

Re: ICEDTEA-WEB not launching

#5 2022-04-12 20:15:58

Re: ICEDTEA-WEB not launching

#6 2022-04-13 17:04:45

Re: ICEDTEA-WEB not launching

#7 2022-04-13 18:01:32

Re: ICEDTEA-WEB not launching

#8 2022-04-13 23:37:26

Re: ICEDTEA-WEB not launching

#9 2022-04-14 00:05:46

Re: ICEDTEA-WEB not launching

#10 2022-04-14 02:29:58

Re: ICEDTEA-WEB not launching

#11 2022-05-17 20:17:27

Re: ICEDTEA-WEB not launching

#12 2022-05-18 09:17:18

Re: ICEDTEA-WEB not launching

Board footer