Hi, I can confirm that this issue has now been resolved (either in 1.0.0 beta 4 or beta5). Feel free to close this bug. I have also closed the upstream report - https://bugs.kde.org/show_bug.cgi?id=196668 Regards, Tom