Project Number Date
test_Tails_ISO_feature-trixie 13 04 Jun 2025, 16:25

Feature Report

Steps Scenarios Features
Feature Passed Failed Skipped Pending Undefined Total Passed Failed Total Duration Status
Using VeraCrypt encrypted volumes 49 9 9 0 0 67 0 9 9 6:55.838 Failed
Tags: @product @not_release_blocker
Feature Using VeraCrypt encrypted volumes
In order to collaborate with non-Tails users As a Tails user I want to unlock VeraCrypt encrypted volumes
10.236
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.011
Given I have started Tails from DVD without network and logged in 10.236
Tags: @product @not_release_blocker
21.330
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume
Steps
When I plug a USB drive containing a basic VeraCrypt volume 8.483
And I cancel the GNOME authentication prompt 2.414
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.248
And I open this VeraCrypt volume in GNOME Files 4.579
Then I see the expected contents in this VeraCrypt volume 0.519
When I lock the currently opened VeraCrypt volume 0.084
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:18:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.376 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a basic VeraCrypt volume' (at time 07:30:07)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:30:07_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:30:07_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:30:07_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:30:07_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
9.226
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails from DVD without network and logged in 9.226
Tags: @product @not_release_blocker
24.112
Scenario Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 10.364
And I cancel the GNOME authentication prompt 2.792
And I unlock and mount this VeraCrypt volume with Unlock VeraCrypt Volumes 5.590
And I open this VeraCrypt volume in GNOME Files 4.814
Then I see the expected contents in this VeraCrypt volume 0.466
When I lock the currently opened VeraCrypt volume 0.083
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:27:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.361 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:30:46)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:30:46_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:30:46_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:30:46_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:30:46_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.000
9.168
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails from DVD without network and logged in 9.168
Tags: @product @not_release_blocker
30.268
Scenario Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 16.371
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.226
And I open this VeraCrypt volume in GNOME Files 5.124
Then I see the expected contents in this VeraCrypt volume 0.459
When I lock the currently opened VeraCrypt file container 0.086
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:35:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.657 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a basic VeraCrypt file container with a PIM' (at time 07:31:31)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:31:31_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:31:31_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:31:31_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:31:31_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000
9.333
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.007
Given I have started Tails from DVD without network and logged in 9.333
Tags: @product @not_release_blocker
41.421
Scenario Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 27.092
And I unlock and mount this VeraCrypt file container with Unlock VeraCrypt Volumes 8.887
And I open this VeraCrypt volume in GNOME Files 4.904
Then I see the expected contents in this VeraCrypt volume 0.449
When I lock the currently opened VeraCrypt file container 0.087
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:43:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.303 
SCENARIO FAILED: 'Use Unlock VeraCrypt Volumes to unlock a hidden VeraCrypt file container' (at time 07:32:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:32:27_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:32:27_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:32:27_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:32:27_Use_Unlock_VeraCrypt_Volumes_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.016
10.004
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails from DVD without network and logged in 10.004
Tags: @product @not_release_blocker
27.551
Scenario Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile
Steps
When I plug a USB drive containing a basic VeraCrypt volume with a keyfile 8.366
And I cancel the GNOME authentication prompt 2.855
And I unlock and mount this VeraCrypt volume with GNOME Disks 11.060
And I open this VeraCrypt volume in GNOME Files 4.759
Then I see the expected contents in this VeraCrypt volume 0.427
When I lock the currently opened VeraCrypt volume 0.082
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:54:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.384 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a basic VeraCrypt volume with a keyfile' (at time 07:33:10)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:33:10_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:33:10_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:33:10_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:33:10_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_basic_VeraCrypt_volume_with_a_keyfile.journal
After features/support/hooks.rb:100 0.000
9.245
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Given I have started Tails from DVD without network and logged in 9.245
Tags: @product @not_release_blocker
25.612
Scenario Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume
Steps
When I plug a USB drive containing a hidden VeraCrypt volume 10.450
And I cancel the GNOME authentication prompt 2.917
And I unlock and mount this VeraCrypt volume with GNOME Disks 6.751
And I open this VeraCrypt volume in GNOME Files 4.956
Then I see the expected contents in this VeraCrypt volume 0.452
When I lock the currently opened VeraCrypt volume 0.084
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:63:in `When I lock the currently opened VeraCrypt volume'
Then the VeraCrypt volume has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.404 
SCENARIO FAILED: 'Use GNOME Disks to unlock a USB drive that has a hidden VeraCrypt volume' (at time 07:33:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:33:51_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:33:51_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:33:51_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:33:51_Use_GNOME_Disks_to_unlock_a_USB_drive_that_has_a_hidden_VeraCrypt_volume.journal
After features/support/hooks.rb:100 0.002
9.818
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.081
Given I have started Tails from DVD without network and logged in 9.818
Tags: @product @not_release_blocker
51.703
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a keyfile 23.101
And I unlock and mount this VeraCrypt file container with GNOME Disks 22.919
And I open this VeraCrypt volume in GNOME Files 5.014
Then I see the expected contents in this VeraCrypt volume 0.579
When I lock the currently opened VeraCrypt file container 0.086
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:71:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.620 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a keyfile' (at time 07:34:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:34:58_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:34:58_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:34:58_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:34:58_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_keyfile.journal
After features/support/hooks.rb:100 0.015
9.439
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.009
Given I have started Tails from DVD without network and logged in 9.439
Tags: @product @not_release_blocker
53.040
Scenario Use GNOME Disks to unlock a hidden VeraCrypt file container
Steps
When I plug and mount a USB drive containing a hidden VeraCrypt file container 26.895
And I unlock and mount this VeraCrypt file container with GNOME Disks 20.496
And I open this VeraCrypt volume in GNOME Files 5.075
Then I see the expected contents in this VeraCrypt volume 0.490
When I lock the currently opened VeraCrypt file container 0.082
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:79:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.331 
SCENARIO FAILED: 'Use GNOME Disks to unlock a hidden VeraCrypt file container' (at time 07:36:06)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:36:06_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:36:06_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:36:06_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:36:06_Use_GNOME_Disks_to_unlock_a_hidden_VeraCrypt_file_container.journal
After features/support/hooks.rb:100 0.021
23.136
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.008
Given I have started Tails from DVD without network and logged in 23.136
Tags: @product @not_release_blocker
41.189
Scenario Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM
Steps
When I plug and mount a USB drive containing a basic VeraCrypt file container with a PIM 16.197
And I unlock and mount this VeraCrypt file container with GNOME Disks 19.415
And I open this VeraCrypt volume in GNOME Files 5.030
Then I see the expected contents in this VeraCrypt volume 0.462
When I lock the currently opened VeraCrypt file container 0.082
Command 
Command failed: udisksctl unmount --block-device /dev/mapper/tcrypt-*
error code: 1
stdout: 
stderr: Error unmounting /dev/dm-0: GDBus.Error:org.freedesktop.UDisks2.Error.DeviceBusy: Error unmounting /dev/dm-0: target is busy
.
<false> is not true. (ExecutionFailedInVM)
./features/support/helpers/vm_helper.rb:496:in `rescue in execute_successfully'
./features/support/helpers/vm_helper.rb:493:in `execute_successfully'
./features/step_definitions/veracrypt.rb:332:in `/^I lock the currently opened VeraCrypt (volume|file container)$/'
features/veracrypt.feature:87:in `When I lock the currently opened VeraCrypt file container'
Then the VeraCrypt file container has been unmounted and locked 0.000
After features/support/hooks.rb:330 5.756 
SCENARIO FAILED: 'Use GNOME Disks to unlock a basic VeraCrypt file container with a PIM' (at time 07:37:16)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:37:16_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:37:16_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:37:16_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_feature-trixie/13/artifact/build-artifacts/07:37:16_Use_GNOME_Disks_to_unlock_a_basic_VeraCrypt_file_container_with_a_PIM.journal
After features/support/hooks.rb:100 0.000