https://bugs.kde.org/show_bug.cgi?id=466691
--- Comment #4 from Michael <mjevans1...@gmail.com> --- Updated to KDE 5.27.3-1 (and Icons-only Task Manager 3.0) last night. * Before I went to bed I didn't notice any issues (* it's possible I actually didn't _notice_ any issues then as I wasn't switching windows regularly). * I locked the screen as usual. * When I unlocked with my password this morning, I noticed the windows were similarly shuffled around as previously. No x11vnc was involved, just _locking_ and _unlocking_ the session; shortly after an update about half a day before I unlocked and noticed the issue had happened again. Is there any method by which I can collect the data that I-oTM uses to remember the window order? E.G. some unique identity per window as well as the order it currently thinks the windows should be sorted by? It might be useful to confirm the windows haven't changed identity or some other event. I checked dmesg as well in case some OOM event caused things to reload unexpectedly. Just the usual perf lines... [ 3315.601813] perf: interrupt took too long (2537 > 2500), lowering kernel.perf_event_max_sample_rate to 78600 [ 4547.040053] perf: interrupt took too long (3196 > 3171), lowering kernel.perf_event_max_sample_rate to 62400 [ 6242.574692] perf: interrupt took too long (4003 > 3995), lowering kernel.perf_event_max_sample_rate to 49800 [25918.772770] perf: interrupt took too long (5023 > 5003), lowering kernel.perf_event_max_sample_rate to 39600 The last line occurred at about 7 hours and 12 min after boot, and would have been while I was sleeping. Search results indicate it might be related to either unresponsive storage subsystems or unusually high system load. -- You are receiving this mail because: You are watching all bug changes.
