Hello, "Ryan Schanzenbacher" <r...@rschanz.org> writes:
> To throw my hat into the ring with this,, I can confirm I've been seeing the > same for a while now (past 3-ish months?) I have a laptop that doesn't exhibit > this behavior that is a bit out of date, and one that does. Something I can > look into doing when I have some time is incrementally updating the "old" > laptop to try and find the commit that introduced this behavior. If you could pinpoint a commit range that introduced the problem, that’d be great. It could also be related to changes in the system config though. Thanks, Ludo’.
