This bug was fixed in the package libpipeline - 1.5.2-1ubuntu1
---
libpipeline (1.5.2-1ubuntu1) focal; urgency=medium
* Make autopkgtests cross-test-friendly.
-- Steve Langasek Thu, 09 Jan 2020
08:45:21 -0800
** Changed in: libpipeline (Ubuntu)
Status: Fix Committed => F
In fact, upon trying to do this in libpipeline, I've changed my mind:
tolerating this situation there is far too fiddly and fragile. I've
therefore decided to document this restriction instead, given that it's
already fixed in man-db:
https://git.savannah.gnu.org/cgit/libpipeline.git/commit/?id=f
On the man-db side, this is no longer an issue as of man-db 2.8.6
(Ubuntu 19.10 and newer), which ensures that the standard file
descriptors are open.
It would probably still be helpful (if cumbersome) for libpipeline to
tolerate this situation.
** Changed in: man-db (Ubuntu)
Importance: Undec
** Also affects: man-db (Ubuntu)
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/992271
Title:
man command not working in lynxcgi script
To manage notifica
Thanks for your report, and sorry for my delay!
The distinguishing feature here is that lynx closes the CGI script's
standard input. As a result, at some point man does roughly:
last_input = open (filename, O_RDONLY);
dup2 (last_input, 0);
close (last_input);
But the "open" returns 0, sin
** Attachment added: "Zipped debug output for man -d under lynx and under w3m"
https://bugs.launchpad.net/bugs/992271/+attachment/3121454/+files/debug.zip
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bu
