The wrapper will show possible files and exists afterwards. This can be also combined with -verbose to see more about what's happening here.
The wrapper script has an option to show created backup files use the argument -show-backup. In case you need help please open a bug report with a log of the command. This will turn on a verbose mode which will show more information about things that probably are going wrong. If there is any solution created as described above the wrapper script is also doing the fixups if needed within the first run.ĭon't panic, no data will be lost, ever! In case nothing is visibly happening then please start the wrapper script from a CLI by the argument -verbose $ thunderbird -verbose The assumption here is that such user know what to do to solve such a constellation. We can't know which folder should be used and the wrapper is showing an error screen. This situation can't be handled by the wrapper script. There is a folder or symlink ~/.icedove and there is a folder or symlink ~/.thunderbird which isn't pointing in a direct way to each other. The wrapper script will detect if the fixups for MIME associations and the *.desktop files are needed and changes those with a created backup before doing so. This is exactly the constellation the wrapper script is now creating to let Thunderbird find a folder ~/.thunderbird that is pointing to valid profile(s) data. Well, if you have used this in the past everything is also fine now.
There is a symlink ~/.thunderbird that is pointing to a folder ~/.icedove. In case you want to share both profile locations please only use one dedicated Icedove or Thunderbird version! Otherwise, one day you will get in trouble as Icedove and Thunderbird are writing version information into the working profile this will break at least your local installed extensions one day! You can probably remove ~/.icedove as Thunderbird doesn't care about that symlink. This will of course work as Thunderbird is detecting the folder ~/.thunderbird with the profile(s) in there. There is a symlink ~/.icedove that is pointing to a folder ~/.thunderbird. The following two other possibilities of folders and symlinks will be detected and cause no trouble. Some users may be using an advanced setup in their home directory. Other environments with other folder structures These steps will cover most typical users' concerns, but some users may have a slightly different environment. Ĭhange associations of /usr/bin/iceweasel to /usr/bin/x-Backup and fixup $/.local/share/applications/mimeapps.list in case they contain entries like userapp-Icedove-*.desktop. Fixup the MIME associations in ~/.thunderbird/$profile(s)/mimeTypes.rdf. Create a symlink from ~/.thunderbird ~/.icedove. Inform the user that an adoption of the existing Icedove profile will happen.ģ. Check if there is no folder or symlink named ~/.thunderbird. The script will do the following things:ġ. It will be triggered automatically if a user is calling thunderbird from a CLI or via the desktop file. The Thunderbird package comes with a wrapper script in /usr/bin/thunderbird which will do the users profile adoption (if possible). Because of this, the user profiles need to be adopted. The profiles are collected in ~/.thunderbird, Icedove was using ~/.icedove. The Thunderbird application uses a different folder for the user profiles than Icedove. The transitional packages don't have any working "thing" inside except to pull the dependent thunderbird package. L10n localization packages for ThunderbirdĪfter any automatic installation of thunderbird related packages (marked replaced by in the above table) you can simply remove the old icedove related packages (marked old package in the above table).
Changes due Icedove to Thunderbird De-branding