Germany
Started on: 2007-01-18
last update: 2007-01-18
Summary:
When mediaportal isn't normaly closed because of a crash or so, a report including all log files and configuration settings is send to a web site where the developers may analyse this information
Area:
complete mediaportal
Description:
Roaming around this forum I've seen many posts where people say "MP dosen't work at all" (one of this threads is from me
) and the core team members say "we need more information to help you. Without log files we can not help you". In other threads the developer asks generally for more log files to find situations they haven't thought about jet and so on. It seems to be a general lack of information about the problems useres have with mediaportal.
To get more informations about the installations out there and to make it easier for the user to post bug reports, I suggest that an automatic crash reporter is developed for mediaportal.
How it may work:
When the program is ended normaly, a flag is set in the configuration settings. If the mediaportal crashes abnormaly or a reboot of the whole mashine is made without terminating mediaportal normaly, this flag will not be set.
On startup of the mediaportal application, first this flag will be checked. If it is not set, this indicates, that mediaportal has crashed the last time. In this situation all log files, configuration settings and so on may be collected into a zip file and send back to a web site where the developers and tester may harvest the information. Of cause the user should be asked to allow to send this information back to the community and maybe a text box is displayed to the user, so he can comment the situation which lead to the mediaportal crash.
last update: 2007-01-18
Summary:
When mediaportal isn't normaly closed because of a crash or so, a report including all log files and configuration settings is send to a web site where the developers may analyse this information
Area:
complete mediaportal
Description:
Roaming around this forum I've seen many posts where people say "MP dosen't work at all" (one of this threads is from me
) and the core team members say "we need more information to help you. Without log files we can not help you". In other threads the developer asks generally for more log files to find situations they haven't thought about jet and so on. It seems to be a general lack of information about the problems useres have with mediaportal.To get more informations about the installations out there and to make it easier for the user to post bug reports, I suggest that an automatic crash reporter is developed for mediaportal.
How it may work:
When the program is ended normaly, a flag is set in the configuration settings. If the mediaportal crashes abnormaly or a reboot of the whole mashine is made without terminating mediaportal normaly, this flag will not be set.
On startup of the mediaportal application, first this flag will be checked. If it is not set, this indicates, that mediaportal has crashed the last time. In this situation all log files, configuration settings and so on may be collected into a zip file and send back to a web site where the developers and tester may harvest the information. Of cause the user should be asked to allow to send this information back to the community and maybe a text box is displayed to the user, so he can comment the situation which lead to the mediaportal crash.