Project

General

Profile

Bug #17462

Tor Browser in development builds sometime opens the wrong startup home page

Added by anonym about 2 months ago. Updated about 2 months ago.

Status:
Confirmed
Priority:
Normal
Assignee:
-
Category:
-
Target version:
-
Start date:
Due date:
% Done:

0%

Feature Branch:
Type of work:
Research
Blueprint:
Starter:
Affected tool:
Browser

Description

For an example, see: https://jenkins.tails.boum.org/job/test_Tails_ISO_stable/2162/

In several of the scenarios using Tor Browser, we get this failure:

[... bunch of Dogtail logs ...]
    And the Tor Browser loads the startup page                                     # features/step_definitions/common_steps.rb:391
      try_for() timeout expired (Timeout::Error)
      ./features/support/helpers/misc_helpers.rb:89:in `rescue in try_for'
      ./features/support/helpers/misc_helpers.rb:36:in `try_for'
      ./features/step_definitions/browser.rb:127:in `page_has_loaded_in_the_Tor_Browser'
      ./features/step_definitions/common_steps.rb:402:in `/^the Tor Browser loads the (startup page|Tails homepage|Tails roadmap)$/'
      features/torified_browsing.feature:99:in `And the Tor Browser loads the startup page'

Looking at the failure screenshot we can see that the startup page that was loaded is:

https://tails.boum.org/home/index.en.html

but for development builds we expect:

https://tails.boum.org/home/testing/index.en.html

This is very odd since the config/chroot_local-hooks/11-localize_browser script hardcodes the startup home page, so we should not be able to see different results.


Related issues

Related to Tails - Bug #17007: JavaScript sometimes blocked on Tor Browser first start ⇒ "Watching a WebM video over HTTPS" and "Playing an Ogg audio track" scenarios are fragile: blocked by NoScript click-to-play Confirmed
Blocks Tails - Feature #16209: Core work: Foundations Team Confirmed

History

#1 Updated by anonym about 2 months ago

To find potential instances one can:

ssh jenkins.lizard "find /var/lib/jenkins/jobs/test_Tails_ISO_* -name debug.log | xargs grep 'features/step_definitions/browser.rb:.*:in .page_has_loaded_in_the_Tor_Browser'"

#2 Updated by intrigeri about 2 months ago

  • Related to Bug #17007: JavaScript sometimes blocked on Tor Browser first start ⇒ "Watching a WebM video over HTTPS" and "Playing an Ogg audio track" scenarios are fragile: blocked by NoScript click-to-play added

#3 Updated by intrigeri about 2 months ago

#4 Updated by intrigeri about 2 months ago

This is very odd since the config/chroot_local-hooks/11-localize_browser script hardcodes the startup home page, so we should not be able to see different results.

Odd indeed! This reminds me from another case where our config seems to be not entirely honored in some cases: #17007.

Also available in: Atom PDF