[Help] New version of ImageJ does not build in pbuilder because of lacking DISPLAY variable

[Andreas Tille <andreas@an3as.eu>]

Hi,

I just commited packaging stuff for the latest ImageJ version to SVN[1] but
I failed in building when using pdebuild:

build:
     [copy] Copying 1 file to /tmp/buildd/imagej-1.46o/build
     [copy] Copying 1 file to /tmp/buildd/imagej-1.46o/build
     [copy] Copying 1 file to /tmp/buildd/imagej-1.46o/build
     [copy] Copying 1 file to /tmp/buildd/imagej-1.46o/build
     [copy] Copying 1 file to /tmp/buildd/imagej-1.46o/build
     [copy] Copying 1 file to /tmp/buildd/imagej-1.46o/build
     [copy] Copying 16 files to /tmp/buildd/imagej-1.46o/build/macros
      [jar] Building jar: /tmp/buildd/imagej-1.46o/ij.jar

run:
     [copy] Copying 1 file to /tmp/buildd
     [java] No protocol specified
     [java] Exception in thread "main" java.lang.InternalError: Can't connect to X11 window server using ':0.0' as the value of the DISPLAY variable.
     [java]     at sun.awt.X11GraphicsEnvironment.initDisplay(Native Method)
     [java]     at sun.awt.X11GraphicsEnvironment.access$200(X11GraphicsEnvironment.java:62)
     [java]     at sun.awt.X11GraphicsEnvironment$1.run(X11GraphicsEnvironment.java:178)
     [java]     at java.security.AccessController.doPrivileged(Native Method)
     [java]     at sun.awt.X11GraphicsEnvironment.<clinit>(X11GraphicsEnvironment.java:142)
     [java]     at java.lang.Class.forName0(Native Method)
     [java]     at java.lang.Class.forName(Class.java:186)
     [java]     at java.awt.GraphicsEnvironment.getLocalGraphicsEnvironment(GraphicsEnvironment.java:82)
     [java]     at java.awt.Window.init(Window.java:424)
     [java]     at java.awt.Window.<init>(Window.java:477)
     [java]     at java.awt.Frame.<init>(Frame.java:419)
     [java]     at ij.ImageJ.<init>(ImageJ.java:132)
     [java]     at ij.ImageJ.main(ImageJ.java:657)


I can confirm that debuild works fine because there is a properly
setup X environment.

Any clue?  The hint from Steve[2] did not ring a bell when I was looking
at the lines of code where the problem occured.

Kind regards

       Andreas.


[1] svn://svn.debian.org/debian-med/trunk/packages/imagej/trunk/
    or `debcheckout imagej`
[2] http://lists.alioth.debian.org/pipermail/debian-med-packaging/2012-June/015823.html

-- 
http://fam-tille.de