Tunderbird/Lightning Portable
There is a bug in the PortableApps.(sorry for bad english...)
The full path to the Calendar-App is stored in "addonStartup.json.lz4" File within the driveletter.
This file will not be changned by the launcher.
So you move from one Computer to the next and the driverletter changes Thunderbird-portable
would not find the App. So there is no Calendar etc. I have try to fix it but now luck (dont know where I can
put in the "search and change" for this file.
meow
You are here
[Fixed] Thunderbird Lightning file addonStartup.json.lz4 paths not modified
October 30, 2018 - 4:09am
#1
[Fixed] Thunderbird Lightning file addonStartup.json.lz4 paths not modified
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
The file format isn't proprietary but might as well be in some ways. It's a JSON file that's been compressed with LZ4 with a special header added (mozLz40[NULL] or mozLz40/0 in some languages). I tried stripping out the identifier and running it through the LZ4.exe decompressor but it didn't produce a usable JSON file. We'll need to figure out a way to properly decompress, adjust the path, and then recompress the file to get this portablized.
Sometimes, the impossible can become possible, if you're awesome!
There appear to possibly be some other decompression utilities that might work link from this StackExchange thread: https://unix.stackexchange.com/questions/326897/how-to-decompress-jsonlz...
I know it's asking about Unix, but most of the linked utilities are either available in Windows binary form, or are python scripts we can try compiling.
Hi
I looked around and find "mozlz4-edit" (https://github.com/serj-kzv/mozlz4-edit) for ferefox
I tried to open the file, change the drive letter and store it.
It seems to work.
but i have no glue how to get it work for us.
meow
This was fixed in Thunderbird Portable 68.10.0 and 78.0 Test 1. Sorry, I neglected to update the bug report at the time.
Sometimes, the impossible can become possible, if you're awesome!