New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sddm 0.12.0 does not focus the password field and the keyboard does nothing #501
Comments
I was about to report an issue for this and I saw that someone had already done it. Every sddm functionality must be accessible with the keyboard. I also agree that the password field must be focused by default. |
What theme are you using? |
I encountered the same behaviour with the maui theme and just tested it with elarun, circles and maledives which show the same behaviour. For Maledives I just noticed that when you click outside of the box with the input fields, you also can't get back to the password field via tab key. I did not test that with other themes, though. |
Hello. I don't know if the issue being reported as a bug prevents it from having others (like myself) to report the same behavior as well. Nevertheless I must enroll myself to the list of those who suffer from this issue (on both my pc's running up-to-date ArchLinux) I also am going to refer this on the #archlinux irc channel, since I've been there yesterday and this was unknown there. Also, will subscribe to this thread to see if/how I can collaborate even further. Regards. |
This isn't a themes bug @plfiorini. This affects all themes that I tried, and even when I added Note that it does seem to work if you do e.g. |
Mh, well i use a custom theme, based on elarun, without the lastUser is displayed. |
I'm facing the same problem with all the standard sddm themes on Arch. But when I applied the archlinux-soft-gray theme from the archlinux-themes-sddm package, the problem is gone and the password field is focused ready for typing in. |
It worked after I copied the timer cludge from the kde login manager into SddmComponents/PasswordBox.qml TextBox {
id: txtMain
width: parent.width
height: parent.height
font.pixelSize: 14
echoMode: TextInput.Password
focus: true
Timer {
interval: 200
running: true
onTriggered: txtMain.forceActiveFocus()
}
} |
One of the issue that "heirecka" reported above,
can easily be fixed! KeyNavigation.backtab: pw_entry; KeyNavigation.tab: user_entry Here i have an example for the elarun main.qml Repeater {
model: screenModel
Background {
x: geometry.x; y: geometry.y; width: geometry.width; height:geometry.height
source: config.background
fillMode: Image.PreserveAspectCrop
/* insert here the TabKeyNavigation row */
KeyNavigation.backtab: pw_entry; KeyNavigation.tab: user_entry
onStatusChanged: {
if (status == Image.Error && source != config.defaultBackground) {
source = config.defaultBackground
}
}
}
} edit: it seems so, that you need to integrate the timer hack/kludge, to get focus the first time. |
Would that also fix the initial autofocus, or only allow to switch via tab key to first input field? |
No, that doesn't fix the initial focus, you need that "timer hack". |
I've hit this on 0.13.0 on NixOS, with |
same problem with 0.13.0 on NixOS with default theme |
I did some preliminary test, I did put this inside the
If I start Xorg with startx, the interface is started without focus on the password field.
And now I did have the focus on the password field... |
I did run a bisect (between v0.11.0 and v0.12.0) and I found that the problematic commit is : 947b8d1 |
I am so sorry to ask that but the project is dead ? There is a pull request that fix the issue... |
I have actually stopped experiencing this issue as of a few weeks ago (on two different systems, one of which has two displays). I am on Arch Linux with extra/sddm 0.13.0-2. I don't believe there's been an SDDM update since I stopped having the issue - so maybe it's somehow a configuration change or another package update. However, it might have been the upgrade to 0.13.0 (maybe I just didn't notice for a while). |
I'm also on arch and it's still bugged in 0.13.0-2. |
I am running a custom build of sddm in my Arch Linux that has this pull request in. I have sddm-0.13.0-2 in my local packages, that was the last version I tried and that had the same issue for me too. Hopefully this can get merged and fixed soon. |
Oh men... I was just so fed up with this focus issue that i nose dived into the code to figure out what was wrong. I hacked several things before i checked out git to see if it had any updates. I'm glad it has, it fixes my no.1 issue :) Too bad i didn't look at git right from the start. Please do release a new version with this. It's a really annoying bug on multiscreen setups! |
This issue is still present in Manjaro 4.4.13-1-MANJARO |
With version 0.14.0-6.1 it's fixed. Yeeha! :) |
I started experiencing this issue too, the moment I switched from the Intel modesetting driver to the DDX driver. Running version |
Kubuntu 18.04.1 when booting with external monitor, can't input password keyboard does work and can change to a different terminal workaround:
after the service restarts, it will automatically change your terminal to the graphic login. |
In my case, an solution to fix the problem is search in de main.qml or login.qml in which part are located the form or the input for the password, and in this put the property focus:primaryScreen, this make than you can put your password, press enter and login, but you can't see the password field changing(this because in dual monitor the screen by default is not the primary), in the case of you are using lubuntu default theme, just replace "focus:true" to "focus:primaryScreen" at the line 130 in Main.qml located in /usr/share/sddm/themes/lubuntu/ |
When booted up SDDM comes up with the last used username selected and the password field apparently "focused" but in reality it is not, as when I try to type it does nothing. Also the keyboard keys (e.g. TAB) don't do anything at all at that moment until I use the mouse to click on the password field which then I can type in the password and also use TAB to move around the fields.
The text was updated successfully, but these errors were encountered: