[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

This bug was fixed in the package gdbm - 1.14.1-2ubuntu1 --- gdbm (1.14.1-2ubuntu1) bionic; urgency=medium * Don't build using dietlibc (universe). -- Matthias Klose Thu, 01 Feb 2018 13:02:01 +0100 ** Changed in: gdbm (Ubuntu) Status: Triaged => Fix

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

This bug was fixed in the package man-db - 2.6.1-2ubuntu1 --- man-db (2.6.1-2ubuntu1) precise-proposed; urgency=low * Avoid fatal errors when opening a 64-bit GDBM database from a 32-bit process (LP: #1001189). * Link with -Wl,--enable-new-dtags, so that LD_LIBRARY_PATH can

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

This all seems to be behaving correctly now, with the version in precise-proposed: man falls back as specified. (accessdb still doesn't work, but there's no way to make it work with the old gdbm and in any case that's a relatively minor issue.) ** Tags removed: verification-needed ** Tags added:

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

** Branch linked: lp:~ubuntu-branches/ubuntu/precise/man-db/precise- proposed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001189 Title: 'man' command fails with lseek error opening

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

Hello Paul, or anyone else affected, Accepted man-db into precise-proposed. The package will build now and be available at http://launchpad.net/ubuntu/+source/man-db/2.6.1-2ubuntu1 in a few hours, and then in the -proposed repository. Please help us by testing this new package. See

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

** Description changed: + [Impact] Sharing a directory containing manual page databases between 32-bit and 64-bit systems can cause man to crash. + [Test Case] Configure a local manual page hierarchy (in ~/.manpath or otherwise), containing a single page. Run mandb over it from a 64-bit

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

** Branch linked: lp:debian/man-db -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001189 Title: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

This bug was fixed in the package man-db - 2.6.2-1 --- man-db (2.6.2-1) unstable; urgency=low * New upstream release: - Optimise apropos when given many arguments (LP: #927028). - apropos prints an error message and returns non-zero when it finds no matches (closes:

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

Not really. I don't want man-db to be in the business of knowing what's local vs. not, and I very much want to preserve the property of having one database per MANDB_MAP entry. I think it would actually be much more complicated to attempt to unwind that - for instance there'd be interesting

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

Mon Jun 18 04:20:41 BST 2012 Colin Watson cjwat...@debian.org Avoid fatal errors when opening a 64-bit GDBM database from a 32-bit process (Ubuntu bug #1001189). * libdb/db_gdbm.c (trap_error): New function. (man_gdbm_open_wrapper): Rearrange interface to call

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

In the long run, migrating all of the DB files to newer ones that identify the size/swap nature is the right approach, however, I wonder if a simpler fix for 'man' which would be useful for current systems would be to keep everything in the in local DB (say the /var/cache/man/index.db file or

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

** Summary changed: - 'man' command fails with lseek error + 'man' command fails with lseek error opening cross-architecture index.db file (on network share) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu.

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

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 Yes... for example, search for the string Is the magic number good? in

[Bug 1001189] Re: 'man' command fails with lseek error opening cross-architecture index.db file (on network share)

** Also affects: gdbm (Ubuntu) Importance: Undecided Status: New ** Changed in: gdbm (Ubuntu) Status: New = Confirmed -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1001189 Title: