Thank you for taking the time to review this bug. I am quite new to Ubuntu bug reporting as an activity so please bear with me while I present a more robust case. In my weak attempt to provide a short-term solution I think I diluted the strength of my message.
Due to the fact that this usability bug prevents the user from taking a next step and completing their intended task I believe it should be reclassified.
As it stands, any non-technical user is not likely to expand the details and, in the unlikely event that they do, the language and presentation of the error message is a significant barrier to them recovering from the error.
There is a difference between a usability bug which prevents a user from completing their task and one where the experience could be improved. This error message definitely falls into the former.
I suggest that at the very least the short-term solution I propose should be implemented and that a design which includes a more appropriate icon and open and available steps for recovery should be implemented.
Hi Dominik,
Thank you for taking the time to review this bug. I am quite new to Ubuntu bug reporting as an activity so please bear with me while I present a more robust case. In my weak attempt to provide a short-term solution I think I diluted the strength of my message.
Due to the fact that this usability bug prevents the user from taking a next step and completing their intended task I believe it should be reclassified.
As it stands, any non-technical user is not likely to expand the details and, in the unlikely event that they do, the language and presentation of the error message is a significant barrier to them recovering from the error.
If we take a look at the GNOME Human Interfaces Guidelines on Warning and Error messages (http:// library. gnome.org/ devel/hig- book/stable/ language- errors. html.en) this error message clearly does not conform.
There is a difference between a usability bug which prevents a user from completing their task and one where the experience could be improved. This error message definitely falls into the former.
A fairly widely used list of usability heuristics (http:// www.useit. com/papers/ heuristic/ heuristic_ list.html) includes Error prevention and Help users recognize, diagnose, and recover from error.
I suggest that at the very least the short-term solution I propose should be implemented and that a design which includes a more appropriate icon and open and available steps for recovery should be implemented.
Sorry I wasted your time the first time!