1

I don't know if this is possible, but if desktop files are simple starting by single process (i think KDED), then it should been possible.

Idea is about create a session daemon, which allow programs to register failure exit codes, monitor processes (catch exit events), allow to register path of log files and show dialog asking to display log file , when exit code is bad (registered).

This dialog could also allow to attach log to e-mail and send it to developers.

For better clarify. Applications can put special parameter to .desktop file, which order it to put log into file, so user still can ran application via terminal. Difference is in running app from .desktop file. In this case, application will tell that exit code 2 means failure and log file will be put in ~/coll_game.log (for example).

Two remarks:

1. I see a technical issue here, logs are typically written on a "write and forget" base, no memory is kept inside the application. Reason is that logging should always be as simple as possible, simple in the sense of risk free.
That means that those logs are not available any longer at a given point in time when your event would occur, except if they were written to a log file. Which makes the process obsolete because the whole suggestion is about logging into a file.

2. you can already redirect or append application log output to log files by means of a simple CLI stream rediretion. If you want that permanently, then just create an alias or a wrapper around the application.

So maybe add new .desktop file field, so user could right click and select debug or Plasma5 ask to relaunch application, which exits with error?