These are some of the funny, sarcastic, or just plain stupid error messages that you might see. If you are looking for "proper" error messages from applications, and how to resolve them, look at ApplicationErrorMessages.
Many BIOSes will report this error if a keyboard is not found at boot time.
The Linux lp# driver says this when your printer signals an error, but doesn't signal which error. Usually this means the printer is offline. (This message was copied from much earlier line printer daemons from Unixes of old.)
Update: Kernel 2.4.20 contains the following change from 2.4.19:
diff -urN linux-2.4.19/drivers/usb/printer.c linux-2.4.20/drivers/usb/printer.c --- linux-2.4.19/drivers/usb/printer.c Fri Aug 2 17:39:45 2002 +++ linux-2.4.20/drivers/usb/printer.c Thu Nov 28 15:53:14 2002 @@ -257,7 +257,7 @@ * Get and print printer errors. */ -static char *usblp_messages[] = { "ok", "out of paper", "off-line", "on fire" }; +static char *usblp_messages[] = { "ok", "out of paper", "off-line", "unknown error" };
A Microsoft Windows error message as reported by comp.risks 21.37
This message appears for certain unix programs when an entry can't be found for you in /etc/passwd (or these days, via PAM). This might be because you've not logged in via login(1) (this can happen if /etc/inittab specifies a program that doesn't log you in, instead of getty(8)), if your machine can't retrieve the data from the network (if you are using NIS or LDAP or some other network user administration system) or if you've made a mistake editing /etc/passwd (or friends).
bibtex(1) style files use an undocumented language called BST (or that's the file extenstion, which is the closest it has to a name). In this language recursion is prohibited, and this is the message you get if you try it.
If you tell GDB to try to attach to its own process. (It can't run it and breakpoint it and the same time.)
Seen from the mdir(1) command.
Software Installation encountered an unexpected error while reading from the MSI file \\mlc1\deploy\FireFox-1.0.1-enUS.msi.
The error was not serious enough to justify halting the operation.
The following error was encountered: The operation completed successfully.
If the insults flag is set in /etc/sudoers, sudo(1) will return one of the following errors when an invalid password is entered:
(Taken from ins_*.h in the source for sudo 1.6.6)
See also:
Part of CategoryFunny, CategoryErrors
2 pages link to FunnyApplicationErrorMessages: