This bug is still present in xvfb 2:1.20.13-1ubuntu1~20.04.2. It
prevents us from using `xvfb-run` when we need to disambiguate STDOUT
and STDERR.
I'm not familiar with the problem of autopkgtests, but is this still an
issue? Can autopkgtests be fixed?
If we're an impasse, does it make sense to
** Changed in: xorg-server (Ubuntu)
Status: Fix Released => Triaged
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059947
Title:
xvfb-run munges stdout and stderr together
To manage notifica
This bug was fixed in the package xorg-server - 2:1.19.4-1ubuntu2
---
xorg-server (2:1.19.4-1ubuntu2) artful; urgency=medium
* xvfb-run: Keep redirecting stderr to stdout, autopkgtests need it.
-- Timo Aaltonen Wed, 11 Oct 2017 11:12:57 +0300
** Changed in: xorg-server (Ubuntu)
the source package is xorg-server
changing this would break a ton of autopkgtests that use xvfb-run which
now get errors like:
testsuiteFAIL stderr: QStandardPaths: XDG_RUNTIME_DIR not set,
defaulting to
'/tmp/runtime-ubuntu'
--
You received this bug notification beca
Any updates? This still exists 4 years later in xvfb 2:1.16.4-1 . The
only workaround is to copy the entire script locally and remove those 4
characters.
Also the package is xvfb, not xorg-server
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed t
Status changed to 'Confirmed' because the bug affects multiple users.
** Changed in: xorg-server (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1059947
Title:
