On Tue, 7 Mar 2017 21:48:00 +0100 Andrea Stacchiotti <andreastacchio...@gmail.com> wrote:
Indeed, this "fix" is a nightmare (replying to this bug report has been
a nontrivial task).

My Thunderbird refuses to start if I have:
* Neither .icedove nor .thunderbird
* Only .thunderbird

And the migration somehow put a .thunderbird inside the .icedove when I
put an empty .icedove folder.

Sorry for the annoyed tone, but this has made Thunderbird completely
non-functional, unless I directly start
"/usr/lib/thunderbird/thunderbird-bin".

Package version: 1:45.7.1-2



I've attached a patch that fixes it, at least for me.
It appears that the comments at the end of lines 196 and 197 (and possibly 198 so I've removed it too) are breaking the elif, by making it read the next line as a comment too (because of the \ telling it to ignore the newline). Either way, bash doesn't like this syntax, don't do it! :-)

HTH,
Chris
--- /usr/bin/thunderbird-broken 2017-03-08 09:06:55.057957903 +0000
+++ /usr/bin/thunderbird        2017-03-08 09:07:31.442581553 +0000
@@ -193,9 +193,9 @@
 # is a state we can't solve on our own !!! The user needs to interact and
 # has probably an old or otherwise used Thunderbird installation. Which one
 # is the correct one to use?
-elif { [ -d "${ID_PROFILE_FOLDER}" ] || [ -L "${ID_PROFILE_FOLDER}" ]; } && \  
     # .icedove exists as folder or symlink
-     { [ -d "${TB_PROFILE_FOLDER}" ] || [ -L "${TB_PROFILE_FOLDER}" ]; } && \  
     # .thunderbird exists as folder or symlink
-       [ "$(readlink -e "${TB_PROFILE_FOLDER}")" != "${ID_PROFILE_FOLDER}" ]; 
then  # compare if canonical name of both folders equal
+elif { [ -d "${ID_PROFILE_FOLDER}" ] || [ -L "${ID_PROFILE_FOLDER}" ]; } && \
+     { [ -d "${TB_PROFILE_FOLDER}" ] || [ -L "${TB_PROFILE_FOLDER}" ]; } && \
+       [ "$(readlink -e "${TB_PROFILE_FOLDER}")" != "${ID_PROFILE_FOLDER}" ]; 
then
 
     output_debug "There is already a folder or symlink '${TB_PROFILE_FOLDER}', 
will do nothing."
     output_debug "Please investigate by yourself! Some more information below."

Reply via email to