Bugzilla

I don't believe this regression is related to easy setup changes which landed in [120.0a1](https://hg.mozilla.org/integration/autoland/rev/dca2f3fe76e7). While use mozregression I noticed a ["No permissions for local state folder."](https://searchfox.org/mozilla-central/source/browser/components/migration/ChromeProfileMigrator.sys.mjs#127) error which was implemented in [D188874](https://phabricator.services.mozilla.com/D188874). I built that patch and was able to reproduce the error without the easy setup changes (although my console is unfortunately frozen). I'll attach a recording of the bug. Interestingly, the old import screen renders on refresh instead of embedded migration wizard which makes me wonder if this might be a permission related bug?

Sorry for all the pings this week Mike, but curious if you have any context on why this error could be throwing/causing about:welcome to freeze? I can confirm that I'm not able to reproduce this issue in Nightly and will try to dig into when this regression may have been resolved?

I don't believe this regression is related to easy setup changes which landed in [120.0a1](https://hg.mozilla.org/integration/autoland/rev/dca2f3fe76e7). While use mozregression I noticed a ["No permissions for local state folder."](https://searchfox.org/mozilla-central/source/browser/components/migration/ChromeProfileMigrator.sys.mjs#127) error which was implemented in [D188874](https://phabricator.services.mozilla.com/D188874). I built that patch and was able to reproduce the error without the easy setup changes (although my console is unfortunately frozen). I'll attach a recording of the bug. Interestingly, the old import screen renders on refresh instead of embedded migration wizard which makes me wonder if this might be a permission related bug?

Sorry for all the pings this week Mike, but curious if you have any context on why this error could be throwing/causing about:welcome to freeze? I can confirm that I'm not able to reproduce this issue in Nightly and will try to dig into when this regression may have been resolved.

I'm not sure if this is related to easy setup changes which landed in [120.0a1](https://hg.mozilla.org/integration/autoland/rev/dca2f3fe76e7). While use mozregression I noticed a ["No permissions for local state folder."](https://searchfox.org/mozilla-central/source/browser/components/migration/ChromeProfileMigrator.sys.mjs#127) error which was implemented in [D188874](https://phabricator.services.mozilla.com/D188874). I built that patch and was able to reproduce the error without the easy setup changes (although my console is unfortunately frozen). I'll attach a recording of the bug. Interestingly, the old import screen renders on refresh instead of embedded migration wizard which makes me wonder if this might be a permission related bug?

Sorry for all the pings this week Mike, but curious if you have any context on why this error could be throwing/causing about:welcome to freeze? I can confirm that I'm not able to reproduce this issue in Nightly and will try to dig into when this regression may have been resolved.

edit: It seems like removing embedded migration wizard screen still causes the regression - so I'm not sure if it's related to a permission issue and maybe something related to our screen targeting.

I'm not sure if this is related to easy setup changes which landed in [120.0a1](https://hg.mozilla.org/integration/autoland/rev/dca2f3fe76e7). While use mozregression I noticed a ["No permissions for local state folder."](https://searchfox.org/mozilla-central/source/browser/components/migration/ChromeProfileMigrator.sys.mjs#127) error which was implemented in [D188874](https://phabricator.services.mozilla.com/D188874). I built that patch and was able to reproduce the error without the easy setup changes (although my console is unfortunately frozen). I'll attach a recording of the bug. Interestingly, the old import screen renders on refresh instead of embedded migration wizard which makes me wonder if this might be a permission related bug?

Sorry for all the pings this week Mike, but curious if you have any context on why this error could be throwing/causing about:welcome to freeze? I can confirm that I'm not able to reproduce this issue in Nightly and will try to dig into when this regression may have been resolved.

edit: It seems like removing embedded migration wizard screen still causes the regression - so I'm not sure if it's related to a permission issue and maybe something related to our screen targeting but still curious about what causes `No permissions for local state folder.` to throw.

I'm not sure if this is related to easy setup changes which landed in [120.0a1](https://hg.mozilla.org/integration/autoland/rev/dca2f3fe76e7). While use mozregression I noticed a ["No permissions for local state folder."](https://searchfox.org/mozilla-central/source/browser/components/migration/ChromeProfileMigrator.sys.mjs#127) error which was implemented in [D188874](https://phabricator.services.mozilla.com/D188874). I built that patch and was able to reproduce the error without the easy setup changes (although my console is unfortunately frozen). I'll attach a recording of the bug. Interestingly, the old import screen renders on refresh instead of embedded migration wizard which makes me wonder if this might be a permission related bug?

Sorry for all the pings this week Mike, but curious if you have any context on why this error could be throwing/causing about:welcome to freeze? I can confirm that I'm not able to reproduce this issue in Nightly and will try to dig into when this regression may have been resolved

I'm not sure if this is related to easy setup changes which landed in [120.0a1](https://hg.mozilla.org/integration/autoland/rev/dca2f3fe76e7). While use mozregression I noticed a ["No permissions for local state folder."](https://searchfox.org/mozilla-central/source/browser/components/migration/ChromeProfileMigrator.sys.mjs#127) error which was implemented in [D188874](https://phabricator.services.mozilla.com/D188874). I built that patch and was able to reproduce the error without the easy setup changes (although my console is unfortunately frozen). I'll attach a recording of the bug. Interestingly, the old import screen renders on refresh instead of embedded migration wizard which makes me wonder if this might be a permission related bug?

