Summary: | User avatar is not properly updated in Kickoff when you change it immediately after create a new user account via User Manager | ||
---|---|---|---|
Product: | [Plasma] plasmashell | Reporter: | Patrick Silva <bugseforuns> |
Component: | Application Launcher (Kickoff) | Assignee: | David Edmundson <kde> |
Status: | RESOLVED DUPLICATE | ||
Severity: | normal | CC: | bfeber, nate, plasma-bugs |
Priority: | NOR | ||
Version: | 5.15.4 | ||
Target Milestone: | 1.0 | ||
Platform: | Arch Linux | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | ||
Sentry Crash Report: |
Description
Patrick Silva
2017-11-17 13:55:51 UTC
fixing step 2: create a new user account, so you have two accounts on your system now At which points do you click apply? Do you need to log in to the other user? Does it still happen with the latest version? Sorry for this bad report. :( Yes, it still happens. Here are better steps to reproduce: 1. open system settings > Account details > User manager 2. create a new user account: type both username and real name of the new user account and click "Apply" button (password dialog shows up: type your password and press enter to confirm user account creation) 3. select the user account logged-in currently and change its avatar: You must select any avatar from the gallery but the one used by the account created in the step 2, click "Apply" button (password dialog shows up again: type your password and press enter to confirm the new user avatar) 5. open kickoff Result: Apparently the user manager configured the avatar of the user account logged-in currently as expected but now kickoff shows the avatar of the new account created in the step 2 instead of the avatar configured in the step 3. Operating System: Arch Linux KDE Plasma Version: 5.15.4 KDE Frameworks Version: 5.57.0 Qt Version: 5.13.0 beta2 In fact you do not need to create a new user account. Kickoff always fails to update the user avatar after you change it via User Manager, no matter if you chose an avatar from the gallery or from the file system. maybe we cam mark this report as duplicate of bug 384107 Yep, looks like the same issue. *** This bug has been marked as a duplicate of bug 384107 *** |