Error reporting for Click packages
https:/
What's the crash reporting experience for click packages? How do they provide us with debugging symbols? How do they record recoverable errors? How do we ensure that the crash data from proprietary applications stays private?
Blueprint information
- Status:
- Not started
- Approver:
- Steve Langasek
- Priority:
- Undefined
- Drafter:
- Evan
- Direction:
- Approved
- Assignee:
- Evan
- Definition:
- Pending Approval
- Series goal:
- Accepted for utopic
- Implementation:
-
Unknown
- Milestone target:
-
ubuntu-14.10
- Started by
- Completed by
Related branches
Related bugs
| Bug #1324853: interface to get manifest corresponding to file in installed package | Fix Released |
Whiteboard
Another open question brought up by Sergio Schvezov is: how do we deal with "descriptive bugs" being reported through ubuntu-bug.
Work Items
Work items:
[beuno] stand up a symbol server: TODO
[beuno] figure out symbol server access control requirements: TODO
[beuno] figure out symbol server garbage collection: TODO
[cjwatson] click SDK handling for symbol extraction: TODO
[cjwatson] follow up with SDK team about QtCreator integration: TODO
apport/whoopsie integration to identify click package/version corresponding to crash file: TODO
daisy integration to talk to appropriate server: TODO
[ev] apis to access errors from MyApps: TODO
click vs. deb filtering on errors.u.c: TODO
