Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
T
tails
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 947
    • Issues 947
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 8
    • Merge Requests 8
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI / CD
    • Repository
    • Value Stream
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • tails
  • tails
  • Issues
  • #16021

Closed
Open
Opened Oct 02, 2018 by anonym@anonymMaintainer

Don't override Debian's system-wide Thunderbird configuration

Originally created by @anonym on #16021 (Redmine)

Due to config/chroot_local-includes/etc/thunderbird/pref/thunderbird.js we overwrite any pref changes made for the Debian package. I noticed this when working on #15942 (closed) and #15959 (closed) — the needed setting for intl.locale.requested was overwritten by us. While I’ve fixed that one there’s at least one more interesting setting:

// This setting is a workaround for some crashes inside the JS engine.
// By this Thunderbird will use more memory and acting slower as the sharing
// memory between interacting JS files is disabled.
pref ("javascript.options.baselinejit", false);

We should sync our config, and possibly consider using a patch instead so upstream changes are not silently lost like this.

Original feature Branch: https://gitlab.com/johanbluecreek/tails.git:bugfix/16021-avoid-overwriting-debian-thunderbird-config

Edited Sep 12, 2020 by intrigeri
To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
Tails_4.11
Milestone
Tails_4.11 (Past due)
Assign milestone
Time tracking
None
Due date
None
Reference: tails/tails#16021