Den här webbplatsen har begränsad funktionalitet medan vi utför underhåll för att förbättra din upplevelse. Om en artikel inte löser ditt problem och du vill ställa en fråga har vi vår gemenskap som väntar på att hjälpa dig på @FirefoxSupport på Twitter, /r/firefox på Reddit.

Avatar for Username

Sök i support

Akta dig för supportbedrägerier: Vi kommer aldrig att be dig att ringa eller skicka ett sms till ett telefonnummer eller dela personlig information. Rapportera misstänkt aktivitet med alternativet "Rapportera missbruk".

Läs mer

Denna tråd har arkiverats. Ställ en ny fråga om du behöver hjälp.

Updates wipe all data

  • 1 svar
  • 1 har detta problem
  • 12 visningar
  • Senaste svar av sfhowes

paulbardsley2002
paulbardsley2002
more options

Hi We (my company) switched to ubuntu, and have been using Thunderbird for a year or so. We really like the app, but on more than one occasion, on launching Thunderbird we get the "This installation of Thunderbird has a new profile. It does not shore email..." message and all our emails and profiles are lost. I'm assuming this is when Thunderbird has been updated. Is there any way we can stop this from happening in the future? As I say, I'm new to ubuntu and don't really know any code, I just know I hate windows. Cheers Paul

Hi We (my company) switched to ubuntu, and have been using Thunderbird for a year or so. We really like the app, but on more than one occasion, on launching Thunderbird we get the "This installation of Thunderbird has a new profile. It does not shore email..." message and all our emails and profiles are lost. I'm assuming this is when Thunderbird has been updated. Is there any way we can stop this from happening in the future? As I say, I'm new to ubuntu and don't really know any code, I just know I hate windows. Cheers Paul

Alla svar (1)

sfhowes
sfhowes
  • Top 10 Contributor
more options

It's unlikely that your data have been deleted, but rather TB has lost the location of the profile. You might be able to restore it by replacing a corrupt prefs.js:

https://support.mozilla.org/en-US/questions/1324156

and as the cited kb article suggests, changing the name of the profile to a non-default name can possibly avoid this happening again.