I have installed PPM 9.2 on a system that has a Red Hat Enterprise 6 operating system. When I try to open the Workbench, using the terminal, i receive the following error :
"GLib-GObject-CRITICAL **: g_object_notify assertion 'G_IS_OBJECT (object)' failed"
And when i try to open the Workbench using Open With -> javaws nothing happens.
Anybody else encountered this problem ?
Go to Solution.
Maybe is a good idea to enable java console to see if there is any error when you try to run workbench from terminal. Here is a link were you can find the information about enabling java console.
Sorry for the late reply, but I was away for a while.
I already enabled the java console, but I receive the error message in the terminal without the java console being displayed.
I am wondering if you have tried to clean the java cache or reinstall the java. If not, you can try it.
What Java version are you using also?
I have tried that too. I am currently using jdk1.7.0_13. Before this I have tried with jdk1.7.0_11. I got the same results with both this versions.
can you tell us how exactly you are opening the workbench from the Linux terminal?
I am using the following command when located in the directory that contains the workbench.jnlp file :
you said that this is the way it works, correct?
Actually, you SHOULD use javaws (which stands for Java Web Start) for launching the jnlp file.
the java executable is meant to execute java code only.
By using the javaws command in the terminal I receive the error from my original post. This is the problem that I am trying to resolve.
I haven't been able to start the workbench in any way.
can you provide the output of javaws -verbose workbench.jnlp?
also, you have to make sure that the workbench window is not open in the background, since javaws may open detached from the terminal session.
how are you connected exactly to the Linux terminal?
Thanks for all your help. Not sure why but when I ran the javaws -verbose workbench.jnlp command, the java console opened, the terminal displayed the followind messages :
" Java(TM) Web Start 10.13.2.20-fcs Launching: /usr/java/jdk1.7.0_13/jre/bin/java/usr/java/jdk1.7.0_13/jre/bin/java -classpath /usr/java/jdk1.7.0_13/jre/lib/deploy.jar -Djava.security.policy=file:/usr/java/jdk1.7.0_13/jre/lib/security/javaws.policy -DtrustProxy=true -Xverify:remote -Djnlpx.home=/usr/java/jdk1.7.0_13/jre/bin -Djnlpx.origFilenameArg=workbench.jnlp -Djnlpx.remove=true -Dsun.awt.warmup=true -Xbootclasspath/a:/usr/java/jdk1.7.0_13/jre/lib/javaws.jar:/usr/java/jdk1.7.0_13/jre/lib/deploy.jar:/usr/java/jdk1.7.0_13/jre/lib/plugin.jar -Djnlpx.splashport=62019 -Djnlpx.jvm=/usr/java/jdk1.7.0_13/jre/bin/java com.sun.javaws.Main -verbose -notWebJava /tmp/javawu5afGK "
, and the workbench successfully started.
I was using a virtual machine that had a Red Hat Enterprise 6 - 64bit OS.
Thanks again for all your help. I am going to look into it a little bit further now, but at least I know that it starts.
:) this is not the first application that only works in debug mode :D
Anyways, glad to help.