Ky sajt do të funksionojë me kufizime, teksa bëjmë mirëmbajtjen e tij për të përmirësuar punën tuaj. Nëse një artikull nuk e zgjidh problemin tuaj dhe dëshironi të bëni një pyetje, kemi bashkësinë tonë të asistencës, e gatshme për t’ju ndihmuar, te @FirefoxSupport në Twitter dhe/r/firefox në Reddit.

Kërkoni te Asistenca

Shmangni karremëzime gjoja asistence. S’do t’ju kërkojmë kurrë të bëni një thirrje apo të dërgoni tekst te një numër telefoni, apo të na jepni të dhëna personale. Ju lutemi, raportoni veprimtari të dyshimtë duke përdorur mundësinë “Raportoni Abuzim”.

Mësoni Më Tepër

Updates wipe all data

  • 1 përgjigje
  • 1 e ka hasur këtë problem
  • 12 parje
  • Përgjigjja më e re nga sfhowes

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

Krejt Përgjigjet (1)

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.