Timeline for Do we need a tool to help users providing information on their system?
Current License: CC BY-SA 3.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jan 9, 2013 at 3:51 | comment | added | Mateo | I'll do that next time @EliahKagan , this usage would give me reason to reinstall it. | |
| Jan 9, 2013 at 2:47 | comment | added | Eliah Kagan | @mateo_salta That would likely not be an impediment to your using the hypothetical maybe-or-maybe-not-extremely-useful tool being discussed here. It seems to me that the new information reporter utility would more likely be a derivative work of Apport, or a totally new program, than a wrapper that requires Apport itself to be installed. Furthermore, removing Apport is totally unnecessary--you can get rid of all the messages by disabling just its automatic crash reporting functionality. | |
| Jan 9, 2013 at 1:38 | comment | added | Mateo | except, I removed apport from my system to avoid vague crash messages. | |
| Jan 9, 2013 at 0:49 | comment | added | Eliah Kagan | When you say we don't need to collect debugging data, perhaps you mean we don't need to collect stack traces and related technical data from program crashes? The rest of the data Apport collects seems quite relevant to providing support. I don't know if automated data collection will prove necessary or useful for Ask Ubuntu, but if we're going to do it, it seems the task is largely already done in Apport. A related approach would be not to rely on Apport or use any of its code, but to write a new app that uses packages' apport hooks, so it automatically collects the same data as Apport. | |
| Jan 8, 2013 at 21:51 | comment | added | gertvdijk | +1 for mentioning to reuse stuff from Apport. Great suggestion. This could make a new application even thinner and just a flat UI skin. Good. Good. Good. | |
| Jan 8, 2013 at 21:48 | history | answered | Rafał Cieślak | CC BY-SA 3.0 |