[Bug 180368] Re: gdbm fatal: lseek error
I believe this was fixed in 0.2.12ubuntu1 ** Changed in: command-not-found (Ubuntu) Status: Confirmed = Fix Released -- gdbm fatal: lseek error https://bugs.launchpad.net/bugs/180368 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180368] Re: gdbm fatal: lseek error
So how did you fix it Rich.. Commands?? -- gdbm fatal: lseek error https://bugs.launchpad.net/bugs/180368 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180368] Re: gdbm fatal: lseek error
dpkg -L command-not-found-data to get a list of the files installed ... /usr/share/command-not-found/programs.d/amd64-main.db /usr/share/command-not-found/programs.d/amd64-restricted.db /usr/share/command-not-found/programs.d/amd64-multiverse.db /usr/share/command-not-found/programs.d/amd64-universe.db ... remove the amd64-* files and you are done -- gdbm fatal: lseek error https://bugs.launchpad.net/bugs/180368 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180368] Re: gdbm fatal: lseek error
marking as critical, as it appears that no one can use command-not-found when it is like this. ** Changed in: command-not-found (Ubuntu) Importance: Undecided = Critical Target: None = hardy-alpha-4 -- gdbm fatal: lseek error https://bugs.launchpad.net/bugs/180368 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180368] Re: gdbm fatal: lseek error
Running with python2.5-dbg I get this: $ /usr/bin/python2.5-dbg /usr/lib/command-not-found -- anything KABOOOM!!! Whoops, command-not-found has crashed! Please file a bug report at: https://bugs.launchpad.net/ubuntu/+source/command-not-found Please include the following information with the report: /usr/lib/python2.5/lib-dynload/gdbm.so: undefined symbol: Py_InitModule4 Traceback (most recent call last): File /usr/lib/command-not-found, line 10, in module from CommandNotFound import CommandNotFound File /usr/lib/python2.5/site-packages/CommandNotFound/__init__.py, line 1, in module from CommandNotFound import CommandNotFound File /usr/lib/python2.5/site-packages/CommandNotFound/CommandNotFound.py, line 4, in module import sys, os, os.path, gdbm, posix, grp ImportError: /usr/lib/python2.5/lib-dynload/gdbm.so: undefined symbol: Py_InitModule4 Python version: 2.5.2 alpha 0 [7889 refs] -- gdbm fatal: lseek error https://bugs.launchpad.net/bugs/180368 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180368] Re: gdbm fatal: lseek error
Problem found. command-not-found-data includes the amd64 parts in the i386 version of ubuntu3, though not ubuntu2. gdbm module on i386 throws an lseek error when you try to open those files on i386. Remove the amd64 files and/or downgrade to ubuntu2, and your problems will vanish. This is obviously just a workaround though - gdbm is being dumb. -- gdbm fatal: lseek error https://bugs.launchpad.net/bugs/180368 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180368] Re: gdbm fatal: lseek error
More specifically, it turns out that the 64-bit version of this system call is no longer the same name as the 32-bit version on Python 2.5...or at least, that's what I gathered from Bug 86685. -- gdbm fatal: lseek error https://bugs.launchpad.net/bugs/180368 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180368] Re: gdbm fatal: lseek error
[EMAIL PROTECTED]:~$ asd gdbm fatal: lseek error -- gdbm fatal: lseek error https://bugs.launchpad.net/bugs/180368 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180368] Re: gdbm fatal: lseek error
i can confirm this bug, any questions you might have I can answer as I will not remove 8.04 from my test computer.. =) But a fix would be helpful as I can't even start svn .. -- gdbm fatal: lseek error https://bugs.launchpad.net/bugs/180368 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180368] Re: gdbm fatal: lseek error
Also confirmed when trying to run any program that does not exist in my $PATH -- gdbm fatal: lseek error https://bugs.launchpad.net/bugs/180368 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
[Bug 180368] Re: gdbm fatal: lseek error
I can confirm this bug; was just about to file it myself. Is there any information that can be collected and posted here on this bug to get a fix going? ** Changed in: command-not-found (Ubuntu) Status: New = Confirmed -- gdbm fatal: lseek error https://bugs.launchpad.net/bugs/180368 You received this bug notification because you are a member of Ubuntu Bugs, which is the bug contact for Ubuntu. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
