GNOME Bugzilla – Bug 689369
Multiple problems with gio/tests/appinfo.c test
Last modified: 2018-05-24 14:52:49 UTC
When running the gio/tests/appinfo test an X11 window is shown, then it flickers and then it disappears. This is not OK to do. The test also seems to fail with GLib-GIO:ERROR:appinfo-test.c:11:main: assertion failed: (envvar != NULL) but I'm not sure if this is related. Either way, tip of tree should never ever fail. Also, when running the test with DISPLAY unset it fails with this error ** (gnome-terminal:3213): WARNING **: Could not open X display ** (gnome-terminal:3215): WARNING **: Could not open X display Failed to parse arguments: Cannot open display: Failed to parse arguments: Cannot open display: Failed to parse arguments: Cannot open display: Failed to parse arguments: Cannot open display:
The test works for me when I just run it under my running session. However, I can reproduce this with xvfb: $ DISPLAY= jhbuild run xvfb-run ./appinfo [...] GLib-GIO:ERROR:appinfo-test.c:11:main: assertion failed: (envvar != NULL) That's also the only currently failing test in our automated jhbuild: https://jenkins.qa.ubuntu.com/view/Raring/view/JHBuild%20Gnome/job/jhbuild-amd64-glib/
This is envvar = g_getenv ("GIO_LAUNCHED_DESKTOP_FILE_PID"); This is supposed to be set by g_app_info_launch(), but where does that actually get called? the g_getenv() is the very first thing in the test.
(In reply to comment #1) > The test works for me when I just run it under my running session. However, I > can reproduce this with xvfb: > > $ DISPLAY= jhbuild run xvfb-run ./appinfo Sorry, that's ./appinfo-test of course, and it fails just as well in an already running environment (no jhbuild, no xvfb, etc.).
Please ignore my previous two comments. ./appinfo-test is not a test case, it is being called from ./appinfo. I think the "assertion failed: (envvar != NULL)" is a red herring here, as that isn't what is making the test case fail. It should still be fixed, of course. The test case starts to succeed if I install xterm into the test environment, as that test needs some terminal installed. So this might actually be a duplicate of bug 684690, but we might keep this for the "$GIO_LAUNCHED_DESKTOP_FILE_PID is not set" issue?
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/glib/issues/640.