LinuxQuestions.org

LinuxQuestions.org (/questions/)
-   Slackware (http://www.linuxquestions.org/questions/slackware-14/)
-   -   Errors when invoking certain manpages (http://www.linuxquestions.org/questions/slackware-14/errors-when-invoking-certain-manpages-4175440438/)

jstg 12-07-2012 08:28 AM

Errors when invoking certain manpages
 
I'll try to describe my problem as best I can.

When invoking certain manpages (man bash and man gcc for example) the manpage displays but after hitting 'q' to return to my prompt I get

Code:

gzip: stdout: Broken pipe

gzip: stdout: Broken pipe
grotty:<standard input> (<standard input>):105371:fatal error: output error

My OS is Slackware 14 I'm using i3 as a window manager. However, if I use man bash in Fluxbox I don't get that error. If I use man bash in the console I don't get that error. 'echo $TERM' in i3 returns xterm and in the console 'echo $TERM' returns linux.

It appears to be harmless since I can still read the manpage but it is quite annoying.

Thanks for your help.

brianL 12-07-2012 09:44 AM

I can't help with your problem, but I suggest you hit the Report button and ask for this thread to be moved to the Slackware forum.

jstg 12-07-2012 09:46 AM

I wasn't sure if it was Slackware specific or not. I'll try getting it moved though.

colucix 12-07-2012 01:38 PM

Moved: This thread is more suitable in Linux - Slackware and has been moved accordingly to help your thread/question get the exposure it deserves. As per request.

ljb643 12-07-2012 05:37 PM

Try this:
Quote:

man -d gcc
The end parts of the output will tell you what commands 'man' is trying to run to format and display the manual page. It might help troubleshoot.

Do you get the same thing if you let the man page run to the end, rather than 'q' before it is done? (I realize those are very long pages.)

Is man using "less" to display the man pages? What are these environment variables set to: PAGER MANPAGER LESS ?

jstg 12-07-2012 05:45 PM

Quote:

Originally Posted by ljb643 (Post 4844875)
Try this:

The end parts of the output will tell you what commands 'man' is trying to run to format and display the manual page. It might help troubleshoot.

Do you get the same thing if you let the man page run to the end, rather than 'q' before it is done? (I realize those are very long pages.)

Is man using "less" to display the man pages? What are these environment variables set to: PAGER MANPAGER LESS ?

man -d gcc returns:

Code:

/home/jstg $ man -d gcc
Reading config file /usr/lib/man.conf
found man directory /usr/man
found man directory /usr/share/man
found man directory /usr/local/man
found man directory /usr/local/share/man
found man directory /usr/X11R6/man
found manpath map /bin --> /usr/share/man
found manpath map /sbin --> /usr/share/man
found manpath map /usr/bin --> /usr/share/man
found manpath map /usr/sbin --> /usr/share/man
found manpath map /usr/local/bin --> /usr/local/share/man
found manpath map /usr/local/sbin --> /usr/local/share/man
found manpath map /usr/X11R6/bin --> /usr/X11R6/man
found manpath map /usr/bin/X11 --> /usr/X11R6/man
found manpath map /usr/bin/mh --> /usr/share/man

using /usr/bin/less -is as pager

using /usr/bin/lynx as browser

using /usr/bin/lynx -dump to dump HTML pages as text
adding /usr/local/man to manpath
adding /usr/man to manpath
adding /usr/share/texmf/man to manpath

gzip: stdout: Broken pipe
no cat page stored because of nonstandard line length

gzip: stdout: Broken pipe
using default preprocessor sequence
found tbl(1) directive
man:
not executing command:
  (cd "/usr/man" && (echo ".ll 12.7i"; echo ".nr LL 12.7i"; echo ".pl 1100i"; /bin/gunzip -c '/usr/man/man1/gcc.1.gz'; echo ".\\\""; echo ".pl \n(nlu+10") | /usr/bin/gtbl | /usr/bin/nroff -mandoc | /usr/bin/less -is)

If I type in man bash or man gcc then scroll to the bottom I get the same error minus the bit about grotty. I just get the gzip: stdout: Broken pipe.

echo $PAGER and echo $MANPAGER return nothing. echo $LESS returns -M

ljb643 12-07-2012 09:27 PM

I don't know why you are seeing those errors, but I have a little info if you or anyone else wants to try to figure this out.

Even "man -d", which doesn't actually format and display the man page, still runs "gzip -d -c" on the man page source. (That explains why you are getting the errors even with "man -d".) If I trace "man -d", I see the gzip process, and it does stop with a broken pipe error (EPIPE) - this just means the pipe reader closed its end before gzip was done. I assume this is the normal behavior for "man". The question is why is that error reported with that window manager, rather than ignored as it is for me, and for you with console or other window managers. I have no ideas on this.

jstg 12-08-2012 08:04 AM

At this point I can only imagine this problem is somehow i3 specific since I cannot recreate it in Fluxbox or in the console. Both i3 and Fluxbox are running under the same resolution with the same .Xresources file. However, xterm is called with alt-F1 in Fluxbox and in i3 super+return launches a "sensible terminal" which shows xterm when I echo $TERM.

Also not sure if it's related but if I'm using i3 as my regular user and launch a terminal and su - to root, when I first run slackpkg I get lots of grep write errors and sed write errors. Again these problems are not present in the console or with Fluxbox.

jstg 12-08-2012 09:13 AM

I tinkered around a bit more. If I run 'man bash' under tmux I don't get the errors either.

padeen 01-07-2013 10:03 PM

I'm late to the party, but I get this error also. I only get it on some man pages though.

On a console, vanilla xterm, or under tmux man pages display fine. On a yeahconsole (like a quake console), I get the error for some man docs. Environment variables except for TERM are identical.

In man(1) there are about 226 of 2815 man docs that produce the error.

jstg 01-08-2013 12:00 AM

Quote:

Originally Posted by padeen (Post 4865106)
I'm late to the party, but I get this error also. I only get it on some man pages though.

On a console, vanilla xterm, or under tmux man pages display fine. On a yeahconsole (like a quake console), I get the error for some man docs. Environment variables except for TERM are identical.

In man(1) there are about 226 of 2815 man docs that produce the error.

I never could get it to work right using xterm + i3. I also had problems using spectrwm as well. I managed to get it 'fixed' under spectrwm. In my spectrwm.conf if
Code:

baraction = conky
then I would get the broken pipe error. If I commented out the baraction section the man pages display fine.

padeen 01-08-2013 03:26 AM

I'm using spectrwm too, but commenting out baraction doesn't fix it for me.

It's more an annoyance than a problem. As far as I remember, it didn't exhibit this behaviour under 13.37.


All times are GMT -5. The time now is 03:12 AM.