Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • T tails
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 970
    • Issues 970
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 26
    • Merge requests 26
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • tails
  • tails
  • Issues
  • #8152
Closed
Open
Issue created Oct 17, 2014 by goupille@goupille

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

Originally created by @goupille on #8152 (Redmine)

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

Feature Branch: bugfix/8158-stacked-rootfs-vs-chroot-browsers

Attachments

  • fix_i2p_browser_chroot.patch
  • fix_i2p_browser_chroot2.patch

Related issues

  • Related to #8158 (closed)
Edited May 21, 2020 by goupille
To upload designs, you'll need to enable LFS and have an admin enable hashed storage. More information
Assignee
Assign to
Time tracking