Summary:
Meaning pressing enter just wakes up the display.
Behaviour now matches lock screen.
BUG: 402957
Test Plan: Ran SDDM
Reviewers: #plasma, ngraham
Reviewed By: ngraham
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D17997
Summary: "Login" is a noun: "I have a login for the system." This is not appropriate for a button title that is used as an action; the correct verb-based string is "Log In".
Test Plan: {F6311398}
Reviewers: #vdg, #plasma, abetts
Reviewed By: #vdg, abetts
Subscribers: abetts, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D16035
Summary: Currently nothing happens when pressing enter in the username field.
Test Plan:
Entered username, pressed enter.
Now the cursor is in the password field.
Reviewers: #plasma, broulik, davidedmundson
Reviewed By: #plasma, broulik, davidedmundson
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D12510
Summary:
for both lockscreen and login screen:
* display the wallpaper and the clock with a shadow by default
* at the first mouse or keyboard input, make the input fields appear
* the actual controls appear pretty fast
* the wallpaper starts to blur, desaturate and fade to darker
* after 10 seconds make the controls disappear again
* as soon as anything is written in the password field never fade out the controls
* if the virtual keyboard is open, never fade out the controls
* if anything is pushed on the stack, like "switch user", never fade the controls
* Esc clears the field and makes controls disappear (closing keyboard if needed)
the fade won't happen if the background is a simple color
BUG: 369676
BUG: 388622
FIXED-IN: 5.13
Depends on D12314
Recommended D11309 and D11308 to change the default wallpaper to plasma wallpaper
Test Plan: tested the behavior of all the above points
Reviewers: #plasma, #vdg, ngraham
Reviewed By: #vdg, ngraham
Subscribers: zzag, abetts, davidedmundson, ngraham, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D11928
Summary:
Similar to D4893, use a state machine to track the status of the
keyboard and animate the open/close.
this improves also the layout on low and weird resolutions when
there isn't much available space
Test Plan:
tested with many different window sizes, to make sure it
behaves better than before
Reviewers: #plasma, davidedmundson, graesslin, broulik
Reviewed By: #plasma, broulik
Subscribers: apol, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D5254
Allows to show the password on click, similar to how it's done in most other
password fields throughout the workspace.
Differential Revision: https://phabricator.kde.org/D3616
When we default to the user input we would not remember the user name.
CHANGELOG: Login screen now remembers the last user name for domain logins where the user list is unavailable
Differential Revision: https://phabricator.kde.org/D3462
Summary:
Renamed userPrompt to userPromptComponent and add an id
(userListComponent) to the initialItem Login component.
Disable user list when there are too many users in the system
In sddm 0.14, there's a userModel.disableAvatarsThreshold property
that defines how many users are "too many" in the system so loading of
avatars should be disabled. This commit honors that property, so if
there are more than disableAvatarsThreshold users, then the user list
is disabled and a prompt is shown to ask for a username and password.
If the property is not available (for example, because sddm 0.13 is
being used) then it works as usual.
This threshold is specially useful for large enterprises with NFS
automounted home directories. In such environments, using sddm while
avatars are enabled results in all remote home directories being
mounted in the system before one user is able to log in. This has been
reported to take hours in cases with thousands of users.
By default the threshold has a value of 7, but it can be modified
in sddm.conf, under the Theme section, in the
UsersThresholdToDisableAvatars variable.
Reviewers: #plasma, davidedmundson
Reviewed By: #plasma, davidedmundson
Subscribers: davidedmundson, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D2874
When logging in failed, focus the password field and select all, so you can start typing a new password thereafter.
I did the same in the lock screen.
There's a workaround for a bug which draws focus away from the password field on login
but never put it back if logging in failed.
Differential Revision: https://phabricator.kde.org/D2767
Summary:
Implements the new SDDM theme
Code is written with the intention to easily port the lock screen
All SDDM related code is now shifted into Main with Login.qml acting as
an abstraction layer.
Test Plan: Ran it, against the awesome mock data.
Reviewers: #plasma, mart
Reviewed By: mart
Subscribers: bshah, mart, apol, plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D2399
Summary:
Currently we install sddm theme twice, once where sddm expects theme and
another in look&feel package. This duplicate installation is not really
a good idea because one in look-and-feel is completely unused.
Reviewers: davidedmundson, mart, sitter
Reviewed By: sitter
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D2351
This is a part from yet another new login screen design which I find much nicer.
It's pretty late in the cycle so let's just only add the new clock and then
do the rest later.
Also minute align the clock data engine and only poll every 60s instead of every second
Summary: Implemented the new login screen as designed by Andreas
Test Plan: As there is a dummydata folder, simply run qmlscene Main.qml
to test
Reviewers: #plasma
Subscribers: plasma-devel
Tags: #plasma
Differential Revision: https://phabricator.kde.org/D1670