Description Dirk Wiesenthal 2013-12-13 12:18:34 CET

In UCS 3.2 we introduced a traceback reporting tool.

Problem is that the tracebacks are not very meaningful. Sometimes they cannot: A meaningful traceback may expose confidential data, e.g. failed LDAP queries.

As tracebacks give really weak test experience, it might be useful to add another mechanism for selected code regions:
  A new UMC_Error that presents a dialogue to the user with a slightly improved layout:
  "The command %s failed. The following steps may help to solve the problem:
     * Updates are available. Install them first.
     * %s
     * %s
  If the error persists, hints about the cause can be found in the following log files:
     * %s
     * %s
  The following sections in the online documentation and the support database cover %s:
     * %s
     * %s
  If you have a maintenance contract with Univention, you can also contact the support, otherwise you may ask in the forum or send the traceback (along with the log files) to Univention."

Advantage: Feels better (we present solutions); does not look too technical and broken, more like "correct error handling" of a known issue.

Disadvantage: Hides the prominent "Send traceback" which may reduce feedback rate. Maybe a possible solution (e.g. a restart of the service) really works: We will never know of the initial problem (which may affect several more people).