Iskanje po podpori

Izogibajte se prevarantski tehnični podpori. Nikoli vam ne bomo naročili, da pokličete telefonsko številko ali nam pošljete osebne podatke. Sumljivo dejavnost prijavite z gumbom »Prijavi zlorabo«.

Več o tem

after mozbackup restores "certificates" firefox cannot start, other items restore OK

  • 3 odgovori
  • 1 ima to težavo
  • 4 ogledi
  • Zadnji odgovor od cor-el

more options

I use Mozbackup to synchronise Firefox from my desktop to my laptop. My laptop's Firefox would not start and displayed a crash reporting dialog.

I completely uninstalled and made a fresh, new install with Beta 19.0.2. I then restored my Mozbackup from my desktop, item by item. When the "Certificates" item was restored, Firefox would not start and display the crash repoting dialog. So now I know that the certificates item is the culprit.

Why does this allow Firefox to start on my desktop but refuses to do so on my laptop?

Thanks a lot! heskel@usa.net

I use Mozbackup to synchronise Firefox from my desktop to my laptop. My laptop's Firefox would not start and displayed a crash reporting dialog. I completely uninstalled and made a fresh, new install with Beta 19.0.2. I then restored my Mozbackup from my desktop, item by item. When the "Certificates" item was restored, Firefox would not start and display the crash repoting dialog. So now I know that the certificates item is the culprit. Why does this allow Firefox to start on my desktop but refuses to do so on my laptop? Thanks a lot! heskel@usa.net

Vsi odgovori (3)

more options

Did you try to remove the cert8.db file?

You can use this button to go to the Firefox profile folder:

  • Help > Troubleshooting Information > Profile Directory: Show Folder
more options

I used the Mozbackup file from my desktop, which does not seem to have this probem, to restore all my Firefox settings. I restored the settings category by category until I found the culprit by process of elimination. The "Certificates" item from the backup is the one that prevented Firefox from starting. My question is, why this happens?

more options

Did you also restore the secmode.db file?