Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 58 11 Jun 2026, 14:57

Failures Overview

The following summary displays scenarios that failed.

Feature: Installing and running Flatpak apps in Tails
Tags: @product @check_tor_leaks
2:5.915
Scenario Installing, starting and uninstalling a Flatpak
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.001
Before features/support/hooks.rb:527 0.001
Steps
Given I have started Tails with the Flatpak feature from a USB drive with a persistent partition enabled and logged in and the network is connected 44.327
When I start GNOME Software 2.484
And I install Signal Desktop using GNOME Software 9.472
Then the org.signal.Signal Flatpak is installed after at most 600 seconds 48.768
When I start the org.signal.Signal Flatpak 0.103
Then the org.signal.Signal Flatpak is running 1.251
Given I kill the org.signal.Signal Flatpak 3.639
And I go to the main screen of GNOME Software 0.150
When I uninstall Signal Desktop using GNOME Software 15.716
The 
The Dogtail init script raised: SearchError: descendant of [application | gnome-software]: child with name='Uninstall Signal Desktop?' roleName='alert'
STDOUT:

STDERR:

 (Dogtail::Failure)
./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:339:in `initialize'
./features/support/helpers/dogtail.rb:268:in `new'
./features/support/helpers/dogtail.rb:268:in `call_tree_api_method'
./features/support/helpers/dogtail.rb:276:in `child'
./features/step_definitions/flatpak.rb:35:in `/^I uninstall (.*) using GNOME Software$/'
features/flatpak.feature:33:in `When I uninstall Signal Desktop using GNOME Software'
Then the org.signal.Signal Flatpak is uninstalled after at most 60 seconds 0.000
After features/support/hooks.rb:535 0.036
After features/support/hooks.rb:339 5.801 
SCENARIO FAILED: 'Installing, starting and uninstalling a Flatpak' (at time 00:10:30)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/00:10:30_Installing,_starting_and_uninstalling_a_Flatpak.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/00:10:30_Installing,_starting_and_uninstalling_a_Flatpak.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/00:10:30_Installing,_starting_and_uninstalling_a_Flatpak.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/00:10:30_Installing,_starting_and_uninstalling_a_Flatpak.journal
After features/support/hooks.rb:108 0.042
Feature: Upgrading an old Tails USB installation
Tags: @product
1:28.553
Scenario Creating a persistent partition with the old Tails USB installation
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given a computer 0.049
And I start Tails from USB drive "old" with network unplugged and I login 57.641
Then Tails is running from USB drive "old" 0.211
And I create a persistent partition 26.544
And I take note of which tps features are available 4.106
Python 
Python script for get_tps_bindings failed.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:23:in `get_tps_bindings'
./features/step_definitions/usb.rb:53:in `tps_bind_mounts'
./features/step_definitions/usb.rb:1124:in `/^I take note of which tps features are available$/'
features/usb_upgrade.feature:39:in `And I take note of which tps features are available'
Then a Tails persistence partition exists on USB drive "old" 0.000
And I shutdown Tails and wait for the computer to power off 0.000
After features/support/hooks.rb:339 4.902 
SCENARIO FAILED: 'Creating a persistent partition with the old Tails USB installation' (at time 01:06:58)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:06:58_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:06:58_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:06:58_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:06:58_Creating_a_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
1:10.964
Scenario Writing files to a read/write-enabled persistent partition with the old Tails USB installation
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Steps
Given a computer 0.090
And I start Tails from USB drive "old" with network unplugged and I login with persistence enabled 1:5.462
Then Tails is running from USB drive "old" 0.321
And all tps features are active 4.942
When I write some files expected to persist 0.146
Python 
Python script for get_tps_bindings failed.
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:23:in `get_tps_bindings'
./features/step_definitions/usb.rb:53:in `tps_bind_mounts'
./features/step_definitions/usb.rb:1083:in `/^I write some files expected to persist$/'
features/usb_upgrade.feature:49:in `When I write some files expected to persist'
# Verify that our baseline for the next scenarios is sane
And all persistent filesystems have safe access rights 0.000
And all persistence configuration files have safe access rights 0.000
And all persistent directories from the old Tails version have safe access rights 0.000
And I take note of which tps features are available 0.000
And I shutdown Tails and wait for the computer to power off 0.000
# XXX: how does guestfs work vs snapshots? (tails/tails#10330)
Then only the expected files are present on the persistence partition on USB drive "old" 0.000
After features/support/hooks.rb:339 4.893 
SCENARIO FAILED: 'Writing files to a read/write-enabled persistent partition with the old Tails USB installation' (at time 01:08:14)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:08:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:08:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:08:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:08:14_Writing_files_to_a_read_write-enabled_persistent_partition_with_the_old_Tails_USB_installation.journal
After features/support/hooks.rb:108 0.007
Feature: Upgrading an old Tails USB installation
Tags: @product
1:9.168
Scenario Booting Tails from a USB drive upgraded from USB with persistence enabled
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.003
Steps
Given a computer 0.059
And I start Tails from USB drive "to_upgrade" with network unplugged and I login with persistence enabled 1:5.289
Then all tps features from the old Tails version are active 1.033
And Tails is running from USB drive "to_upgrade" 0.271
And the boot device has safe access rights 2.514
And the expected persistent files created with the old Tails version are present in the filesystem 0.000
<nil> 
<nil> was expected to not be nil. (Test::Unit::AssertionFailedError)
./features/step_definitions/usb.rb:1132:in `/^the expected persistent files(| created with the old Tails version) are present in the filesystem$/'
features/usb_upgrade.feature:77:in `And the expected persistent files created with the old Tails version are present in the filesystem'
And all persistent directories from the old Tails version have safe access rights 0.000
After features/support/hooks.rb:339 4.666 
SCENARIO FAILED: 'Booting Tails from a USB drive upgraded from USB with persistence enabled' (at time 01:11:44)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:11:44_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:11:44_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:11:44_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/01:11:44_Booting_Tails_from_a_USB_drive_upgraded_from_USB_with_persistence_enabled.journal
After features/support/hooks.rb:108 0.006
Feature: Tails persistence
Tags: @product
1:9.248
Scenario Creating and using a persistent NetworkManager connection
Before features/support/hooks.rb:274 0.000
Before features/support/hooks.rb:281 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.401
And the network is plugged 0.031
And Tor is ready 9.596
And I add a wired DHCP NetworkManager connection called "persistent-con-current" 0.118
And I shutdown Tails and wait for the computer to power off 9.676
Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled 42.423
Known 
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:447:in `/^the computer (?:re)?boots Tails$/'
./features/step_definitions/common_steps.rb:235:in `/^I start Tails from (.+?) drive "(.+?)"( with network unplugged)?( and I login( with persistence enabled)?( with the changed persistence passphrase)?( (?:and|with) an administration password)?)?$/'
features/persistence.feature:88:in `Given I start Tails from USB drive "__internal" with network unplugged and I login with persistence enabled'
And I capture all network traffic 0.000
And the network is plugged 0.000
And Tor is ready 0.000
And I switch to the "persistent-con-current" NetworkManager connection 0.000
And the 1st network device has a spoofed MAC address configured 0.000
And no network device leaked the real MAC address 0.000
After features/support/hooks.rb:339 4.799 
SCENARIO FAILED: 'Creating and using a persistent NetworkManager connection' (at time 02:31:39)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/02:31:39_Creating_and_using_a_persistent_NetworkManager_connection.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/02:31:39_Creating_and_using_a_persistent_NetworkManager_connection.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/02:31:39_Creating_and_using_a_persistent_NetworkManager_connection.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/58/artifact/build-artifacts/02:31:39_Creating_and_using_a_persistent_NetworkManager_connection.journal
After features/support/hooks.rb:108 0.030