Created attachment 133440 [details] Screenshot 1 SUMMARY STEPS TO REPRODUCE 1. Press Meta/Windows key 2. Enter Users and press enter >> See Screenshot Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.9.8-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520
Weird, works for me.
What is the version of systemsettings you are using? You can get the version number from the three - lines in the top right and clicking About System Settings.
(In reply to Justin Zobel from comment #2) > What is the version of systemsettings you are using? You can get the version > number from the three - lines in the top right and clicking About System > Settings. Operating System: Arch Linux KDE Plasma Version: 5.20.3 KDE Frameworks Version: 5.76.0 Qt Version: 5.15.1 Kernel Version: 5.9.8-arch1-1 OS Type: 64-bit Processors: 4 × Intel® Core™ i5-6300U CPU @ 2.40GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa Intel® HD Graphics 520
I tested it right now again - same issue
Thanks, I can't confirm the same issue here on openSUSE Tumbleweed, 5.20.3. Can you please test on a fresh user to make sure it's not a config related issue?
This seems to be a race condition with accountsservice. For me, it ony happens the first time I launch it after boot. All subsequent runs work fine. If I kill accounts-daemon, then I can reproduce it again (only the first time, again).
Confirmed. Antonio's comment allows me to reproduce this issue.
Ugh, the first time you open it after boot is exactly the case that most users will hit. :(
dS810, per chance, are you not using a display manager such as SDDM or GDM? The accounts service generally expects that a display manager interacts with it for stuff like locale, so it being dead when you're in a user session isn't really part of its expected flow of events. Either way, it failing to have a sane state on DBus activation is most likely an upstream bug, so I filed an issue there. https://gitlab.freedesktop.org/accountsservice/accountsservice/-/issues/93 Marking this as resolved upstream for now. If there's anything that can be done downstream to work around this, please reopen this bug.
(In reply to Jan Blackquill (Carson Black) from comment #9) Hello Jan, I use SDDM.
(In reply to Jan Blackquill (Carson Black) from comment #9) > dS810, per chance, are you not using a display manager such as SDDM or GDM? > The accounts service generally expects that a display manager interacts with > it for stuff like locale, so it being dead when you're in a user session > isn't really part of its expected flow of events. I don't think SDDM interacts with accountsservice in any way, other than to retrieve avatars from accoutsservice's path (which doesn't need the accounts daemon to be running at all) sddm > git grep Accounts ChangeLog: + Make greeter see icons set by AccountsServices. src/greeter/UserModel.cpp: QString accountsServiceFace = QStringLiteral("/var/lib/AccountsService/icons/%1").arg(user->name);
*** Bug 429897 has been marked as a duplicate of this bug. ***
is there nothing we can do to work around this locally? It's a pretty bad bug.
Created attachment 133787 [details] access in terminal kcmshell5 kcm_users
I ran in bustle, reproduced the issue and captured a DBus traffic log. AccountsService looked correct in that. I'm not convinced we understand the initial problem.
Found it! It is a race, it is entirely our side. Will fix.
A possibly relevant merge request was started @ https://invent.kde.org/plasma/plasma-desktop/-/merge_requests/250
@Jan can you close the upstream bug report please.
Git commit 987cafc23638d59bc4e15a964931a04fe30aa988 by David Edmundson. Committed on 02/12/2020 at 10:05. Pushed by davidedmundson into branch 'master'. [kcms/users] Avoid race condition on startup If accounts service is not yet running the name will not be registered when we make our first call. We call into AccountsService from our client code with a blocking call. We then create a new QDBusAbstractInterface on a given service. QDBusAbstractInterface::isValid effectively is just a check that the service is registered. This might not be processed yet at the time we call this. It isn't a helpful check, if it wasn't up the previous call to fetch users would have failed. We can just remove it. M +1 -1 kcms/users/src/user.cpp https://invent.kde.org/plasma/plasma-desktop/commit/987cafc23638d59bc4e15a964931a04fe30aa988
Git commit 036fd9d18cef1d33f330ae91b9b272089493caa3 by David Edmundson. Committed on 02/12/2020 at 10:06. Pushed by davidedmundson into branch 'Plasma/5.20'. [kcms/users] Avoid race condition on startup If accounts service is not yet running the name will not be registered when we make our first call. We call into AccountsService from our client code with a blocking call. We then create a new QDBusAbstractInterface on a given service. QDBusAbstractInterface::isValid effectively is just a check that the service is registered. This might not be processed yet at the time we call this. It isn't a helpful check, if it wasn't up the previous call to fetch users would have failed. We can just remove it. (cherry picked from commit 987cafc23638d59bc4e15a964931a04fe30aa988) M +1 -1 kcms/users/src/user.cpp https://invent.kde.org/plasma/plasma-desktop/commit/036fd9d18cef1d33f330ae91b9b272089493caa3