Project Number Date
test_Tails_ISO_devel 3717 03 Mar 2025, 22:36

Failures Overview

The following summary displays scenarios that failed.

53.959
Scenario Using a persistent Pidgin configuration
Before features/support/hooks.rb:266 0.000
Before features/support/hooks.rb:273 0.005
Before features/support/hooks.rb:511 0.005
Steps
Given I have started Tails without network from a USB drive with a persistent partition enabled and logged in 11.326
And the network is plugged 0.095
And Tor is ready 19.195
And available upgrades have been checked 0.040
And all notifications have disappeared 4.311
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 12.020
Then I see Pidgin's account manager window 3.349
When I create my XMPP account 3.621
cannot find PidginAddAccountProtocolXMPP.png on the screen (FindFailed)
./features/support/helpers/screen.rb:157:in `find'
./features/support/helpers/screen.rb:367:in `hover'
./features/support/helpers/screen.rb:394:in `click'
./features/step_definitions/pidgin.rb:126:in `/^I create my XMPP account$/'
features/pidgin.feature:68:in `When I create my XMPP account'
And I close Pidgin's account manager window 0.000
Then Pidgin automatically enables my XMPP account 0.000
When I close Pidgin 0.000
And I take note of the configured Pidgin accounts 0.000
And I shutdown Tails and wait for the computer to power off 0.000
Given a computer 0.000
And I start Tails from USB drive "__internal" and I login with persistence enabled 0.000
And Pidgin has the expected persistent accounts configured 0.000
When I start "Pidgin Internet Messenger" via GNOME Activities Overview 0.000
Then Pidgin automatically enables my XMPP account 0.000
And I join some empty multi-user chat 0.000
# Exercise Pidgin AppArmor profile with persistence enabled.
# This should really be in dedicated scenarios, but it would be
# too costly to set up the virtual USB drive with persistence more
# than once in this feature.
Given I start monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/home/amnesia/.gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/home/amnesia/.gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Given I restart monitoring the AppArmor log of "/usr/bin/pidgin" 0.000
Then I cannot add a certificate from the "/live/persistence/TailsData_unlocked/gnupg" directory to Pidgin 0.000
And AppArmor has denied "/usr/bin/pidgin" from opening "/live/persistence/TailsData_unlocked/gnupg/test.crt" 0.000
When I close Pidgin's certificate import failure dialog 0.000
And I close Pidgin's certificate manager 0.000
Then I can add a certificate from the "/home/amnesia" directory to Pidgin 0.000
After features/support/hooks.rb:519 0.029
After features/support/hooks.rb:330 5.392

SCENARIO FAILED: 'Using a persistent Pidgin configuration' (at time 03:56:43)

Boot log: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3717/artifact/build-artifacts/03:56:43_Using_a_persistent_Pidgin_configuration.file_content_var_log_boot.log

Screenshot: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3717/artifact/build-artifacts/03:56:43_Using_a_persistent_Pidgin_configuration.png

Video: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3717/artifact/build-artifacts/03:56:43_Using_a_persistent_Pidgin_configuration.mkv

Systemd journal: https://jenkins.tails.boum.org/job/test_Tails_ISO_devel/3717/artifact/build-artifacts/03:56:43_Using_a_persistent_Pidgin_configuration.journal

After features/support/hooks.rb:100 0.000