Tails

#1 Updated by intrigeri 2017-07-18 12:24:42

• Target version set to Tails_3.1

(Like parent ticket.)

#2 Updated by anonym 2017-08-07 14:05:18

• Target version changed from Tails_3.1 to Tails_3.2

#3 Updated by lamby 2017-08-19 22:58:30

• Status changed from Confirmed to In Progress
• Assignee changed from lamby to anonym

I’ve fixed this upstream here:

https://bugzilla.gnome.org/show_bug.cgi?id=786528

It applies against the stretch version of src:gtk+2.0 with a small offset.

Enjoy!

#4 Updated by intrigeri 2017-08-20 11:34:21

• QA Check set to Ready for QA
• Type of work changed from Research to Code

Yeah :)

#7 Updated by intrigeri 2017-09-07 12:12:06

• Priority changed from Normal to Elevated

#8 Updated by anonym 2017-09-07 15:49:55

• % Done changed from 0 to 50
• Feature Branch set to bugfix/13440-reproducible-gtk2.0-immodules.cache

#9 Updated by intrigeri 2017-09-10 17:33:35

• File diffoscope.html added
• QA Check changed from Ready for QA to Dev Needed

kurono’s 3.2~alpha2 ISO has a problem in this, see attached diffoscope output. Looks like things get sorted in a different order.

#10 Updated by intrigeri 2017-09-11 13:01:54

• File diffoscope.html added

Another Tails contributor reported FTBR of 3.1~alpha2 with the same problem, diffoscope output attached.

#11 Updated by intrigeri 2017-09-12 09:47:13

• File diffoscope.txt.bz2 added

And a third one.

#12 Updated by anonym 2017-09-12 11:05:13

• Assignee changed from anonym to lamby

lamby, is there any chance you could try to have a look and provide us a fix before 13:00 2017-09-14 UTC so we might have this fix in Tails 3.2~rc1?

#13 Updated by lamby 2017-09-12 15:31:36

• Assignee changed from lamby to anonym

anonym wrote:
> lamby, is there any chance you could try to have a look and provide us a fix before 13:00 2017-09-14 UTC so we might have this fix in Tails 3.2~rc1?

Sure, but can you confirm my patch was applied when building this ISO? I don’t see anything about it being merged here…

#14 Updated by anonym 2017-09-12 16:16:34

• Assignee changed from anonym to lamby

tl;dr: I confirm your patch was applied in 3.2~alpha2.

More explanation: https://labs.riseup.net/code/issues/13442#note-12

#15 Updated by anonym 2017-09-12 17:33:04

• File immodules.cache.bad added
• File immodules.cache.good added

Here’s the good file and one of the bad files (not necessarily the same as in any of the diffoscope reports here).

#17 Updated by lamby 2017-09-13 18:50:55

• File gtk+3.0.diff.txt added
• Assignee changed from lamby to anonym

After a lot of head-scratching and testing my code and being like “but it works dammit!!” I realised this was because we have a code copy of this patch, one for gtk+2.0 and gtk+3.0.

We now have two bugs in the Debian BTS tracking this:

https://bugs.debian.org/872729 (GTK2)
https://bugs.debian.org/875700 (GTK3)

Attaching patch for gtk+3.0.

Enjoy :)

#18 Updated by intrigeri 2017-09-13 18:55:18

• QA Check changed from Dev Needed to Ready for QA

Thanks a lot Chris!

#20 Updated by anonym 2017-09-15 10:41:02

• Status changed from In Progress to Fix committed
• % Done changed from 50 to 100

Applied in changeset commit:8c8592689c64cd35d9085be18bbb23ebed2ecbe3.

#21 Updated by anonym 2017-09-15 17:49:17

• Assignee deleted (anonym)
• QA Check changed from Ready for QA to Pass

#22 Updated by anonym 2017-09-28 18:41:21

• Status changed from Fix committed to Resolved