Thunderbird doesn't start if ~/.icedove exists and is empty
as a workaround, set up an administrator password in the greeter, then after Tails has started, open a terminal and type
sudo sed -i '/icedove/d' /live/persistence/TailsData_unlocked/persistence.conf
Drop Claws Mail persistence setting migration (refs: #12734).
Whenever persistent Claws Mail setting is enabled, this creates an empty
~/.icedove/ directory, that prevents Thunderbird from starting.
#1 Updated by goupille about 1 year ago
a user affected by this issue reported that deleting the icedove line from /live/persistence/TailsData_unlocked/persistence.conf doesn't fix the issue because during Tails startup a script add the line to persistence.conf and /live/persistence/TailsData_unlocked/icedove is created again
#3 Updated by intrigeri about 1 year ago
- Priority changed from Normal to Low
- Target version set to Tails_3.2
- Affected tool set to Email Client
4-5 affected users reported this bug, but they've all migrated successfully now. So at the help desk / foundations team meeting today, we deemed this ticket as low-priority. FWIW I've seen another similar report on XMPP today. Please don't spend too much time on it: if the fix is trivial, or a workaround can be documented easily, do so; if it's any harder, reject.
- Status changed from Confirmed to Rejected
- Assignee deleted (
(Given how anonym's plate for 3.2 looks like, I doubt this should be prioritized for this release. And it's not worth our time to do it later as most affected users should have bypassed this limitation already, so rejecting.)
- Status changed from Rejected to In Progress
- Assignee changed from anonym to intrigeri
- Target version changed from Tails_3.2 to Tails_3.5
- Feature Branch set to bugfix/12734-claws-persistence-breaks-thunderbird
most affected users should have bypassed this limitation already, so rejecting.
Apparently not. It seems trivial to avoid creating more instances of this problem, let's do it.