This bug seems to have become less frequent since my upstream kernel test: reliably triggering it now requires being on battery and (rather than or) heavy graphics load. As no relevant packages are listed in the apt log as upgraded since then, I suspect this test left a configuration change behind.
This bug seems to have become less frequent since my upstream kernel test: reliably triggering it now requires being on battery and (rather than or) heavy graphics load. As no relevant packages are listed in the apt log as upgraded since then, I suspect this test left a configuration change behind.