Bug #8152

I2P browser doesn't start after incremental upgrade to Tails 1.2

Added by goupille 2014-10-17 09:06:52 . Updated 2014-12-03 19:40:31 .

Status:
Resolved
Priority:
Elevated
Assignee:
Category:
Target version:
Tails_1.2.1
Start date:
2014-10-17
Due date:
% Done:

100%

Feature Branch:
bugfix/8158-stacked-rootfs-vs-chroot-browsers
Type of work:
Code
Blueprint:

Starter:
Affected tool:
I2P
Deliverable for:

Description

when lauching the i2p browser, the warning show up but multiple users waited more thant 30 minutesand the i2p browser didn’t start. I found that in the logs (.xsession-errors):

Everything is Ok
unzip: cannot find or open /var/lib/i2p-browser/chroot//usr/local/lib/tor-browser/browser/omni.ja, /var/lib/i2p-browser/chroot//usr/local/lib/tor-browser/browser/omni.ja.zip or /var/lib/i2p-browser/chroot//usr/local/lib/tor-browser/browser/omni.ja.ZIP.
sed: can’t read /tmp/tmp.vJsqnaMTPH/chrome/en-US/locale/branding/brand.dtd: No such file or directory

Files

fix_i2p_browser_chroot.patch (699 B) sanic, 2014-10-20 09:23:34
fix_i2p_browser_chroot2.patch (899 B) sanic, 2014-10-20 12:02:39

Subtasks

Related issues

Related to Tails - Bug #8158: Unsafe Browser does not start Resolved 2014-10-19

History

#1 Updated by BitingBird 2014-10-17 09:42:20

  • Category set to 180

#2 Updated by intrigeri 2014-10-17 13:55:51

  • Subject changed from I2p browser doesn't start to I2P browser doesn't start
  • Assignee set to kytv
  • Priority changed from Normal to Elevated
  • Target version set to Tails_1.2.1

kytv, may you please have a look? Assuming it worked back when anonym merged your work for 1.2, I guess it was caused by one of last changes for the migration to TBB / FF31.

#3 Updated by intrigeri 2014-10-20 07:34:10

  • related to Bug #8158: Unsafe Browser does not start added

#4 Updated by intrigeri 2014-10-20 07:34:57

  • Assignee changed from kytv to anonym

anonym, I guess the explanation on Bug #8158 applies here too. There’s a patch there.

#5 Updated by sanic 2014-10-20 09:23:34

Here’s a fix for the I2P browser problem, which has the same cause as Bug #8158.

#6 Updated by sanic 2014-10-20 12:03:21

Updated patch, confirmed working on my computer. The patch is identical to the final one for Bug #8158 except for referencing i2p-browser instead of unsafe-browser.

#7 Updated by anonym 2014-10-21 13:26:43

  • Assignee deleted (anonym)
  • Feature Branch set to bugfix/8158-stacked-rootfs-vs-chroot-browsers
  • Type of work changed from Research to Code

The patch needed some love. Please review’n’merge!

(BTW, my test in Bug #8158–13 also verified that the I2P Browser works after incremental upgrades.)

#8 Updated by intrigeri 2014-10-30 15:44:44

  • Assignee set to intrigeri

#9 Updated by intrigeri 2014-10-30 17:05:32

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

#10 Updated by intrigeri 2014-11-20 19:29:48

  • Subject changed from I2P browser doesn't start to I2P browser doesn't start after incremental upgrade to Tails 1.2

#11 Updated by BitingBird 2014-12-03 19:40:31

  • Status changed from Fix committed to Resolved