Skip to content
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

Jajuk fails to load following Ubuntu upgrade 17.10 to 18.10 #2017

Closed
GoMeister opened this issue May 5, 2018 · 5 comments
Closed

Jajuk fails to load following Ubuntu upgrade 17.10 to 18.10 #2017

GoMeister opened this issue May 5, 2018 · 5 comments
Assignees

Comments

@GoMeister
Copy link

@GoMeister GoMeister commented May 5, 2018

System log gives:
May 5 21:33:26 eric-Latitude-E5510 jajuk.desktop[8405]: Detected a 64-bit operating system, using the lib64 native library directory.
May 5 21:33:26 eric-Latitude-E5510 jajuk.desktop[8405]: Java version in the default path is: 10.
May 5 21:33:26 eric-Latitude-E5510 jajuk.desktop[8405]: No Java compatible version detected, but let's still try to run it!
May 5 21:33:26 eric-Latitude-E5510 jajuk.desktop[8405]: java -client -Xms20M -Xmx2G -XX:MinHeapFreeRatio=5 -XX:MaxHeapFreeRatio=10 -Xverify:none -Djava.library.path=/usr/lib/jni:/usr/lib:/usr/share/jajuk/lib64:/usr/share/jajuk/bin/../lib/lib64 -jar jajuk.jar -notest
May 5 21:33:26 eric-Latitude-E5510 jajuk.desktop[8405]: [BOOT] Java Runtime Environment 1.7 minimum required. You use a JVM ext.JVM@7d4793a8

@bflorat

This comment has been minimized.

Copy link
Contributor

@bflorat bflorat commented May 8, 2018

@GoMeister

This comment has been minimized.

Copy link
Author

@GoMeister GoMeister commented May 8, 2018

Jajuk loads with following:

image

image

@GoMeister

This comment has been minimized.

Copy link
Author

@GoMeister GoMeister commented May 8, 2018

Seemed a good time to reload the collection.... Shall I close the ticket?

@bflorat

This comment has been minimized.

Copy link
Contributor

@bflorat bflorat commented May 9, 2018

Thanks, please close the ticket indeed. The version you use is unstable, it creates a separated collection in ~/.jajuk_test_<release> as final releases collections are stored in ~/.jajuk directory. If you're happy with this release, changing (being root) in /usr/bin/jajuk -testto -notest should force it to use your current collection (please confirm).
If you don't mind loosing your playing history / ratings... you may want just reload your collection.

@GoMeister

This comment has been minimized.

Copy link
Author

@GoMeister GoMeister commented May 9, 2018

Flag set to -notest and collection loads. Many thanks!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
2 participants
You can’t perform that action at this time.