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

[Paul Crawford]

The $PATH variables are different, with the 12.04 (32-bit) system having
/packages/local/bin included in the list. If I remove that from the
12.04 system it then avoids the /packages/local/share/man/index.db file
and it works.

However, if I add /packages/local/bin to the 10.04 system (64-bit, in
case it matters) it takes noticeably longer to present the page, and it
reads the /packages/local/share/man/index.db file (according to strace),
but it still works!

So we have found why they the accounts behave differently, but there
still seems to be an issue where the 12.04 system is not handling the
network mounted index.db file correctly, or at least, not handling
database/format errors in any sort of elegant manner.

-- 
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