man pages unreadable in current

AxeZ · 12-23-2004, 06:34 PM

I am having weird issues when invoking man pages in slackware-current.
I am regulary updating to current and rhis appeared maybe sometime before Pat got ill and it is still present.
Here is something as a "screenshot"
Yes, man page indeed looks like this

Anyone knows what could be wrong?

Code:

man(1)                                                     man(1)

NAME
       man <E2><88><92> format and display the on<E2><80><90>line manual pages
       manpath <E2><88><92> determine user<E2><80><99>s search path for man pages

SYNOPSIS
       man  [<E2><88><92<E2><88><92>acdfFhkKtwW]  [<E2><80><90<E2><80><90><E2>
<80><90<E2><80><90>path]  [<E2><88><92<E2><88><92>m  system]  [<E2><88><92<E2>
<88><92>p string] [<E2><88><92<E2><88><92>C con�[24m<AD>
       fig_file] [<E2><88><92<E2><88><92>M pathlist] [<E2><88><92<E2><88><92>P pa
ger]  [<E2><88><92<E2><88><92>S  section_list]  [section]
       name ...

DESCRIPTION
       man  formats and displays the on<E2><80><90>line manual pages.  If you spe
c<C2><AD>
       ify section, man only looks in that section of the manual.   name
       is  normally  the name of the manual page, which is typically the
       name of a command, function, or file.  However, if name  contains
       a  slash  (/)  then man interprets it as a file specification, so
       that you can do man ./foo.5 or even man /cd/foo/bar.1.gz.

       See below for a description of where man  looks  for  the  manual
       page files.

trickykid · 12-23-2004, 09:00 PM

You have the updated packages from groff installed along with the latest man pages.. etc? How are you installing slackware-current?

Navaboy · 12-24-2004, 01:45 AM

If your running -current , make sure everythangs -current.
Im running -current everythangs running fine here.

AxeZ · 12-24-2004, 05:33 PM

Groff version installed on my computer is groff-1.17.2-i386-3 which is also in current

I am updating to current using swaret with dependancy checking.

ror · 12-24-2004, 05:40 PM

ouch (at swaret)

mAineAc · 12-24-2004, 05:52 PM

actually this is a udev problem I believe. What kernel are you using?
You could look at /etc/udev/rules.d/udev.rules
in here look for KERNEL="tty[p-za-e][0-9a-f]*", NAME="tty/s%n", SYMLINK="%k"
and change it to KERNEL="tty[p-za-e][0-9a-f]*", NAME="pty/s%n", SYMLINK="%k"
and that should fix the problem.

GuestFox · 12-24-2004, 07:44 PM

Yep, it's a UDEV problem. I haven't checked -current in a few days but I'm sure that's your problem.

See the following thread for a solution (simply updating udev to a current version is the best way to fix your problem). http://www.linuxquestions.org/questi...light=guestfox

Cheers!

EDIT: Never mind, I just re-read your post.

Quote:

I am regulary updating to current and rhis appeared maybe sometime before Pat got ill and it is still present.

AxeZ · 12-25-2004, 10:52 AM

Quote:

Originally posted by mAineAc
actually this is a udev problem I believe. What kernel are you using? http://www.linuxquestions.org/questi...postid=1368659
You could look at /etc/udev/rules.d/udev.rules
in here look for KERNEL="tty[p-za-e][0-9a-f]*", NAME="tty/s%n", SYMLINK="%k"
and change it to KERNEL="tty[p-za-e][0-9a-f]*", NAME="pty/s%n", SYMLINK="%k"
and that should fix the problem.

Here is my udev.rules

# pty devices
KERNEL="pty[p-za-e][0-9a-f]*", NAME="pty/m%n", SYMLINK="%k"
KERNEL="tty[p-za-e][0-9a-f]*", NAME="pty/s%n", SYMLINK="%k"

I dont think this is the problem.
My udev version is udev-042-i486-1 and as i said I am updated to lates current.