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

[Nathan Stratton Treadway]

On Sun, May 20, 2012 at 18:27:11 -0000, Paul Crawford wrote:
> 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.

Okay, moving on to this question...  it turns out there is an "accessdb"
command included with the man-db package that dumpts the contents of a
database file.

So, what happens when you run
  $ /usr/sbin/accessdb /packages/local/share/man/index.db
on your two machines?  

I'm guessing it will fail on at least the Precise machine, but if it
succeeds on both, does it produce the same output in both cases?

What do the $mtime$ and $version$ fields show?  (Looks like
Debian/Ubuntu have had $version$ of "2.4.1" for quite a while.)

                                                        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