protege
protege copied to clipboard
protegeproject
Protege does not start - blank window on Debian
I am trying to get Protege 5.2.0 to run on a Debina/Jessie system. I have downloaded the tar-ball, and start the run.sh script. I get the dialog box offering to install extra components, but the main window is blank, i.e. the X server creates the window and the window manager supplies borders and headers, but there is no content from the application.
The only thing resembling an error message is this Cannot generate ontology catalog for ontology at http://www.semanticweb.org/georg/ontologies/2017/3/untitled-ontology-2
As far as I can see from other issues and advice on the web, this is not supposed to be a critical error. The only advice I could find was to delete the java user preferences, which I have done to no effect. The result is the same whether or not I install extras on startup.
I also tried 5.1.0 with the same result.
Now, protege does run on my home system, running Debian/stretch, or at least the main window looks all right. It also works on my laptop running Ubuntu 16.04, although I have to manually reduce the screen resolution to get legible font size (is there a better way to do that?).
Does anyone have any idea why protege may not work on my main system? Does it depend on any packages? Are there any obscure environment variables which may affect it?
As so much time has passed, if you're still stuck with this issue please let us know. We'll otherwise close it.
I'm (apparently) getting this error with https://www.archlinux.org/packages/community/any/protege using Java 8.
I'm (apparently) getting this error with https://www.archlinux.org/packages/community/any/protege using Java 8.
I've had some troubles with this too on bspwm. Running _JAVA_AWT_WM_NONREPARENTING=1 ./run.sh seems to work. If you want to make this persistent, you can export it on shell startup.
I'm (apparently) getting this error with https://www.archlinux.org/packages/community/any/protege using Java 8.
I've had some troubles with this too on bspwm. Running
_JAVA_AWT_WM_NONREPARENTING=1 ./run.shseems to work. If you want to make this persistent, you can export it on shell startup.
This solved this issue for me too on Artix Linux using DWM WM
Sorry for yakshaving but I ran into this issue on Arch Linux with EXWM as my WM. Setting _JAVA_AWT_WM_NONREPARENTING=1 resolved things for me. I think this should be closed by someone :)
