-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Windows 10 java 8 issue #2
Comments
I'm having issues with WOSQI 4.7.2u on all platforms. Try 4.6.0, available here: http://www.webosarchive.com/docs/appstores/ |
Can you elaborate? I am back to working on WOSQI. |
Excited that there's new work happening on this! I have been unable to get 4.7.2 working on any platform -- Linux, Windows and Mac. I'm fairly sure is a Java compat issue. Getting a version of Java that the rest of the SDK is happy with is a bit of a trick on Linux. I follow these instructions: https://www.fosstechnix.com/install-oracle-java-8-on-ubuntu-20-04/ On Mac, I've stopped upgrading at Mojave, and still use Apple Java installer: https://support.apple.com/kb/dl1572?locale=en_US On Windows, I use both 10 and 11 and a newer version of Java. I'll get exact details and update here. All have the same symptoms with 4.7.2. Here's the command line output when running on Ubuntu 22.04 -- of note, the same ipk installed fine seconds later in 4.6.0
|
I think your issues are all caused by the fact that WOSQI builds against Java 12. I will revert to Java 8 (specifically the updated, secure JDK distribution by OpenLogic) for the release of WOSQI 4.8.0. That should fix your problems on Windows and Linux. On your Mojave machine, I would highly recommend uninstalling apple’s Java 6 distribution. Not only is it full of vulnerabilities, my Java code uses Java 7 specific file APIs. I would suggest using jenv via homebrew to install OpenLogic’s JDK 8. |
@codepoet80 please try this early build of 4.8.0 to see if it fixes your java runtime problems. It is HIGHLY incomplete, so please don't try to use it normally, I'm only uploading this so you can test the JREs. |
For completeness on 4.7.2, console output on Windows 11 running Java:
|
For Debian-based modern Linux, Herrie has it working: |
I've seen that, I don't love the implementation. It's not distro or init system agnostic. I am thinking of merging relevant parts of this: https://github.com/incidentist/novacomd and my raspberry pi fork: https://github.com/NotAlexNoyle/novacomd into one universal *nix novacomd installer. Supporting linux, the BSDs, macOS, etc. |
The new *nix novacomd installer will be published here https://github.com/NotAlexNoyle/novacomd-bootstrap I made it a separate project so that I could use a more permissive license. WOSQI 4.8.0 will bundle it into the .jar like a library. |
Jan 26, 2022 2:46:39 PM java.util.prefs.WindowsPreferences
WARNING: Could not open/create prefs root node Software\JavaSoft\Prefs at root 0xffffffff80000002. Windows RegCreateKeyEx(...) returned error code 5.
Jan 26, 2022 2:46:39 PM java.util.prefs.WindowsPreferences WindowsRegOpenKey1
WARNING: Trying to recreate Windows registry node Software\JavaSoft\Prefs at root 0xffffffff80000002.
Jan 26, 2022 2:46:39 PM java.util.prefs.WindowsPreferences openKey
WARNING: Could not open windows registry node Software\JavaSoft\Prefs at root 0xffffffff80000002. Windows RegOpenKey(...) returned error code 2.
Jan 26, 2022 2:46:40 PM java.util.prefs.WindowsPreferences WindowsRegOpenKey1
WARNING: Trying to recreate Windows registry node Software\JavaSoft\Prefs at root 0xffffffff80000002.
Jan 26, 2022 2:46:40 PM java.util.prefs.WindowsPreferences openKey
WARNING: Could not open windows registry node Software\JavaSoft\Prefs at root 0xffffffff80000002. Windows RegOpenKey(...) returned error code 2.
Jan 26, 2022 2:46:40 PM org.jdesktop.application.LocalStorage getId
WARNING: unspecified resource Application.id using WebOSQuickInstallApp
Jan 26, 2022 2:46:40 PM org.jdesktop.application.LocalStorage getId
WARNING: unspecified resource Application.vendorId using UnknownApplicationVendor
The text was updated successfully, but these errors were encountered: