Created attachment 178729 [details] user account settings glitches SUMMARY When clicking on user account in user setting page, the user settings (content of the right column) glitches. STEPS TO REPRODUCE 1. Open the user account setting page 2. Click on your username on the left column OBSERVED RESULT The content on the right column glitches, as shown in the attached video. EXPECTED RESULT The content should not glitch. SOFTWARE/OS VERSIONS Operating System: Fedora Linux 41 KDE Plasma Version: 6.3.0 KDE Frameworks Version: 6.10.0 Qt Version: 6.8.2 Kernel Version: 6.12.11-200.fc41.x86_64 (64-bit) Graphics Platform: Wayland Graphics Processor: Intel® Iris® Xe Graphics ADDITIONAL INFORMATION My screen is scaled at 200%.
Can reproduce.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-workspace/-/merge_requests/5257
Git commit a52501d162921232cbccc1c7d6894f82a56862f6 by Nate Graham. Committed on 27/02/2025 at 17:46. Pushed by ngraham into branch 'master'. kcms/users: don't unnecessarily push another page for the visible user When you click on the list item for the currently-viewed user, it unconditionally pushes a new page for it. This is unnecessary; we only need to do this for users that are not the currently-viewed one. M +5 -3 kcms/users/src/ui/main.qml https://invent.kde.org/plasma/plasma-workspace/-/commit/a52501d162921232cbccc1c7d6894f82a56862f6
I believe the problem itself here is with Kirigami's FormLayout, not in the implementation in the KCM. It could be possible to refactor it to use the same sub-page, but other sub-pages are used for user creation, so it is not possible to work around every case. (When creating a new user, and then changing sub-page, we'll need to create and show the user sub-page, and hit this.) Nate's MR fixes a single case when switching to the same user, which should not cause the page to be re-created at all and lose state. This may be a duplicate of BUG 476816 (likely at least related to), a more general issue of FormLayout's implementation (i.e. not with native code), or a specific issue in dynamically creating a FormLayout.
Yep, looks like exactly Bug 476816. *** This bug has been marked as a duplicate of bug 476816 ***
*** This bug has been marked as a duplicate of bug 410352 ***