Feature #16066

Cancelling Wipe Available Disk Space feature should provide feedback to user

Added by huertanix 2018-10-18 21:39:18 . Updated 2019-03-21 16:39:43 .

Status:
Rejected
Priority:
Normal
Assignee:
Category:
Target version:
Start date:
2018-10-18
Due date:
% Done:

0%

Feature Branch:
Type of work:
User interface design
Blueprint:

Starter:
Affected tool:
Deliverable for:

Description

The current user flow for cancelling a Wipe Available Disk Space process:

When using the “Wipe Available Disk Space” feature on a 4GB FAT formatted drive, the process seemed to be taking to long so a user cancelled, after which a confirmation dialog appears and “Cancel operation” is pressed. When that happens, the confirmation dialog disappears but the Wipe Available Disk Space dialog is still there, unchanged, and seems like it’s ignoring the cancel request for a period of time close to a minute before a cryptic message finally appears to confirm it was cancelled.

Ideally, this flow should change so that when a user confirms the cancellation, the Wipe Available Disk Space dialog should change to indicate that the cancellation is being processed. This can be as simple as changing the “Wiping available disk space…” copy to “Cancelling…” Instead of seeing a cryptic message when the cancellation kicks in, the displayed cancellation confirmation should just say that the wipe was cancelled.

Subtasks

History

#1 Updated by intrigeri 2018-10-20 09:20:38

  • Assignee deleted (None)

I believe this is a bug in nautilus-wipe. u, do you want to forward this upstream? You don’t have to, in theory help desk (or worst case FT) could/should do it. But since that’s one of the packages you maintain in Debian for Tails, I figured it would be a good opportunity for you to get in touch with the upstream developer.

#2 Updated by Anonymous 2018-10-24 14:07:03

Sure!

#3 Updated by Anonymous 2018-10-24 14:32:18

I’ve contacted the upstream author and opened a wishlist bug here: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=911764

#4 Updated by Anonymous 2018-10-24 14:32:33

  • Status changed from New to Confirmed

#5 Updated by Anonymous 2018-11-02 19:59:17

  • Target version set to Tails_3.12

#6 Updated by anonym 2019-01-30 11:59:35

  • Target version changed from Tails_3.12 to Tails_3.13

#7 Updated by Anonymous 2019-03-18 15:53:03

  • Assignee deleted ()
  • Target version deleted (Tails_3.13)

I don’t expect this to happen: the upstream developer has never replied.
I’m removing this from my plate.

#8 Updated by sajolida 2019-03-21 16:39:43

  • Status changed from Confirmed to Rejected

Then I think we should reject this as a Tails ticket since it’s been reported upstream already.