On Thu, Aug 8, 2019 at 2:08 PM Antonio M <[email protected]> wrote: > confirmed that running on 5.1.20-300 this issue is not present
Same here. It does seem to be the 5.2 kernel that triggered this behavior. I also managed to reproduce it once today without virt-manager running, so maybe VMs have nothing to do with it. Interacting with them seems to be the easiest way to trigger the behavior, though. -- Jerry James http://www.jamezone.org/ _______________________________________________ devel mailing list -- [email protected] To unsubscribe send an email to [email protected] Fedora Code of Conduct: https://docs.fedoraproject.org/en-US/project/code-of-conduct/ List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/[email protected]
