https://bugs.kde.org/show_bug.cgi?id=442106
--- Comment #5 from Xavion <xavio...@gmail.com> --- Thanks for doing that good research. Before going any further, just remember that downgrading to kio v5.84.0-2 solves the problem. That means there had to be a coding change between kio v5.84.0 and kio v5.85.0 which is responsible for this bug (even if kio isn't directly to blame). If the developers can determine which line(s) of code are causing it, they can then decide whether to roll them back or go looking elsewhere (as you're planning to do). -- You are receiving this mail because: You are watching all bug changes.
