Distribution: Hardware Environment: N/A Software Environment: N/A Problem Description: "man <word>" cause error in "less" when "less" is a default pager Steps to reproduce: just set up "less" as pager and type "man ping"
I have the same problem. It appears on only one machine of 2, where I have tested. It also seems to be related with other problem mentioned in linux-kernel mailing list (http://www.ussg.iu.edu/hypermail/linux/kernel/0411.2/0510.html). I see either both or none of them. 1) AtlonXP 1800+ with 512Mb: doesn't appear (less works as expected, also recently mentioned problems with SSH doesn't appear). 2) Pentium-4 with 1Gb RAM: I can reproduce problems both with less and SSH. As far as I have verified, kernel 2.6.9-rc1 doesn't have this problem, but 2.6.9-rc1-bk5, 2.6.9-rc1-bk10, 2.6.9-rc2, 2.6.9, 2.6.10-rc2 have
Created attachment 4078 [details] strace output when less fails strace output when less fails. The end of it realted to /dev/tty is really strange and seems to be wrong. Such strange error reports doesn't appear on other machine where I tested, only ono one of two. Command: ls -lR | strace -o less_strace.log less
Created attachment 4113 [details] Difference between 2.6.9-rc1-bk1 and 2.6.9-rc1-bk2 which causes this problem Reverting this patch (differnce between 2.6.9-rc1-bk1 and 2.6.9-rc1-bk2) fixed the problems both with less and SSH with kernel 2.6.9 for me.
Repeatable results with kernel 2.6.9 on 3 machines: Athlon 650 'Classic', VIA chipset, less and ssh don't work Athlon 2500+, VIA chipset, less and ssh work fine Pentium 4 2.6C, Intel ICH5 chipset, less and ssh don't work I may be able to provide kernel .config's, logs, etc
Reproduced again with 2.6.10. As earlier, reverting the same patch fixes the problem.
Created attachment 4449 [details] Possible fix for this problem. At list this small patch fixed the problem with kernel 2.6.10 for me. At least I saw this problem with unchanged 2.6.10. After applying patch and rebuilding kernel problem no more appeared
this patch is wrong.
Any updates, has the problem been resolved? Thanks.
Since no complaints/updates I am closing the bug. Please reopen if needed.