Feature #15951

Inconsistency between doc and actual behaviour: "Unlock VeraCrypt Volumes opens your volume"

Added by intrigeri 2018-09-13 12:23:04 . Updated 2018-10-01 13:29:38 .

Status:
Resolved
Priority:
Normal
Assignee:
Category:
Target version:
Tails_3.9.1
Start date:
2018-09-13
Due date:
% Done:

100%

Feature Branch:
Type of work:
End-user documentation
Blueprint:

Starter:
Affected tool:
Deliverable for:
299

Description

Spotted while writing the test suite, trying to follow the steps we document as closely as possible: in our doc, after unlocking a volume, I read that “Unlock VeraCrypt Volumes opens your volume”. The way I understand it, it should open it in GNOME Files, no? Otherwise I’m not sure what “opens” means in this context. But on Tails 3.9, after unlocking a volume (unpartitionned USB stick) with Unlock VeraCrypt Volumes, GNOME Files is not started.

I see that commit 09f8b2e1364d6baa58206121937fc7bf6907d16f said it would “Fix automatic opening after unlocking”, which suggests we indeed want to open the just-unlocked volume (which, incidentally, would make it easier to write the test suite).

Is the current code behaviour what we want? If yes, then at least one person (me) was confused by the doc. If no, please reassign to segfault so that’s fixed.

Thanks!

Subtasks

History

#1 Updated by intrigeri 2018-09-13 12:23:41

segfault, you might want to take a look as well, perhaps we don’t need sajolida here :)

#2 Updated by sajolida 2018-09-14 10:08:57

  • Assignee changed from sajolida to intrigeri
  • QA Check set to Ready for QA

Indeed, good catch! I’m not sure why we’re doing it this way but there’s probably a reason :)

I fixed that in doc/15951-veracrypt-doesnt-open. Do you mind reviewing it and merging? Since segfault can’t merge, I thought I wouldn’t be worth the overhead to ask him for a first review.

#3 Updated by segfault 2018-09-14 10:48:34

It is expected that the volume does not automatically open in Nautilus if it’s added via the “Add” button in Unlock VeraCrypt Volumes (but you can open Nautilus by clicking the notification).

But it should open automatically when “Unlock VeraCrypt Volumes” is called from Nautilus to open the volume (e.g. by double clicking the volume). I just noticed that this does not always work in Tails 3.9. I created Bug #15954 for this.

#4 Updated by intrigeri 2018-09-15 07:38:50

  • Status changed from Confirmed to Resolved
  • Assignee deleted (intrigeri)
  • % Done changed from 0 to 100
  • QA Check changed from Ready for QA to Pass
  • Type of work changed from User interface design to End-user documentation

sajolida wrote:
> Indeed, good catch! I’m not sure why we’re doing it this way but there’s probably a reason :)
>
> I fixed that in doc/15951-veracrypt-doesnt-open. Do you mind reviewing it and merging? Since segfault can’t merge, I thought I wouldn’t be worth the overhead to ask him for a first review.

Merged, thanks!

#5 Updated by intrigeri 2018-09-15 07:39:14

segfault wrote:
> It is expected that the volume does not automatically open in Nautilus if it’s added via the “Add” button in Unlock VeraCrypt Volumes (but you can open Nautilus by clicking the notification).
>
> But it should open automatically when “Unlock VeraCrypt Volumes” is called from Nautilus to open the volume (e.g. by double clicking the volume). I just noticed that this does not always work in Tails 3.9. I created Bug #15954 for this.

OK, thanks for looking into it!

#6 Updated by intrigeri 2018-10-01 13:29:38

  • Target version changed from Tails_3.10.1 to Tails_3.9.1