I cannot reproduce the issues mentioned in comment 0 by opening Firefox 126.0b9 with a new profile with user.js, which sets the `security.nocertdb: true` on Windows 10x64. Also after updating to Firefox 128.0 the `browser.migration.version` is updated to 148 from 144(126.0b9). Can you please verify if the issues stated at comment 0 are still reproducible with Firefox 128.0. Or are there any additional steps that need to be taken to reproduce the issue besides having `security.nocertdb: true` on startup? Thank you in advance!
Bug 1898884 Comment 10 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
I cannot reproduce the issues mentioned in comment 0 by opening Firefox 126.0b9 with a new profile with user.js, which sets the `security.nocertdb: true` on Windows 10x64. Also after updating to Firefox 128.0 the `browser.migration.version` is updated to 148 from 144(126.0b9). Can you please verify if the issues stated at comment 0 are still reproducible with Firefox [128.0](https://archive.mozilla.org/pub/firefox/candidates/128.0-candidates/build1/win64/en-US/). Or are there any additional steps that need to be taken to reproduce the issue besides having `security.nocertdb: true` on startup? Thank you in advance!
I cannot reproduce the issues mentioned in comment 0 by opening Firefox 126.0b9 with a new profile with user.js, which sets the `security.nocertdb: true` on Windows 10x64. Also after updating to Firefox 128.0 the `browser.migration.version` is updated to 148 from 144(126.0b9). Can you please verify if the issues stated at comment 0 are still reproducible with [Firefox 128.0](https://archive.mozilla.org/pub/firefox/candidates/128.0-candidates/build1/win64/en-US/). Or are there any additional steps that need to be taken to reproduce the issue besides having `security.nocertdb: true` on startup? Thank you in advance!
I cannot reproduce the issues mentioned in comment 0 by opening Firefox 126.0b9 with a new profile with user.js, which sets the `security.nocertdb: true` on Windows 10x64. Also after updating to Firefox 128.0 the `browser.migration.version` is updated to 148 from 144(126.0b9). Can you please verify if the issues stated at comment 0 are still reproducible with [Firefox 128.0](https://archive.mozilla.org/pub/firefox/candidates/128.0-candidates/build1/win64/en-US/)? Or are there any additional steps that need to be taken to reproduce the issue besides having `security.nocertdb: true` on startup? Thank you in advance!