Tails

#1 Updated by mercedes508 2017-07-09 08:30:47

• Status changed from New to Confirmed
• Assignee set to sajolida

#2 Updated by sajolida 2017-07-10 18:49:47

• Assignee changed from sajolida to bertagaz
• Type of work changed from Research to Code

@bertagaz: This is a code bug, right? So assigning to you as the next RM.

#3 Updated by intrigeri 2017-07-13 18:53:13

• Assignee changed from bertagaz to intrigeri
• Target version set to Tails_3.1

> @bertagaz: This is a code bug, right? So assigning to you as the next RM.

It’s not part of the RM’s job to take care of bugs.
Reassigning to me as the current Foundation Team on-call person.

#4 Updated by intrigeri 2017-07-22 11:27:46

• blocks Feature #13234: Core work 2017Q3: Foundations Team added

#5 Updated by intrigeri 2017-07-22 11:31:40

• Category set to Internationalization
• Status changed from Confirmed to In Progress
• % Done changed from 0 to 10
• Affected tool set to Greeter

Regarding “Tor is ready”: /etc/NetworkManager/dispatcher.d/60-tor-ready.sh expects it’ll find $LANG in /etc/default/locale, which is not a valid assumption on Tails 3.0.1, which is a problem in itself. That’s a bug in the Greeter’s PostLogin.default, that calls localectl set-locale twice (once for $LANG, once for the formats settings). The second call overwrites the effect of the first one. I’ll merge these two calls into a single one, so it should be a straightforward fix => adding to the foundations team’s plate.

Regarding “Synchronizing the system’s clock”, we display this in two places:

• /etc/NetworkManager/dispatcher.d/20-time.sh, in a rare case; this one has never been gettext’ized (there’s a “XXX” in the code) so it’s not a regression and I’ll ignore it for now.
• /usr/local/lib/tails-htp-notify-user, called by /etc/NetworkManager/dispatcher.d/20-time.sh too after doing export_gnome_env. I don’t know why export_gnome_env doesn’t pick up $LANG. It might be a consequence of the localectl -related bug described above, so I’ll fix that one first and will see if it fixes this one.

#6 Updated by intrigeri 2017-07-22 11:38:56

• Feature Branch set to bugfix/13437-translations-not-applied, greeter:bugfix/13437-translations-not-applied

#8 Updated by intrigeri 2017-07-22 12:27:54

• Assignee changed from intrigeri to bertagaz
• % Done changed from 10 to 50
• QA Check set to Ready for QA

The two regressions described above are fixed here (in French) by the topic branch.

#9 Updated by bertagaz 2017-07-27 13:33:25

• Status changed from In Progress to Fix committed
• Assignee deleted (bertagaz)
• % Done changed from 50 to 100
• QA Check changed from Ready for QA to Pass

intrigeri wrote:
> The two regressions described above are fixed here (in French) by the topic branch.

Seems they are, good catch! Merged the related branch, congrats.

#10 Updated by bertagaz 2017-08-09 12:38:47

• Status changed from Fix committed to Resolved

#12 Updated by intrigeri 2017-09-29 09:37:49

• Status changed from Resolved to Fix committed
• Target version changed from Tails_3.1 to Tails_3.3

That’s because bertagaz failed to merge greeter.git:bugfix/13437-translations-not-applied into master (or push his merge) when he merged the corresponding branch in tails.git, so my work there made it into 3.1 but not into 3.2 :/

I’ve now merged it so this should be fixed in 3.3.

#13 Updated by intrigeri 2017-09-29 10:56:53

• Status changed from Fix committed to In Progress
• Assignee set to anonym

> I’ve now merged it so this should be fixed in 3.3.

Well, this requires releasing a new WhisperBack, that does not happen every time we do a Tail release, so putting this back on the RM’s plate so he knows that this time we really need it.

#14 Updated by intrigeri 2017-10-01 08:49:21

• % Done changed from 100 to 90
• QA Check deleted (Pass)

intrigeri wrote:
> Well, this requires releasing a new WhisperBack,

Err, s/WhisperBack/Greeter/.

#15 Updated by intrigeri 2017-10-01 09:50:16

• blocks Feature #13244: Core work 2017Q4: Foundations Team added

#16 Updated by intrigeri 2017-10-01 09:50:18

• blocked by deleted (Feature #13234: Core work 2017Q3: Foundations Team)

#17 Updated by intrigeri 2017-11-06 16:01:22

• Assignee changed from anonym to intrigeri

I’ll do the release without waiting for 3.3.

#18 Updated by intrigeri 2017-11-08 21:26:15

• Assignee changed from intrigeri to anonym

anonym said he was taking all this back. If this doesn’t work, please reassign to me ASAP.

#19 Updated by anonym 2017-11-15 11:30:54

• Target version changed from Tails_3.3 to Tails_3.5

#20 Updated by intrigeri 2017-12-07 13:07:09

• blocked by deleted (Feature #13244: Core work 2017Q4: Foundations Team)

#21 Updated by intrigeri 2018-01-12 10:59:25

• Priority changed from Normal to High

This got reported again on tails-l10n. Please do not skip releasing a new Greeter for Tails 3.5 and ensure you fetch from Git first (commit 606cac45b05b311b0467b13c41174129557006f9 should be in there).

#22 Updated by anonym 2018-01-22 22:29:55

• Status changed from In Progress to Fix committed
• Assignee deleted (anonym)
• % Done changed from 90 to 100
• QA Check set to Pass

Merged this time, I promise!

#24 Updated by anonym 2018-01-23 19:50:23

• Status changed from Fix committed to Resolved

#25 Updated by intrigeri 2020-04-15 06:02:11

• Affected tool changed from Greeter to Welcome Screen