Comment 6 for bug 1882525

Today I had some more time to play around with my computer so I tried testing your hypothesis. I rebooted into my current software configuration with no workarounds as a control, and reproduced the bug as expected. Then I downgraded my system to the Marco version from 19.10 (1.22.3) by downloading it from the Ubuntu packages site, along with the necessary versions of libmarco-private2 and marco-common. Then I installed the .deb's with dpkg, and rebooted. The bug was still triggered so perhaps that suggests it's not a bug in Marco? Anything else I could try testing to narrow it down? Obviously it's confusing because GNOME doesn't trigger it, but Marco seems to regardless of version.