[Bug 180368] Re: gdbm fatal: lseek error

2008-01-12 Thread Terence Simpson
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

[Bug 180368] Re: gdbm fatal: lseek error

2008-01-07 Thread James McDonald
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-univers

[Bug 180368] Re: gdbm fatal: lseek error

2008-01-07 Thread zjaak
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.ubunt

[Bug 180368] Re: gdbm fatal: lseek error

2008-01-06 Thread Rich
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 bec

[Bug 180368] Re: gdbm fatal: lseek error

2008-01-06 Thread Rich
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 obviou

[Bug 180368] Re: gdbm fatal: lseek error

2008-01-06 Thread Terence Simpson
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 rep

[Bug 180368] Re: gdbm fatal: lseek error

2008-01-06 Thread Sarah Hobbs
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 b

[Bug 180368] Re: gdbm fatal: lseek error

2008-01-05 Thread mattismyname
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-bug

[Bug 180368] Re: gdbm fatal: lseek error

2008-01-05 Thread Tommy Mikkelsen
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 mem

[Bug 180368] Re: gdbm fatal: lseek error

2008-01-05 Thread Rene Pärts
[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://li

[Bug 180368] Re: gdbm fatal: lseek error

2008-01-04 Thread Michael B. Trausch
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 Yo