Microchip-MPLAB-Harmony / contentmanager

Harmony 3 Content Manager
https://microchip-mplab-harmony.github.io/contentmanager/
Other
3 stars 2 forks source link

Blank GUI when run from MPLAB X 6.00 #12

Open topherbuckley opened 2 years ago

topherbuckley commented 2 years ago

As per this issue I can run the content manager from the terminal, but when trying to open it via MPLAB X 6.00, I get the attached blank GUI. harmony

The buttons are responsive, but it looks like text is just failing to render in both the text input fields and button labels. All subsequent menus (e.g. pressing the top right button to select a dir) opens up other similarly buggy screens.

I had to replace the jdk within my mplab install directory (e.g. {basepath}/mplab/v6.00/sys/java/{existing_jdk} with the jdk downloaded from zulu). After doing this, I have to manually run mplab_ide with the --jdkhome flag and point it to this new directory.

So two points for this issues: 1.) I recommend you fix the default jdk installed to properly render the gui without having to do the workaround mentioned above 2.) How can I permanently configure the new jdkhome such that I don't have to type this everytime? I'm guessing there is some config file somewhere?

System details: Ubuntu 20.04.3 LTS MPLAB X v6.00

kkathirvel commented 2 years ago

@topherbuckley No need to replace MPLABX jdk with the downloaded one. Place the new downloaded jdk somewhere else and add the path \<jdk folder location>/bin to environment variable PATH

topherbuckley commented 2 years ago

@kkathirvel as I already resolved this I'm hesitant to go back and test, but just curious how would MPLABX know which jdk to select if I had multiple in my PATH? MPLABX appeared to be ignoring my env vars and continuing to use the jdk in {basepath}/mplab/v6.00/sys/java/{existing_jdk}.

I'm not sure, but maybe I already did what you intended via setting the environment vars via update-alternatives and manually setting $JAVA_HOME to the Zulu with fx jdk, though this did not appear to work. This is why I ended up replacing the one mentioned above (which did work).

zizimumu commented 2 years ago

i have the same issue when install mplab 6.0 on Ubuntu 16.04, there is a solution for me:

"mplab/v6.00/sys/java/zulu8.54.0.21-ca-fx-jre8.0.292-linux_x64" is my mplab 6.0 JDK path, I copy all the directory "mplabx/v5.50/sys/java/zulu8.40.0.25-ca-fx-jre8.0.222-linux_x64" from mplab 5.50 to mplab v6.0 "mplab/v6.00/sys/java/", and then rename zulu8.40.0.25-ca-fx-jre8.0.222-linux_x64 to java/zulu8.54.0.21-ca-fx-jre8.0.292-linux_x64.

MichalJahelka commented 2 years ago

Mageia 8. Same problem. Solution is download newer (for example) zulu8.62.0.19-ca-fx-jre8.0.332-linux_x64.tar.gz unpack to mplab/v6.00/sys/java. Then edit MPLAB config file mplab/v6.00/mplab_platform/etc/mplab_ide.conf to use this file. Line jdkhome="/opt/microchip/mplabx/v6.00/sys/java/zulu8.54.0.21-ca-fx-jre8.0.292-linux_x64/" replace with jdkhome="/opt/microchip/mplabx/v6.00/sys/java/zulu8.62.0.19-ca-fx-jre8.0.332-linux_x64/".

ecadmaster commented 2 years ago

using zulu8.62.0.19-ca-fx-jre8.0.332-linux_x64, it works like a charm, thanks @MichalJahelka , I downloaded from https://cdn.azul.com/zulu/bin/

Yusuf-joe commented 1 year ago

i tried all the solutions offered here and non worked. MPLAB IPE v6.00 Ubuntu 22.04

how on the planet does a company that makes software as part of their main product leave a big massive error like that in their software? just how? the software is literally not functional.

koenusz commented 1 year ago

@MichalJahelka worked like a charm I used zulu8.68.0.21-ca-fx-jre8.0.362-linux_x64

MPLAB IPE v6.00 Ubuntu 22.04