I asked Chris about those recently - I think those errors come from
old view generation code and can be ignored.
-Rob-
Do you have the log from the load?
Are all the labels null?
SELECT count(*) FROM node WHERE uid LIKE 'PATO:%' and label IS NULL;
You can always run obo2database separately (obd-create-db.pl is just a
wrapper for this)
>
> Thanks,
>
> Cartik
>
>
> >
>
Amina - is this a known problem with Ubuntu?
Cartik - are you doing something like running obo2database on a remote
machine via ssh?
The problem here is that obo2database (and all the obo command line
tools) *should* be able to execute without any awt or gui code.
However, there is something in
org.oboedit.util.GUIUtil.copyExistingConfigFiles that appears to
invoke awt.
If we remove this dependency, you should be fine
Until we fix this, there should be a way to get this to work once we
know more about your setup (e.g. just setting the DISPLAY env var, or
tunneling X over ssh via the -x option)
On Sep 22, 2008, at 3:33 PM, Cartik R. Kothari wrote:
> Hi Chris,
>
> I discovered the ontologies were not being loaded in the first place
> because of
> some idiosyncracies of the Ubuntu platform, directory read/write
> permissions,
> and such. After clearing through this, as of now I have narrowed the
> problem to
> something in the obo2database program, which executes the
> OBO2Database Java
> class. I get the error message
>
> Exception in thread "main" java.lang.ExceptionInInitializerError
> at org.oboedit.launcher.OBO2Database.main(OBO2Database.java:430)
> Caused by: java.awt.HeadlessException:
> No X11 DISPLAY variable was set, but this program performed an
> operation which
> requires it.
> at
> java.awt.GraphicsEnvironment.checkHeadless(GraphicsEnvironment.java:
> 173)
> at java.awt.Window.<init>(Window.java:437)
> at java.awt.Frame.<init>(Frame.java:419)
> at java.awt.Frame.<init>(Frame.java:384)
> at javax.swing.SwingUtilities
> $SharedOwnerFrame.<init>(SwingUtilities.java:1756)
> at
> javax.swing.SwingUtilities.getSharedOwnerFrame(SwingUtilities.java:
> 1833)
> at javax.swing.JOptionPane.getRootFrame(JOptionPane.java:1692)
> at javax.swing.JOptionPane.showOptionDialog(JOptionPane.java:864)
> at javax.swing.JOptionPane.showMessageDialog(JOptionPane.java:668)
> at javax.swing.JOptionPane.showMessageDialog(JOptionPane.java:639)
> at org.oboedit.util.GUIUtil.copyExistingConfigFiles(GUIUtil.java:307)
> at org.oboedit.gui.Preferences.getOBOEditPrefsDir(Preferences.java:
> 258)
> at org.oboedit.gui.Preferences.<clinit>(Preferences.java:191)
> ... 1 more
>
> This happens after every ontology is downloaded into a directory on
> my machine.
>
> Thanks,
>
> Cartik
>
>
>
> Hi Chris, Rob, Amina,
>
> Thanks for your help. This should be my last post for today. I set the
> DISPLAY environment variable (#export DISPLAY :0.0)
There needs to be an equals sign between name and value for bash:
$ export DISPLAY=":0.0"
What's odd enough is that you need to set this in the first place,
which lets me to believe that you are executing this command as a
different user than you are logged in with to the X11 session. In that
case the X server will likely deny connection attempts from another
user's X clients. To remedy that, do
$ xhost +localhost
*as the user you are logged in with to the X session* (not as the user
as which you can't execute the command below.
You can also try to put Java into headless mode by adding the option -
Djava.awt.headless=true to the command line that invokes the JVM
(i.e., java), but judging from where the error occurs, there is some
OBO-edit code that assumes you are running the GUI no matter what.
-hilmar
--
===========================================================
: Hilmar Lapp -:- Durham, NC -:- hlapp at duke dot edu :
===========================================================