Sorry for all the pings this week Mike, but curious if you have any context on why this error could be throwing/causing about:welcome to freeze? I can confirm that I'm not able to reproduce this issue in Nightly and will try to dig into when this regression may have been resolved.

edit: It seems like removing embedded migration wizard screen still causes the regression - so I'm not sure if it's related to a permission issue and maybe something related to our screen targeting.

I'm not sure if this is related to easy setup changes which landed in [120.0a1](https://hg.mozilla.org/integration/autoland/rev/dca2f3fe76e7). While use mozregression I noticed a ["No permissions for local state folder."](https://searchfox.org/mozilla-central/source/browser/components/migration/ChromeProfileMigrator.sys.mjs#127) error which was implemented in [D188874](https://phabricator.services.mozilla.com/D188874). I built that patch and was able to reproduce the error without the easy setup changes (although my console is unfortunately frozen). I'll attach a recording of the bug. Interestingly, the old import screen renders on refresh instead of embedded migration wizard which makes me wonder if this might be a permission related bug?

Sorry for all the pings this week Mike, but curious if you have any context on why this error could be throwing/causing about:welcome to freeze? I can confirm that I'm not able to reproduce this issue in Nightly and will try to dig into when this regression may have been resolved.

edit: It seems like removing embedded migration wizard screen still causes the regression - so I'm not sure if it's related to a permission issue and maybe something related to our screen targeting (specifically `(EVALUATE_SCREEN_TARGETING)`) but still curious what causes "No permission for local state folder" to log.

I'm not sure if this is related to easy setup changes which landed in [120.0a1](https://hg.mozilla.org/integration/autoland/rev/dca2f3fe76e7). While use mozregression I noticed a ["No permissions for local state folder."](https://searchfox.org/mozilla-central/source/browser/components/migration/ChromeProfileMigrator.sys.mjs#127) error which was implemented in [D188874](https://phabricator.services.mozilla.com/D188874). I built that patch and was able to reproduce the error without the easy setup changes (although my console is unfortunately frozen). I'll attach a recording of the bug. Interestingly, the old import screen renders on refresh instead of embedded migration wizard which makes me wonder if this might be a permission related bug?

Sorry for all the pings this week Mike, but curious if you have any context on why this error could be throwing/causing about:welcome to freeze? I can confirm that I'm not able to reproduce this issue in Nightly and will try to dig into when this regression may have been resolved.

edit: It seems like removing embedded migration wizard screen still causes the regression - so I'm not sure if it's related to a permission issue and maybe something related to our screen targeting (specifically `(EVALUATE_SCREEN_TARGETING)`) but still curious what causes "No permission for local state folder" to log. As a sanity check, I also removed the easy setup screens and I can still reproduce the freeze.

I'm not sure if this is related to easy setup changes which landed in [120.0a1](https://hg.mozilla.org/integration/autoland/rev/dca2f3fe76e7). While use mozregression I noticed a ["No permissions for local state folder."](https://searchfox.org/mozilla-central/source/browser/components/migration/ChromeProfileMigrator.sys.mjs#127) error which was implemented in [D188874](https://phabricator.services.mozilla.com/D188874). I built that patch and was able to reproduce the error without the easy setup changes (although my console is unfortunately frozen). I'll attach a recording of the bug. Interestingly, the old import screen renders on refresh instead of embedded migration wizard which makes me wonder if this might be a permission related bug?

Sorry for all the pings this week Mike, but curious if you have any context on why this error could be throwing/causing about:welcome to freeze? I can confirm that I'm not able to reproduce this issue in Nightly and will try to dig into when this regression may have been resolved.

edit: It seems like removing embedded migration wizard screen still causes the regression - so I'm not sure if it's related to a permission issue and maybe something related to our screen targeting (specifically `(EVALUATE_SCREEN_TARGETING)`) but still curious what causes "No permission for local state folder" to log. As a sanity check, I also removed the easy setup screens and I can still reproduce the freeze.

Also given that this issue started in 119.0b1 I don't believe 1855031 or 1818237 may have caused this since they both landed in 120.0a1. Still narrowing down when this issue started.

I'm not sure if this is related to easy setup changes which landed in [120.0a1](https://hg.mozilla.org/integration/autoland/rev/dca2f3fe76e7). While use mozregression I noticed a ["No permissions for local state folder."](https://searchfox.org/mozilla-central/source/browser/components/migration/ChromeProfileMigrator.sys.mjs#127) error which was implemented in [D188874](https://phabricator.services.mozilla.com/D188874). I built that patch and was able to reproduce the error without the easy setup changes (although my console is unfortunately frozen). I'll attach a recording of the bug. Interestingly, the old import screen renders on refresh instead of embedded migration wizard which makes me wonder if this might be a permission related bug?

Sorry for all the pings this week Mike, but curious if you have any context on why this error could be throwing/causing about:welcome to freeze? I can confirm that I'm not able to reproduce this issue in Nightly and will try to dig into when this regression may have been resolved (and started).

edit: It seems like removing embedded migration wizard screen still causes the regression - so I'm not sure if it's related to a permission issue and maybe something related to our screen targeting (specifically `(EVALUATE_SCREEN_TARGETING)`) but still curious what causes "No permission for local state folder" to log. As a sanity check, I also removed the easy setup screens and I can still reproduce the freeze.

Also given that this issue started in 119.0b1 I don't believe 1855031 or 1818237 may have caused this since they both landed in 120.0a1. Still narrowing down when this issue started.