Il 31/07/19 16:07, Carsten Schoenert ha scritto:
It was *not* made for directly modifications on the file system in
parallel made by the users them self!
I did not do any modifications until I had this issue, I know this since
I log these kind of changes.
And the root for your reported issue wasn't the TB profile folder migration.
I don't think we have enough information to rule either way.
If you are missing some further hints, did you have followed the logging
output of the starting wrapper and / or have taken a look at the README
file within /usr/share/doc/thunderbird?
Yes, but until I saw the contents of pref.js the hints in the README
made no sense. Adding text in the README was outside my jurisdiction, so
to speak, but I felt adding a note in the wiki was ok.
Do you believe it's really likely that about 2.5 years after the
de-branding of Thunderbird and the profile migration issue are happen
often?
Please don't make unnecessary assumptions on why some errors might
resurface after a long time: I actively use TB on this laptop about once
a year, perhaps less often, so it's hardly surprising that an unused
program gives no errors.
But now I also don't see any deeper need to spend more time on this. The
de-branding is almost history and people still have a working TB
profile. Even if they have enabled AppArmor.
For sure, changing the script now without a clear case to solve is just
asking for trouble. Extending the documentation, however, would have
been a safe bet, however unlikely it is that we address each and every
corner case.
Over and out.
