Sometimes a user asks a question and shows the error message, and the error message clearly indicates that there is a bug in the application. If it weren't for the bug, that message wouldn't be shown. So we know there's a bug that ought to be reported.
This happens most often when the message shows a stack trace, a traceback, when it is an Apport window, or when it is indicating termination by a crash-denoting singal (e.g., "segmentation fault`).
Usually, filing the bug is all there is to do. So the question is simply off-topic, and we urge people to report the bug.
Sometimes, there are possible workarounds, but they are workarounds relating to the bug, and would be meaningless if the bug were fixed. In these cases, the workarounds belong on the Launchpad (or other) bug pages, and we still close as off-topic.
Occasionally, the program would still not work--or could reasonably not work--even if the bug were fixed. This happens when the bug is triggered by a problem that would prevent it from continuing anyway.
That's actually a pretty large class of bugs--bugs programmers ended up shipping to end users because they only occur when the "user does something wrong."
I'm asking about this because there's a question up for closure (or reopening, depending on what happens between when I write this and you read it) where this applies:
The bug (at the bottom of the text--the error-like text at the top doesn't mean anything) is that when Wubi gets a 404 error attempting to download an Ubuntu ISO image, it cannot handle this, and it crashes. Clearly that's a bug and should be reported.
However, the cause of the 404 message in this instance that the user is attempting to install Ubuntu 11.04 with Wubi. Ubuntu 11.04 is no longer supported (it is an end-of-life release), so its ISO images are not present on the
releases server which Wubi is connecting to.
They are present on the
old-releases server and one reasonable option for fixing the bug would be to make it automatically fetch EoL images from
However, since using an EoL release is not a great thing to do, I think it's also quite reasonable to fix the bug just by making Wubi it fail with an error message and terminate normally.
So the fundamental question about how to install Wubi still applies. It's possible to give an answer to the question that explains:
- What's causing the error. (Which would still occur even if Wubi hadn't crashed.)
- How to get Wubi installed. There are many ways, but the good ones are to download the ISO manually and put it in the same directory as the Wubi executable, or to install Wubi from a burned/written Ubuntu CD/DVD/USB.
- To strongly consider using a supported release of Ubuntu in one's Wubi system, and the reason this is a good idea. (Or linking to a source that provides this information.)
So, should this question be answered? Or should it be closed?