[Bug 1001189] Re: 'man' command fails with lseek error

[Nathan Stratton Treadway]

On Sun, May 20, 2012 at 16:47:21 -0000, Paul Crawford wrote:
> One thing I noticed that is different is $PATH but I expected that to be
> the search order for programs, not for mand pages and/or index.db files!

Actually, I see that man-db does do some mapping between $PATH and the
man-page directory trees...

What are the $PATHs for your "opr" and a no-error account on the Precise
machine?  Is $PATH for "opr" on your Lucid machine the same as on the
Precise machine?


Do you have any idea how the /package/local/share/man/index.db file was
originally generated?   (Could it have been generated on some non-Linux
system, for example.)

                                                Nathan

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to man-db in Ubuntu.
https://bugs.launchpad.net/bugs/1001189

Title:
  'man' command fails with lseek error

Status in “man-db” package in Ubuntu:
  New

Bug description:
  When trying to look up the on-line documentation using the 'man'
  command it fails on 12.04 with lseek error. For example:

  $ man resolvconf
  gdbm fatal: lseek error

  This lseek error applies to other requests as well (e.g. ls, fdisk,
  etc). System information is:

  $ lsb_release -rd
  Description:	Ubuntu 12.04 LTS
  Release:	12.04

  apt-cache policy man
  man:
    Installed: (none)
    Candidate: (none)
    Version table:

  However, it is installed since it runs as a command, and I find:

  $ which man
  /usr/bin/man

  $ man --version
  man 2.6.1

  What I expect is to read the manual page appropriate to the
  command/program, and not get a software error.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/man-db/+bug/1001189/+subscriptions