Project Number Date
test_Tails_ISO_7929-celluloid-flatpak 32 19 May 2026, 14:39

Failures Overview

The following summary displays scenarios that failed.

Feature: Additional software
Tags: @product @check_tor_leaks @slow
46.449
Scenario The Additional Software dpkg hook notices when persistence is locked down while installing a package
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.013
Before features/support/hooks.rb:523 0.013
Steps
Given a computer 0.075
And I start Tails from USB drive "__internal" and I login with an administration password 46.373
Known 
Known issue #20282: Error starting GDM with your graphics card (RuntimeError)
./features/step_definitions/common_steps.rb:448: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/additional_software_packages.feature:46:in `And I start Tails from USB drive "__internal" and I login with an administration password'
And I update the APT lists using apt 0.000
When I install "ripgrep" using apt 0.000
Then the Additional Software dpkg hook has been run for package "ripgrep" and notices the persistence is locked 0.000
And the package "ripgrep" is installed 0.000
After features/support/hooks.rb:531 0.055
After features/support/hooks.rb:335 5.515 
SCENARIO FAILED: 'The Additional Software dpkg hook notices when persistence is locked down while installing a package' (at time 00:50:53)
Exception thrown while trying to save /tmp/TailsToaster/artifact.file_content_run_live-additional-software_log: RemoteShell::ServerFailure: FileNotFoundError: [Errno 2] No such file or directory: '/run/live-additional-software/log'
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/00:50:53_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.file_content_var_log_boot.log
Output of ls -la --full-time /live/persistence/tailsdata_unlocked: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/00:50:53_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_persistent_volume
Output of ls -lar --full-time /var/cache/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/00:50:53_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_cache_apt
Output of ls -lar --full-time /var/lib/apt: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/00:50:53_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_var_lib_apt
Output of mount: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/00:50:53_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.cmd_output_mount
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/00:50:53_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/00:50:53_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/00:50:53_The_Additional_Software_dpkg_hook_notices_when_persistence_is_locked_down_while_installing_a_package.journal
After features/support/hooks.rb:104 0.008
Feature: GNOME is well-integrated into Tails
Tags: @product
3:7.987
Scenario I can launch various apps via GNOME Activities Overview
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.006
Steps
# Some apps (Electrum and Persistent Storage Backup) only start when
# a Persistent Storage is available.
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.090
# Some apps (Tor Browser) only start when the network is plugged.
And the network is plugged 0.022
And Tor is ready 14.143
And all notifications have disappeared 7.059
When I start "Additional Software" via GNOME Activities Overview 9.553
And I close the "tails-additional-software-config" window 1.462
When I start "Disks" via GNOME Activities Overview 8.063
# The close button of GNOME Disks is not accessible
And I close the "gnome-disks" window via Alt+F4 0.489
When I start "Console" via GNOME Activities Overview 7.952
And I close Console 2.793
When I start "Files" via GNOME Activities Overview 7.526
And I close the "org.gnome.Nautilus" window 14.094
When I start "Persistent Storage" via GNOME Activities Overview 9.977
And I close the "tps-frontend" window 2.290
When I start "Back Up Persistent Storage" via GNOME Activities Overview 10.152
And I close the "zenity" window 2.354
When I start "Pidgin" via GNOME Activities Overview 7.811
And I close the "Pidgin" window via Alt+F4 2.113
When I start "Thunderbird" via GNOME Activities Overview 8.333
And I click "Learn More" in the "Install Thunderbird" zenity dialog 3.698
And I close the "Firefox" window 1:0.005
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'Firefox' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1206:in `new'
./features/step_definitions/common_steps.rb:1206:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:1205:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1205:in `/^I close the "([^"]+)" window$/'
features/gnome.feature:44:in `And I close the "Firefox" window'
When I start "Tor Browser" via GNOME Activities Overview 0.000
And I close the "Firefox" window 0.000
When I start "Unlock VeraCrypt Volumes" via GNOME Activities Overview 0.000
And I close the "unlock-veracrypt-volumes" window 0.000
When I start "Unsafe Browser" via GNOME Activities Overview 0.000
And I close the "Firefox" window 0.000
When I start "Secrets" via GNOME Activities Overview 0.000
And I close the "secrets" window 0.000
After features/support/hooks.rb:335 8.559 
SCENARIO FAILED: 'I can launch various apps via GNOME Activities Overview' (at time 01:28:53)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:28:53_I_can_launch_various_apps_via_GNOME_Activities_Overview.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:28:53_I_can_launch_various_apps_via_GNOME_Activities_Overview.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:28:53_I_can_launch_various_apps_via_GNOME_Activities_Overview.journal
After features/support/hooks.rb:104 0.000
Feature: Hardware failures
Tags: @product @doc
1:12.766
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Steps
Given a computer 0.071
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.981
When Tails detects disk read failures on the SquashFS 1.349
Then I see a disk failure message 0.867
Then I can open the hardware failure documentation from the disk failure message 1:2.496
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'Firefox' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/hardware.rb:48:in `new'
./features/step_definitions/hardware.rb:48:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/hardware.rb:48:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/hardware.rb:48:in `/^I can open the hardware failure documentation from the disk failure message$/'
features/hardware_failure.feature:29:in `Then I can open the hardware failure documentation from the disk failure message'
features/hardware_failure.feature:26:in `Then I can open the hardware failure documentation from the disk failure message'
After features/support/hooks.rb:335 5.614 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#1)' (at time 01:31:51)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:31:51_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:31:51_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:31:51_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:31:51_Alerting_about_disk_read_failures_in_GNOME,_Examples___1_.journal
After features/support/hooks.rb:104 0.000
Feature: Hardware failures
Tags: @product @doc
1:12.513
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Steps
Given a computer 0.106
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.739
When Tails detects disk read failures on the boot device 1.351
Then I see a disk failure message 0.828
Then I can open the hardware failure documentation from the disk failure message 1:2.487
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'Firefox' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/hardware.rb:48:in `new'
./features/step_definitions/hardware.rb:48:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/hardware.rb:48:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/hardware.rb:48:in `/^I can open the hardware failure documentation from the disk failure message$/'
features/hardware_failure.feature:30:in `Then I can open the hardware failure documentation from the disk failure message'
features/hardware_failure.feature:26:in `Then I can open the hardware failure documentation from the disk failure message'
After features/support/hooks.rb:335 5.680 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#2)' (at time 01:33:09)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:33:09_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:33:09_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:33:09_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:33:09_Alerting_about_disk_read_failures_in_GNOME,_Examples___2_.journal
After features/support/hooks.rb:104 0.000
Feature: Hardware failures
Tags: @product @doc
1:12.615
Scenario Outline Alerting about disk read failures in GNOME
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.002
Steps
Given a computer 0.064
And I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.030
When Tails detects disk read failures on the boot device with a target error 1.333
Then I see a disk failure message 0.732
Then I can open the hardware failure documentation from the disk failure message 1:2.453
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'Firefox' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/hardware.rb:48:in `new'
./features/step_definitions/hardware.rb:48:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/hardware.rb:48:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/hardware.rb:48:in `/^I can open the hardware failure documentation from the disk failure message$/'
features/hardware_failure.feature:31:in `Then I can open the hardware failure documentation from the disk failure message'
features/hardware_failure.feature:26:in `Then I can open the hardware failure documentation from the disk failure message'
After features/support/hooks.rb:335 5.253 
SCENARIO FAILED: 'Alerting about disk read failures in GNOME, Examples (#3)' (at time 01:34:27)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:34:27_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:34:27_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:34:27_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/01:34:27_Alerting_about_disk_read_failures_in_GNOME,_Examples___3_.journal
After features/support/hooks.rb:104 0.000
Feature: Tails has a sane default configuration
Tags: @product
8.839
Scenario No unexpected error messages in the journal after booting from USB drive
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.004
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.775
Then there are no unexpected messages of priority "err" or higher in the journal 0.064
Unexpected 
Unexpected error messages in the journal: [
  {
    "MESSAGE": "BUG: unable to handle page fault for address: ffffffffffffffb0",
    "SYSLOG_IDENTIFIER": "kernel",
    "PRIORITY": "1",
    "SYSLOG_FACILITY": "0",
    "_BOOT_ID": "02e48a9f9a444073946082d5ad3034f2",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_RUNTIME_SCOPE": "system",
    "_SOURCE_BOOTTIME_TIMESTAMP": "59584745",
    "_SOURCE_MONOTONIC_TIMESTAMP": "59584745",
    "_TRANSPORT": "kernel",
    "__CURSOR": "s=5ec60e2007ca486fbfc7175dfab1c61f;i=172f;b=02e48a9f9a444073946082d5ad3034f2;m=38ca320;t=65229ef1e1899;x=17cac27411ea5f60",
    "__MONOTONIC_TIMESTAMP": "59548448",
    "__REALTIME_TIMESTAMP": "1779189919127705",
    "__SEQNUM": "5935",
    "__SEQNUM_ID": "5ec60e2007ca486fbfc7175dfab1c61f"
  },
  {
    "MESSAGE": "#PF: supervisor write access in kernel mode",
    "SYSLOG_IDENTIFIER": "kernel",
    "PRIORITY": "1",
    "SYSLOG_FACILITY": "0",
    "_BOOT_ID": "02e48a9f9a444073946082d5ad3034f2",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_RUNTIME_SCOPE": "system",
    "_SOURCE_BOOTTIME_TIMESTAMP": "59584754",
    "_SOURCE_MONOTONIC_TIMESTAMP": "59584754",
    "_TRANSPORT": "kernel",
    "__CURSOR": "s=5ec60e2007ca486fbfc7175dfab1c61f;i=1730;b=02e48a9f9a444073946082d5ad3034f2;m=38ca53a;t=65229ef1e1ab4;x=e62f060a271af395",
    "__MONOTONIC_TIMESTAMP": "59548986",
    "__REALTIME_TIMESTAMP": "1779189919128244",
    "__SEQNUM": "5936",
    "__SEQNUM_ID": "5ec60e2007ca486fbfc7175dfab1c61f"
  },
  {
    "MESSAGE": "#PF: error_code(0x0002) - not-present page",
    "SYSLOG_IDENTIFIER": "kernel",
    "PRIORITY": "1",
    "SYSLOG_FACILITY": "0",
    "_BOOT_ID": "02e48a9f9a444073946082d5ad3034f2",
    "_HOSTNAME": "amnesia",
    "_MACHINE_ID": "203552d5819c41f3800e2c8ef2545404",
    "_RUNTIME_SCOPE": "system",
    "_SOURCE_BOOTTIME_TIMESTAMP": "59584757",
    "_SOURCE_MONOTONIC_TIMESTAMP": "59584757",
    "_TRANSPORT": "kernel",
    "__CURSOR": "s=5ec60e2007ca486fbfc7175dfab1c61f;i=1731;b=02e48a9f9a444073946082d5ad3034f2;m=38ca579;t=65229ef1e1af3;x=301546c145d98adb",
    "__MONOTONIC_TIMESTAMP": "59549049",
    "__REALTIME_TIMESTAMP": "1779189919128307",
    "__SEQNUM": "5937",
    "__SEQNUM_ID": "5ec60e2007ca486fbfc7175dfab1c61f"
  }
].
<false> is not true. (Test::Unit::AssertionFailedError)
./features/step_definitions/checks.rb:253:in `/^there are no unexpected messages of priority "err" or higher in the journal$/'
features/sane_defaults.feature:26:in `Then there are no unexpected messages of priority "err" or higher in the journal'
After features/support/hooks.rb:335 5.185 
SCENARIO FAILED: 'No unexpected error messages in the journal after booting from USB drive' (at time 02:57:04)
Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/02:57:04_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.file_content_var_log_boot.log
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/02:57:04_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/02:57:04_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/02:57:04_No_unexpected_error_messages_in_the_journal_after_booting_from_USB_drive.journal
After features/support/hooks.rb:104 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:46.376
Scenario The Persistent directory is usable in Tor Browser
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.008
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 8.699
And the network is plugged 0.019
And I successfully configure Tor 14.974
And available upgrades have been checked 1.118
And all notifications have disappeared 6.935
And there is a GNOME bookmark for the Persistent directory 14.567
When I start the Tor Browser 1:0.060
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'Firefox' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/common_steps.rb:1086:in `new'
./features/step_definitions/common_steps.rb:1086:in `block in launch_app'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/common_steps.rb:1085:in `launch_app'
./features/step_definitions/common_steps.rb:1140:in `launch_tor_browser'
./features/step_definitions/browser.rb:493:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/common_steps.rb:1085:in `launch_app'
./features/step_definitions/common_steps.rb:1140:in `launch_tor_browser'
./features/step_definitions/browser.rb:493:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:108:in `When I start the Tor Browser'
And I download some file in the Tor Browser to the Persistent directory 0.000
Then the file is saved to the Persistent directory 0.000
When I open the address "https://tails.net/about" in the Tor Browser 0.000
Then "Tails - How Tails works" has loaded in the Tor Browser 0.000
And I can print the current page as "output.pdf" to the Persistent directory 0.000
After features/support/hooks.rb:335 8.016 
SCENARIO FAILED: 'The Persistent directory is usable in Tor Browser' (at time 03:19:43)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/03:19:43_The_Persistent_directory_is_usable_in_Tor_Browser.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/03:19:43_The_Persistent_directory_is_usable_in_Tor_Browser.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/03:19:43_The_Persistent_directory_is_usable_in_Tor_Browser.journal
After features/support/hooks.rb:104 0.000
Feature: Browsing the web using the Tor Browser
Tags: @product
1:18.920
Scenario Persistent browser bookmarks
Before features/support/hooks.rb:270 0.000
Before features/support/hooks.rb:277 0.009
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 7.421
And all tps features are active 1.411
And all persistent filesystems have safe access rights 0.423
And all persistence configuration files have safe access rights 0.405
And all persistent directories have safe access rights 2.162
When I start the Tor Browser in offline mode 1:7.095
try_for() 
try_for() timeout expired
Last ignored exception was: Dogtail::Failure: The Dogtail init script raised: SearchError: child of [desktop frame | main]: 'Firefox' application
STDOUT:

