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

Nathan Stratton Treadway ubuntu.lp at nathanst.com
Sun May 20 21:01:21 UTC 2012


On Sun, May 20, 2012 at 20:07:40 -0000, Paul Crawford wrote:
> But trying this on a 32-bit 10.04 machine (not normally with this file
> available) I get something vaguely familiar:
> 
> $ /usr/sbin/accessdb /packages/local/share/man/index.db
> gdbm fatal: read error
> 
> So it seems the underlying issue is the database has no indication (or
> handling) of 64-bit versus 32-bit data! That seems to me to be a


I can confirm that if I copy /var/cache/man/index.db from a 64-bit
machine to a 32-bit Lucid machine, I get the same error:

  $ uname -m
  i686
  $ lsb_release -r
  Release:        10.04
  $ accessdb mandb_index.db_x86_64 
  gdbm fatal: read error

That same operation on a Precise 32-bit machine fails with a slightly 
different error message:

  $ uname -m
  i686
  $ lsb_release -r
  Release:        12.04
  $ accessdb mandb_index.db_x86_64 
  accessdb: can't open mandb_index.db_x86_64 for reading


Opening this _x86_64 file on a 64-bit Lucid machine works fine.... but
on that machine the _i686 file fails:

  $ uname -m
  x86_64
  $ lsb_release -r
  Release:        10.04
  $ accessdb mandb_index.db_i686 | less
  accessdb: can't open mandb_index.db_i686 for reading: Invalid argument


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

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




More information about the foundations-bugs mailing list