drkonqi debug installer
Open, LowPublic

Description

Workflow

  • App crashes
  • Drkonqi starts
  • Drkonqi complains that the crash data is incomplete
  • Drkonqi offers a button to install stuff to make the data better
  • Installer gets started
  • Installer has 3 states:
    • Looking for packages we can install
    • Offer installation of those packages
    • Installation of packages
  • Once done we return to drkonqi which now reloads data and allows the user to report the bug

Current look

Techno Questions

  • should we maybe use pkgkit to not conflict with discover? (for install probably, for the other parts it doesn't really work... can't add repo (ddebs injection), can't get sourcename of package...)
  • how to handle ubuntu ddebs? should maybe be automatically add the repo and then ask the user if they want to keep it enabled to speed up future debugging?
  • maybe write for multile resolver logics on packagekit, so other distros could use the same thing, not sure that is even possible
sitter created this task.Jul 15 2016, 10:13 AM
sitter updated the task description. (Show Details)
sitter updated the task description. (Show Details)Aug 5 2016, 12:15 PM
sitter updated the task description. (Show Details)Aug 16 2016, 11:02 AM
sitter updated the task description. (Show Details)Aug 19 2016, 9:30 AM

Needs new debug installer written which uses pkgkit

There is a debug installer now, it has no UI though. As in: it entirely relies on the UI drkonqi provides, which is severely limited :(

That's actually what this task is primarily about. the techno aspects at the end are only implementation details of what goes on behind the scenes.

sitter lowered the priority of this task from Normal to Low.Feb 13 2019, 3:37 PM
sitter moved this task from Discussing to Backlog on the Neon board.Aug 12 2019, 1:04 AM