Search Support

Avoid support scams. We will never ask you to call or text a phone number or share personal information. Please report suspicious activity using the “Report Abuse” option.

Learn More

Import Logins from a csv file

  • 1 reply
  • 1 has this problem
  • 6 views
  • Last reply by scotsmist

more options

Hi,

My old install of Mint Mate 19.3 worked flawlessly until the recent FF upgrade to version 86. Then after the upgrade it would crash but only when I logged out or rebooted the OS. Hence I hadn't noticed an issue for a while. The crash happened also using firefox --safe-mode from the command line. Deleting profiles and restarting - crash. Uninstalling FF and re-installing - crash. So I bit the bullet and wiped my drive and installed Mint Mate 20.1

I imported my bookmarks and Imported my logins from a csv file and all worked until I logged out/rebooted and again FF crashed. I dug out a spare HDD and did a clean install of Mate. I didn't import logins and FF didn't crash when I logged out of Mate or rebooted. Once I imported logins from the csv file FF crashed again.

I installed Chromium and imported bookmarks and logins - it worked okay but I wanted to use FF so am at the point where I've spent a week troubleshooting this problem and have fallen behind in my workload. I just don't want to spend days installing / uninstalling etc. I could go round in circles, testing on the Live USB stick for example, I could try enabling signon.management.page.fileImport.enabled import my logins and then disable the option before closing FF and subsequently rebooting Mate and so on, but its getting tedious and for now Chromium works and I can get work done.

So, when I enable signon.management.page.fileImport.enabled and import my logins, all is well until I logout of Mate or reboot the OS. Then when I launch FF I get the Crash report. Running firefox at the command line gives this error -

ExceptionHandler::GenerateDump cloned child 3776 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal...

nothing else. Same with firefox --safe-mode

Uninstalling, deleting my profile, rebooting the OS, reinstalling FF, same error, and that's without importing my logins. It appears that once the option in about:config - signon.management.page.fileImport.enabled has been used, its causing FF to crash.

I was going to do a clean install of Mint Mate and not update FF from version 84 to version 86 and test the older version to see if its version 86 causing this, which I suspect it is, since the problem also suddenly occurred on my old Mint Mate 19.3 install after an update...

Its possible my login.csv file is an issue, so I also exported the logins from Chromium instead after importing them from a FF csv backup and then imported the Chromium login csv back into a clean FF install and it crashed again... So after going around in these circles I decided to post here and pass the buck so to speak.

Perhaps later tonight or later this week if I get the urge I will try the clean Mint Mate install, not update FF to latest version, staying at version 84 and try the same thing to see if its the firefox causing the issue.

On a side note, once in a blue moon, instead of FF giving a crash report, it would offer to boot in safe mode or perform a clean startup. This would get FF going again until I closed it and started it, when it would crash again.

Cheers and have a good day :)

Hi, My old install of Mint Mate 19.3 worked flawlessly until the recent FF upgrade to version 86. Then after the upgrade it would crash but only when I logged out or rebooted the OS. Hence I hadn't noticed an issue for a while. The crash happened also using firefox --safe-mode from the command line. Deleting profiles and restarting - crash. Uninstalling FF and re-installing - crash. So I bit the bullet and wiped my drive and installed Mint Mate 20.1 I imported my bookmarks and Imported my logins from a csv file and all worked until I logged out/rebooted and again FF crashed. I dug out a spare HDD and did a clean install of Mate. I didn't import logins and FF didn't crash when I logged out of Mate or rebooted. Once I imported logins from the csv file FF crashed again. I installed Chromium and imported bookmarks and logins - it worked okay but I wanted to use FF so am at the point where I've spent a week troubleshooting this problem and have fallen behind in my workload. I just don't want to spend days installing / uninstalling etc. I could go round in circles, testing on the Live USB stick for example, I could try enabling signon.management.page.fileImport.enabled import my logins and then disable the option before closing FF and subsequently rebooting Mate and so on, but its getting tedious and for now Chromium works and I can get work done. So, when I enable signon.management.page.fileImport.enabled and import my logins, all is well until I logout of Mate or reboot the OS. Then when I launch FF I get the Crash report. Running firefox at the command line gives this error - ExceptionHandler::GenerateDump cloned child 3776 ExceptionHandler::SendContinueSignalToChild sent continue signal to child ExceptionHandler::WaitForContinueSignal waiting for continue signal... nothing else. Same with firefox --safe-mode Uninstalling, deleting my profile, rebooting the OS, reinstalling FF, same error, and that's without importing my logins. It appears that once the option in about:config - signon.management.page.fileImport.enabled has been used, its causing FF to crash. I was going to do a clean install of Mint Mate and not update FF from version 84 to version 86 and test the older version to see if its version 86 causing this, which I suspect it is, since the problem also suddenly occurred on my old Mint Mate 19.3 install after an update... Its possible my login.csv file is an issue, so I also exported the logins from Chromium instead after importing them from a FF csv backup and then imported the Chromium login csv back into a clean FF install and it crashed again... So after going around in these circles I decided to post here and pass the buck so to speak. Perhaps later tonight or later this week if I get the urge I will try the clean Mint Mate install, not update FF to latest version, staying at version 84 and try the same thing to see if its the firefox causing the issue. On a side note, once in a blue moon, instead of FF giving a crash report, it would offer to boot in safe mode or perform a clean startup. This would get FF going again until I closed it and started it, when it would crash again. Cheers and have a good day :)

All Replies (1)

more options

Just an update that after 20 years using Mozilla in all its flavours as my browser and valuing support over anything, I have decided to quit using this app and instead opted to use Chromium. Although not quite what I look for in a browser their support is first class.

So long and thanks for all the fish :(