Friendly ping to get an update as it is marked as RBB. Thanks

Is there anything that can help narrow down the search? Was there multi monitor? mirror mode? Display size changes? crostini? 

no multi monitor (so no mirror mode or related).  no display size changes.  no crostini usage.

it might be related to suspend+resume.  i don't see the problem after logging in initially, but it does eventually show up.

i don't recall ever seeing the issue on R69 or older.

Friendly ping. Checking on the progress of these RBBs, please update with an ETA on fixes if this issue is still an RBB. Otherwise please remove the RBB label. Thanks.

I have not been able to repro this bug so far. Things I have tried:

 - Go to text field to show I beam cursor and close lid.
 - Go to text field to show I beam cursor and change display size while the cursor is hidden and then close lid.
 - Go to text field to show I beam cursor and then hide it while typing. Close lid.

None of these methods reproduced the bug. We should see if there are other users reporting this as well.

i haven't seen it wedged with the latest M70 versions (70.0.3530.0 / 11005.0.0), so perhaps the bug has been fixed by now.  if no one else is reporting this in feedback, we can close it out.

I think  Issue 878064  is related.

*Issue 853035

Checking on the progress of these RBBs, please update with an ETA on fixes if this issue is still an RBB. 

Otherwise please remove the RBB label. Thanks.

Moving to RBS.

i don't think issue 853035 is related.  i've seen that on specific devices and it tends to be related to the touchpad hardware/drive breaking down.  there's no mouse cursor because there's no mouse input :).

in my scenario, the touchpad works fine other than the fact that the cursor doesn't update -- it stays an i-beam.

if no one else is seeing this, we can ice the report until i see it again.  it happened to me a lot for a few releases in canary, but the last few seemed to have gone away.

[Auto-generated comment by a script] We noticed that this issue is targeted for M-70; it appears the fix may have landed after branch point, meaning a merge might be required. Please confirm if a merge is required here - if so add Merge-Request-70 label, otherwise remove Merge-TBD label. Thanks.