You are not logged in.

#1 2009-07-22 14:42:16

interskh
Member
From: pittsburgh
Registered: 2008-10-23
Posts: 45

"gdbm fatal: lseek error" with manpages

i got "gdbm fatal: lseek error" when i "man" anything..

i tried to rebuild manpage index by "mandb -c"
but they gave me a bunch of warnings like this

mandb: warning: /usr/share/man/man3x/FcStrSetAdd.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/glGetTexGendv.3gl.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/wmemmove.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/gnutls_certificate_set_x509_key_file.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/XkbGetIndicatorChanges.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/XMaskEvent.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/libpngpf.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/asctime.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/OBJ_cleanup.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/cprojf.3p.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/fssetdm_by_handle.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/ldap_first_message.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/ldap_next_entry.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/trunc.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/glMultiTexCoord4ivARB.3gl.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/ber_flush.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/curl_multi_timeout.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3x/pam_sm_close_session.3.gz: ignoring bogus filename
mandb: warning: /usr/share/man/man3/CPAN::HandleConfig.3perl: whatis parse for CPAN::HandleConfig(3perl) failed
mandb: warning: /usr/share/man/man3/CPAN::Tarzip.3perl: whatis parse for CPAN::Tarzip(3perl) failed

any advices are appreciated... thanks!


o.O

Offline

#2 2009-07-22 19:43:23

djszapi
Member
From: Cambridge, United Kingdom
Registered: 2009-06-14
Posts: 1,439
Website

Re: "gdbm fatal: lseek error" with manpages

After a total core/man-pages with its dependency ? (You need to delete it before)

Offline

#3 2009-07-23 04:05:14

interskh
Member
From: pittsburgh
Registered: 2008-10-23
Posts: 45

Re: "gdbm fatal: lseek error" with manpages

@djszapi  u mean remove and re-install it? just tried, didnt work sad


o.O

Offline

#4 2009-08-13 14:17:59

nshalman
Member
Registered: 2009-08-13
Posts: 1

Re: "gdbm fatal: lseek error" with manpages

I ran into the same problem, and this thread was high on the list of matches so I'm posting my solution for posterity:

How I solved this:
I ran "strace man man" and discovered that it was looking for manpages corresponding to a directory in my $PATH
that didn't have one.  Fortunately for me it was an extra directory added to my path from old development that I'm not currently doing.
Removing that directory from my $PATH variable (as configured in my ~/.bashrc file) cleared up the problem.

So, between

$ strace man man

and

$ echo $PATH

you should be able to track down the culprit.

I hope this helps!

Offline

#5 2009-10-31 04:02:43

cb474
Member
Registered: 2009-04-04
Posts: 469

Re: "gdbm fatal: lseek error" with manpages

I'm getting a lot of "bogus filename" and "failed" errors like in the first post of this thread. I tried running strace man man and didn't really know what to make of the output, it was a bit beyond me. "echo $PATH" gives me:

/bin:/usr/bin:/sbin:/usr/sbin:/usr/lib/icecat:/usr/bin/perlbin/site:/usr/bin/perlbin/vendor:/usr/bin/perlbin/core

I don't know what to do with that information either. And I don't see anything about "$PATH" in my .bashrc. Could somebody spell out for me a little more what I'm looking for and trying to change here? Thanks.

Offline

#6 2011-02-10 08:54:57

hcs
Member
Registered: 2011-02-10
Posts: 2

Re: "gdbm fatal: lseek error" with manpages

I also got the lseek error, in my case the problem was a index.db file in one of the man dirs, everything works after removing it.

Offline

Board footer

Powered by FluxBB