STDERR:


./features/support/helpers/dogtail.rb:93:in `run'
./features/support/helpers/dogtail.rb:70:in `initialize'
./features/step_definitions/browser.rb:503:in `new'
./features/step_definitions/browser.rb:503:in `block (2 levels) in <top (required)>'
./features/support/helpers/misc_helpers.rb:78:in `block (2 levels) in try_for'
<internal:kernel>:187:in `loop'
./features/support/helpers/misc_helpers.rb:66:in `block in try_for'
./features/support/helpers/misc_helpers.rb:65:in `try_for'
./features/step_definitions/browser.rb:502:in `block in <top (required)>'
./features/step_definitions/browser.rb:497:in `block in <top (required)>' (Timeout::Error)
./features/support/helpers/misc_helpers.rb:145:in `rescue in try_for'
./features/support/helpers/misc_helpers.rb:51:in `try_for'
./features/step_definitions/browser.rb:502:in `/^the Tor Browser (?:has started|starts)$/'
./features/step_definitions/browser.rb:497:in `/^I start the Tor Browser( in offline mode)?$/'
features/torified_browsing.feature:135:in `When I start the Tor Browser in offline mode'
And I add a bookmark to eff.org in the Tor Browser 0.000
And I cold reboot the computer 0.000
And the computer reboots Tails 0.000
And I enable persistence 0.000
And I log in to a new session 0.000
And all notifications have disappeared 0.000
And I start the Tor Browser in offline mode 0.000
Then the Tor Browser has a bookmark to eff.org 0.000
After features/support/hooks.rb:335 8.614 
SCENARIO FAILED: 'Persistent browser bookmarks' (at time 03:24:41)
Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/03:24:41_Persistent_browser_bookmarks.png
Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/03:24:41_Persistent_browser_bookmarks.mkv
Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_7929-celluloid-flatpak/32/artifact/build-artifacts/03:24:41_Persistent_browser_bookmarks.journal
After features/support/hooks.rb:104 0.000