On 9/7/07, David Tomaschik <[EMAIL PROTECTED]> wrote: > > What kind of builds were you running? Standard makes, or something deb- > oriented? Were any apt upgrades being performed?
I suppose it's possible that "apt-get update" was running. That runs automatically every day I think. Would that explain the files going missing for several seconds? It's not like I only saw the error once - I had time to research which command bash was running and run it manually, and it was still broken. If this is caused by an "apt-get update" running automatically in the background then apt-get should be fixed to make sure it leaves the required files in place until it is really ready to replace them. Could it be that it deletes them before fetching replacements from the network or something? -- errors from command-not-found https://bugs.launchpad.net/bugs/137939 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
