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

[Paul Crawford]

It seems this dumbness has been recognised since 2005 according to this
bug report, but not taken seriously:

https://bugzilla.redhat.com/show_bug.cgi?id=162416

Apparently "gdbm-1.9.1 (already in Rawhide) provides different magic
values for 32 and 64 bits, so we can discover what system the file was
created on if we use this new version", though I see that Ubuntu 12.04
is still using an older version:

$ apt-cache policy libgdbm3
libgdbm3:
  Installed: 1.8.3-10
  Candidate: 1.8.3-10
  Version table:
 *** 1.8.3-10 0
        500 http://gb.archive.ubuntu.com/ubuntu/ precise/main i386 Packages
        100 /var/lib/dpkg/status


** Bug watch added: Red Hat Bugzilla #162416
   https://bugzilla.redhat.com/show_bug.cgi?id=162416

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