Bi-monthly password check does not work
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Déjà Dup |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
Hi,
I get a password test prompt every two months (from what it says). I would put my password in it and it just disappears after I click on "Test"; I get no confirmation that it is ok or that it does not work.
I thought it would complain if I made a mistake so I didn't worry. I decided to test it with a wrong password to see how it reacts and to my surprise it does exactly the same as when I put my real password, it does nothing (no error as expected). I conclude that this feature is broken. I think it should in either case return something (positive or negative).
Thank you.
Here is the requested info:
1. The distribution of Linux you're using:
Ubuntu 16.04 LTS (it reacted the same way with the previous version)
2. The version of deja-dup and duplicity:
deja-dup 34.2-0ubuntu1
duplicity 0.7.06-2ubuntu2
3. The file /tmp/deja-
org.gnome.DejaDup last-restore ''
org.gnome.DejaDup periodic true
org.gnome.DejaDup full-backup-period 90
org.gnome.DejaDup backend 'file'
org.gnome.DejaDup last-run '2016-05-
org.gnome.DejaDup nag-check '2016-03-
org.gnome.DejaDup prompt-check '2015-10-
org.gnome.DejaDup root-prompt true
org.gnome.DejaDup include-list ['$HOME']
org.gnome.DejaDup exclude-list ['$TRASH', '$DOWNLOAD']
org.gnome.DejaDup last-backup '2016-05-
org.gnome.DejaDup periodic-period 7
org.gnome.DejaDup delete-after 0
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
org.gnome.
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):
neither command is the issue.
I can reproduce the dialog just disappearing instead of giving feedback in the correct-password case (bug 1583986). But I can't reproduce it not giving feedback in the wrong-password case.
In that case -- for me -- I get prompted again for my password.