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

[Paul Crawford]

The id command shows:

$ id
uid=xxx05(opr) gid=xxx00(local) groups=xxx00(local),4(adm),20(dialout),109(lpadmin),501(operadores),502(vboxuser),xxx03(hrpt),xxx04(dosgroup),xxx07(vboxsf)

(with xxx replacing various numeric values that our sysadmin don't want
on a public forum)

The copy works without issue:

$ \cp --verbose /var/cache/man/index.db /dev/null
`/var/cache/man/index.db' -> `/dev/null'

Where 'cp' is normally aliased to 'cp -ip' so it squawks about /dev/null
existing, and that it can't preserve timestamps, hence the '\cp'.

The obvious permissions are fine, all users can read the file:

$ ls -l /var/cache/man/index.db
-rw-r--r-- 1 man root 634842 May 18 12:30 /var/cache/man/index.db

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