Tails

#1 Updated by intrigeri 2015-07-17 07:58:08

• Assignee set to emmapeel
• QA Check set to Info Needed

Can you reproduce this with a recent nightly build of feature/jessie? It might be that the port to GTK3 has fixed it.

#2 Updated by emmapeel 2015-07-19 04:55:37

• blocked by Bug #9761: Jessie:Orca not working added

#3 Updated by emmapeel 2015-07-19 06:21:52

• Assignee deleted (emmapeel)

It is fixed in Tails/Jessie. tails-i386-feature_jessie-1.5-20150718T0408Z-345c673.iso

#4 Updated by emmapeel 2015-07-19 06:44:56

• blocks deleted (Bug #9761: Jessie:Orca not working)

#5 Updated by intrigeri 2015-07-19 07:23:49

• Subject changed from Tails installer cannot run with Orca to Tails Installer cannot be read by Orca
• Assignee set to emmapeel
• QA Check deleted (Info Needed)
• Type of work changed from Code to End-user documentation

Thanks for the update (I love good news)!

I doubt anyone will fix the Qt codebase on Wheezy, so please:

1. document this problem on the known issues page; and then:
2. mark this ticket as resolved with the Tails_2.0 milestone.

#6 Updated by intrigeri 2015-07-19 09:44:16

• Subject changed from Tails Installer cannot be read by Orca to Tails Installer cannot be read by Orca on Wheezy

#7 Updated by intrigeri 2015-07-19 09:44:36

• related to Bug #7504: Tails Installer is fully inaccessible added

#8 Updated by intrigeri 2015-07-19 09:46:53

• Subject changed from Tails Installer cannot be read by Orca on Wheezy to Document that Tails Installer cannot be read by Orca on Wheezy

Actually we had Bug #7504 already (found by looking at tickets in the Accessibility category), so:

> # document this problem on the known issues page; and then:

That’s still a good idea.

> # mark this ticket as resolved with the Tails_2.0 milestone.

That’s not needed, since Bug #7504 has this information => repurposing this ticket for the known issues thing.

#9 Updated by emmapeel 2015-07-21 10:04:18

• Status changed from Confirmed to In Progress
• QA Check set to Ready for QA
• Feature Branch set to emmapeel:bug/9739-tails_installer_orca
• Starter set to Yes

please review:

https://git-tails.immerda.ch/emmapeel/tails/diff/?h=bug/9739-tails_installer_orca&id=9a72e42f80a9b89fc26d1e4430fd0d228d4b6716

#10 Updated by emmapeel 2015-07-21 10:06:55

• Assignee deleted (emmapeel)

#11 Updated by sajolida 2015-07-28 03:55:03

• QA Check changed from Ready for QA to Info Needed

Thanks for working on this. I have a few comments though:

• Did you consider referencing this as a <div id="bug"> section in /doc/first_steps/installation instead?
• We spell Tails Installer.
• What about documenting that this will be fixed by Tails Jessie (due in the first quarter of 2016)?

#12 Updated by sajolida 2015-07-28 03:55:17

• Assignee set to emmapeel

#14 Updated by emmapeel 2015-07-29 07:32:44

• Assignee changed from emmapeel to sajolida

The phrasing has been adjusted, what do you think about adding it to the bug tag in https://tails.boum.org/doc/first_steps/accessibility/

#15 Updated by sajolida 2015-08-03 03:20:48

• Assignee changed from sajolida to emmapeel
• QA Check changed from Info Needed to Dev Needed

Definitely. Then maybe we can do that only.

#16 Updated by emmapeel 2015-08-03 09:05:29

• Assignee deleted (emmapeel)
• % Done changed from 0 to 50
• QA Check changed from Dev Needed to Ready for QA

I moved the orca warning to acccesibility.

There, I took out the Tor Browser warning, as it looks fixed already in Bug #9261.

The Unsafe Browser looks like it will be fixed for 2.0 too, see Bug #7502

Please review

#17 Updated by intrigeri 2015-08-03 09:25:27

• Assignee set to sajolida

#18 Updated by sajolida 2015-08-10 08:22:33

• Assignee changed from sajolida to emmapeel
• QA Check changed from Ready for QA to Dev Needed

I think that you found the right place to document this. Keeping this to the minimum!

But I see no reference to 2.0 or Tails Jessie fixing the Unsafe Browser in Bug #7502. Where did you see that?

Furthermore, the indication of a future version number might not be very useful unless we give an indication on when this might happen. Also, I’m not 100% sure whether Tails Jessie will be called 2.0. I would be in favor of that but I don’t see this acted neither on Redmine (where it still means something different), neither on the calendar. So I’m not sure here, but I wonder whether we could remove that and be done with it.

#20 Updated by emmapeel 2015-08-25 04:01:17

• Assignee changed from emmapeel to sajolida

I tested the Unsafe browser and was working on Tails/Jessie. It seems I forgot to report that, my bad.

So, what do you think then? Shall we leave the information about Tails/Jessie, or change it for ‘the first quarter of 2016’, or just don’t commit to any date?

#21 Updated by intrigeri 2015-08-25 04:33:54

• Assignee changed from sajolida to emmapeel

> I tested the Unsafe browser and was working on Tails/Jessie. It seems I forgot to report that, my bad.

Both Bug #7504 and Bug #9739 are about Tails Installer, not about the Unsafe Browser, so:

• it seems to me that this ticket has all the info we need to document the limitation it’s about; if you want to extend its scope to the Unsafe Browser, then please adjust the ticket description accordingly;
• please report anything related to Unsafe Browser accessibility on Bug #7502 :)

> So, what do you think then? Shall we leave the information about Tails/Jessie, or change it for ‘the first quarter of 2016’, or just don’t commit to any date?

“first quarter of 2016” sounds good!

#23 Updated by emmapeel 2015-08-25 07:16:29

• Assignee deleted (emmapeel)

#24 Updated by intrigeri 2015-08-25 11:06:53

• Assignee set to sajolida
• QA Check changed from Dev Needed to Ready for QA

#25 Updated by sajolida 2015-08-27 08:42:23

• Assignee changed from sajolida to emmapeel
• Feature Branch changed from emmapeel:bug/9739-tails_installer_orca to bug/9739-tails_installer_orca

What you are saying in Bug #9739#note-20 seems to contradict what you are saying in Bug #7502#note-13. I’ll stick with Unsafe Browser being unread by Orca. Correct me if I misunderstood. I also added I2P Browser which is also chrooted. I didn’t check this myself but I don’t see why it would work better than the Unsafe Browser.

So I removed the commitment on dates as that would make the whole thing more complicated than useful and we’ve already spent too much time on this issue to my taste.

Please review my commits c2b20bf..d0d5c4e and if you’re fine with them I’ll merge them.

#26 Updated by emmapeel 2015-09-01 04:53:56

• Assignee changed from emmapeel to sajolida

Yeah you are right… please merge!

#27 Updated by sajolida 2015-09-01 07:55:34

• Status changed from In Progress to Resolved
• % Done changed from 50 to 100

Applied in changeset commit:1d010ea0777ccffa714beda41e758d410a357571.

#28 Updated by sajolida 2016-02-08 19:08:50

• Target version set to Tails_1.6

#29 Updated by intrigeri 2018-04-08 16:47:24

• QA Check deleted (Ready for QA)