display tests fail

Sorry Robert, I can't reproduce this failure (and neither can seb128). Is there anything weird about your display settings that I might not have though about?

Not that I can find. I've tried removing any non-standard packages. I'm building from a freshly created user account and I'm fully up to date utopic here.

Consistently breaks but I can't find out why.

I can reproduce by running 'debuild binary' inside the build directory. I've modified testsuite/gdk/display.c to redirect stdout/stderr to a file and I get:

(/home/bob/bzr/ubuntu/build-area/gtk+3.0-3.12.2/debian/build/shared/testsuite/gdk/.libs/lt-display:18477): Gdk-ERROR **: error: XDG_RUNTIME_DIR not set in the environment.

So something is going wrong in the environment. Note I do have XDG_RUNTIME_DIR set in my environment.

This error is from libwayland-client0 - Since the test is checking for an invalid/missing $DISPLAY Gdk is trying to use the Wayland backend. The Wayland backend is generating a log message and Gdk is converting this to a g_error. g_error aborts the program.

From reading the debuild source it does clean the environment. Can you guys check if you have anything set in /etc/devscripts.conf or ~/.devscripts or do you know of anything that should be setting XDG_RUNTTIME_DIR that I might not have?

Robert, I never editing those configurations, that's weird...

Laney suggested setting XDG_RUNTIME_DIR in debian/rules as other packages do that (e.g. glib2.0). That fixes the problem for me. Still no idea why it breaks for me and not others, but we definitely should set XDG_RUNTIME_DIR as the Wayland backend requires it and tests might use the Wayland backend.

This bug was fixed in the package gtk+3.0 - 3.12.2-0ubuntu6

---------------
gtk+3.0 (3.12.2-0ubuntu6) utopic; urgency=medium

  * debian/control.in, debian/libgtk-3-0.symbols, debian/rules:
    - enable the mir backends only on architectures where mir is built
 -- Sebastien Bacher <email address hidden> Wed, 30 Jul 2014 19:08:26 +0200