Bug #4287

Separate user error messages from developer error messages.

Added by David Welker about 13 years ago. Updated over 10 years ago.

In Progress
Target version:
Start date:
Due date:
% Done:


Estimated time:


An error in the GUI should never display a nonsensical stack trace to the user. All stack traces involving the GUI and other errors made to be read by the developer should be logged to file (and optionally standard out).

null.tiff (25.6 KB) null.tiff Chad Berkley, 08/13/2009 11:09 AM
broken dialog.tiff (42.4 KB) broken dialog.tiff Chad Berkley, 08/13/2009 11:12 AM

Related issues

Blocked by Kepler - Bug #4286: Changes to the GUI before 2.0Resolved08/07/2009


#2 Updated by Chad Berkley about 13 years ago

Need to check all error messages to make sure they make sense and that an appropriate message is actually displayed. Many errors just return a dialog that says "null" (see attachment 1).

Many error message are too long for the dialog box and the layout gets cut off. Error messages should resize the dialog so that they message fits. (See attachment 2).

#4 Updated by Christopher Brooks about 13 years ago

The way to fix this bug is that each time a nonsensical error message
appears, then we need to know what the stack trace is and how to
reproduce the bug.

For the "A ridiculous error message" at
we would need to know how to reproduce it and what the stack trace is.

For "error dialog that is cut off" at
This could be associated with "Error message with selectable text"
I would need to know how to reproduce this dialog.

#5 Updated by Chad Berkley about 13 years ago

Pushing to 2.x.y when we will make other gui changes.

#6 Updated by Redmine Admin over 9 years ago

Original Bugzilla ID was 4287

Also available in: Atom PDF