From your ```about:support```: ```"contentWin32kLockdownState": "Win32k Lockdown disabled -- user in Control Group"``` This matches your observation: >Also, I have tried ```security.sandbox.content.win32k-disable``` to ```false```, but it still fails. The first message is a bit weird because there is no Control Group for win32k - it's enabled by default for everyone. But maybe this is caused by manually changing the experiment preferences. I don't know enough about what the values mean here. It does look like win32k Lockdown is now disabled for you, but you still have the problem. So perhaps the problem is actually unrelated, this is not very clear to me. At this point, it might be best to create a fresh profile (see https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles) which will have the default settings (and no add-ons!) and check whether the problem reproduces there or not. If it does, I'd be interested in the ```about:support``` from that profile. >p.s. I have turned on webrender, and it's still the same. >didn't do anything. >I found that Status 2 is related to WebRender, and then went to open it. Sorry but I really do not understand what happened: - What does *"went to open it"* mean? - I don't understand how to align *"I have turned on webrender"* against *"didn't do anything"* I see in your ```about:support```: ``` "name": "WEBRENDER", "description": "WebRender", ==> "status": "force_enabled", <== "log": [ { "type": "default", "status": "available" }, { "type": "user", "status": "force_enabled", "message": "Force enabled by pref" } ``` Which seems to indicate that at some point WebRender *was* explicitly forced on by modifying the settings. That could also be a cause of this problem, which is why checking on a profile with the default would be good at this point in tracking this down. Right now there's too much uncertainty about the state of this config... Another point of confusion for me is that I gather from your comments is that you saw some message that related win32k Lockdown to WebRender being disabled, but the above ```about:support``` implies WebRender would have been enabled even if not force-enabled. This is another thing a fresh profile would clarify.
Bug 1769811 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.
From your ```about:support```: ```"contentWin32kLockdownState": "Win32k Lockdown disabled -- user in Control Group"``` This matches your observation: >Also, I have tried ```security.sandbox.content.win32k-disable``` to ```false```, but it still fails. The first message is a bit weird because there is no Control Group for win32k - it's enabled by default for everyone. But maybe this is caused by manually changing the experiment preferences. I don't know enough about what the values mean here. It does look like win32k Lockdown is now disabled for you, but you still have the problem. So perhaps the problem is actually unrelated, this is not very clear to me. At this point, it might be best to create a fresh profile (see https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles) which will have the default settings (and no add-ons!) and check whether the problem reproduces there or not. If it does, I'd be interested in the ```about:support``` from that profile. >p.s. I have turned on webrender, and it's still the same. >didn't do anything. >I found that Status 2 is related to WebRender, and then went to open it. Sorry but I really do not understand what happened: - What does *"went to open it"* mean? - I don't understand how to align *"I have turned on webrender"* against *"didn't do anything"* I see in your ```about:support```: ``` "name": "WEBRENDER", "description": "WebRender", ==> "status": "force_enabled", <== "log": [ { "type": "default", "status": "available" }, { "type": "user", "status": "force_enabled", "message": "Force enabled by pref" } ``` Which seems to indicate that at some point WebRender *was* explicitly forced on by modifying the settings. That could also be a cause of this problem, which is why checking on a profile with the default would be good at this point in tracking this down. Right now there's too much uncertainty about the state of this config... Another point of confusion for me is that I gather from your comments is that you saw some message that related win32k Lockdown status to WebRender being disabled, but the above ```about:support``` implies WebRender would have been enabled even if not force-enabled. This is another thing a fresh profile would clarify.
From your ```about:support```: ```"contentWin32kLockdownState": "Win32k Lockdown disabled -- user in Control Group"``` This matches your observation: >Also, I have tried ```security.sandbox.content.win32k-disable``` to ```false```, but it still fails. The first message is a bit weird because there is no Control Group for win32k - it's enabled by default for everyone. But maybe this is caused by manually changing the experiment preferences. I don't know enough about what the values mean here. It does look like win32k Lockdown is now disabled for you, but you still have the problem. So perhaps the problem is actually unrelated, this is not very clear to me. At this point, it might be best to create a fresh profile (see https://support.mozilla.org/en-US/kb/profile-manager-create-remove-switch-firefox-profiles) which will have the default settings (and no add-ons!) and check whether the problem reproduces there or not. If it does, I'd be interested in the ```about:support``` from that profile. >p.s. I have turned on webrender, and it's still the same. >didn't do anything. >I found that Status 2 is related to WebRender, and then went to open it. Sorry but I really do not understand what happened: - What does *"went to open it"* mean? - I don't understand how to align *"I have turned on webrender"* against *"didn't do anything"* I see in your ```about:support```: ``` "name": "WEBRENDER", "description": "WebRender", ==> "status": "force_enabled", <== "log": [ { "type": "default", "status": "available" }, { "type": "user", "status": "force_enabled", "message": "Force enabled by pref" } ``` Which seems to indicate that at some point WebRender *was* explicitly forced on by modifying the settings. That could also be a cause of this problem, which is why checking on a profile with the default would be good at this point in tracking this down. Right now there's too much uncertainty about the state of this config... Another point of confusion for me is that I gather from your comments is that you saw some message that related win32k Lockdown status to WebRender being disabled, but the above ```about:support``` implies (I think?) WebRender would have been enabled by default even without the force-enable. This is another thing a fresh profile would clarify.