Triaging Déjà Dup Bugs

Priority

  • Critical: Bugs that prevent restoring, create data loss, or crash Déjà Dup

    • If restore-prevention bug has an in-program workaround, drop to High

    • If restore-prevention bug is for a non-supported workflow (like full system restore), drop to Medium

  • High: Bugs that prevent backing up or cause promised functionality to not work

    • If backup-prevention bug is for a non-supported workflow (like full system backup), drop to Medium

  • Medium: Bugs that annoy users or cause them to jump through hoops

  • Low: Bugs that don't stop any interaction or aren't very visible

  • Wishlist: Anything that is not strictly a bug (feature requests, changes in behavior)

Tags

  • restore: for a restore-only problem

  • backup: for a backup-only problem

  • gnome-shell: for a problem only affecting the GNOME Shell interface

  • needs-design: for a feature that needs user experience design work

Requesting Info

1. The distribution of Linux you're using:
    lsb_release -d

2. The version of deja-dup and duplicity:
    (if on Ubuntu or Debian:)
    dpkg-query -W deja-dup duplicity

    (if on Fedora or other RPM-based systems:)
    rpm -q deja-dup duplicity

3. The file /tmp/deja-dup.gsettings after running the following line (you may want to scrub the file of any incriminating file names or details):
    gsettings list-recursively org.gnome.DejaDup > /tmp/deja-dup.gsettings

4. The file /tmp/deja-dup.log after running the appropriate line below and replicating the problem (you may want to scrub the log of any incriminating file names or details):

 * If you're having problems backing up:
    DEJA_DUP_DEBUG=1 deja-dup --backup | tail -n 1000 > /tmp/deja-dup.log

 * If you're having problems restoring:
    DEJA_DUP_DEBUG=1 deja-dup --restore | tail -n 1000 > /tmp/deja-dup.log

Apps/DejaDup/GettingInvolved/Triage (last edited 2013-08-14 14:40:19 by WilliamJonMcCann)