https://bugs.kde.org/show_bug.cgi?id=398235
--- Comment #2 from Michael Pyne <mp...@kde.org> --- kdesrc-build-setup has used output-fd since I wrote it in 2011, as far as I can glean from git. My memory is not *that* good as to say why but the dialog(1) manpage explains that dialog(1) normally writes to stderr, which might mix with error messages from dialog(1), if any. Using --output-fd would ensure that any output that is received is related to the user input. By default dialog(1) does not write to stdout, but to stderr instead. stdout is used to drive the TTY after all (though it seems dialog(1) can try to reopen the TTY even if you ask for output to go to stdout). You may also try adjusting the value for $^F on line 57 to something higher than 4 (e.g. 5 or even 10 or 15). The value chosen here is used by Perl to set which file descriptors should *not* be closed-on-exec. 4 should be sufficient but if your configuration involves extra file descriptors being open, or randomizes descriptor values, you may need to adjust this value to be >= whatever the pipe(2) call would be returning here. As an alternative, it might be easier to just fallback to a readline-based interface if dialog(1) fails? -- You are receiving this mail because: You are watching all bug changes.
