It simply doesn't log in. #186
Comments
|
It looks like the upgrade of webkit2gtk (2.36.7-1 -> 2.38.0-2) broke it on my side. I did a downgrade and was able to login again. |
|
Yeah experiencing the same issue and was thinking that webkit2gtk update broke it as well :) |
|
Can confirm, I have the same issue, logfile (seat0-greeter.log) says: The login screen appears, but when I enter my password and hit enter, nothing happens |
|
Same for me, the webkit2gtk broke it :/ |
|
I'm happy I'm not the only one w/ problems lol
Can you tell me how to downgrade it? |
|
Experiencing the same issue, rolled back to default greeter, didn't realized webkit2gtk had been updated. Does version v3.2.0 fix the problem? |
|
Same problem here. Downgrading webkit2gtk packages solves the problem on Arch. |
|
A bug report was open on arch > https://bugs.archlinux.org/task/75988 |
|
I also experienced same issue, it may all lightdm-webkit2-greeter themes problem. edit |
Exactly what I did actually! https://github.com/antergos/web-greeter is dead anyways so better use something more up to date |
|
TLDR: Seems there is no way to fix this. I tried to look into this error in Arch with WebkitGTK 2.38, and it seems like WebkitGTK 2.38 runs webkit extensions in a sandboxed environment or similar, so all connection tries to the LightDM daemon fails inevitably. Therefore, there is no way to fix this error unless WebKitGTK decreases security regarding webkit extensions (maybe there is an option for this) or lightdm-webkit2-greeter is rewritten to connect to LightDM from the main program instead of connecting from the extension (which is unlikely). How I tested itI added the following lines to lightdm-webkit2-greeter source code at GError *err_conn = NULL;
gboolean connected = lightdm_greeter_connect_to_daemon_sync(greeter, &err_conn);
fprintf(stderr, "Connected: %d\n", connected);
if (err_conn != NULL) {
fprintf(stderr, "Error: %s\n", err_conn->message);
g_error_free(err_conn);
} else {
fprintf(stderr, "There is no error message\n");
}So, this would check if the connection to the LightDM daemon success. Here's the result in As you can see, when trying to connect from the main program ( AlternativesI did the same test with my own program sea-greeter, which is made with WebkitGTK and it does work flawlessly. My fork of web-greeter and nody-greeter do work as well. |
|
That's unfortunate. I'm going to take a look at sea-greeter then. I'm going to keep it open because it isn't fixed, when it gets fixed, I'll close it. |
|
https://bugs.archlinux.org/index.php?do=details&action=details.addvote&task_id=75988 |
|
@JezerM I tried your web-greeter fork, however the litarvan theme seems to be throwing a lot of errors for me with that greeter (some js functions appear to be missing) How did you get it to work with your web-greeter? |
works good for me. Installed it with yay from AUR. |
I am getting these errors: |
|
Getting the same "lightdm.language.toLowerCase is not a function" error when using the web-greeter with the latest lightdm-webkit-theme-litarvan release 3.2.0 from Github. community version is still 3.1.0. |
Try using the |
|
Just tested with the version from the master branch. It does not show any errors and boots up correctly, however. I am stuck on the splash screen now (where it says "Press Space or Return"). It seems none of my keypresses are registered. I use this shell function to install the theme: |
|
|
Thanks it worked now, only the dpi settings seem to be different compared to the older webkit2 greeter |
|
Try the master version. Litarvan's 3.2.0 version still uses some deprecated lightdm-webkit2-greeter and wasn't updated to web-greeter/nody-greeter/sea-greeter, which is fixed in the master branch. |
|
yeah I am using the master branch |
Doubt it. There is no sandboxed environment unless you enable it manually using By the way, the only relevant change I can think of between 2.36 -> 2.38 is that leaked file descriptors no longer inherit into the child processes (at least for now, might get reverted). So if the parent process opens a file descriptor, forgets to set CLOEXEC, and accidentally relies on it in the child process, then that would have previously worked, but not anymore. That scenario seems extremely unlikely, though. |
|
Oh, yeah, lightdm-webkit2-greeter doesn't enable a web-context sandbox, so my hypothesis is incorrect. I don't think |
|
Can you check if WebKit/WebKit#4868 fixes the problem for you? It really shouldn't, as that would indicate a very weird lightdm or lightdm-webkit-greeter bug... but it's worth checking. |
|
Hey everyone, after running a sudo pacman -Syu yesterday I'm also facing this issue with my greeter. Since I'm basically "locked out" of my laptop rn, how should I change stuff to fix it? |
|
@tanish1729 you can fall back to tty with Ctrl+Alt+F2, and then |
Yep perfect. I just didn't know about the Ctrl+Alt+F2 thing. Thanks a lot :)) |
|
Same here, I don't want to manually change webkit2gtk versions, so I guess I'll look for a different theme. Shame, I really liked this one, and I'll definitely give it a chance again if it gets updated. Also, sometimes changing tty doesn't work especially if you have your lightdm service set to restart on crash, and mess up your config, as it will always grab focus to tty7... So always have a live installation of linux on hand. Edit: other themes also don't work, so I guess it's an issue with the greeter itself |
|
Btw, I found out what caused the difference in DPI from the old webkit greeter: The setting in |
|
As reported above by mcatanzaro, I opened a ticket here: https://bugs.webkit.org/show_bug.cgi?id=246206 But I am unable to get a gdb backtrace; if someone could, please report a gdb backtrace. |
|
For anyone waiting on this. It seems like the issue is fixed with the new version of lightdm-webkit2-greeter. At least it's working for me again. |
|
Likewise. I believe this can be closed now (and, regardless, the issue was never with the theme to begin with). |
No, rather the process launching change was simply reverted in WebKit. It may break again in the future if lightdm-webkit2-greeter does not reconsider its IPC strategy. See WebKit/WebKit#4868 for more details. |
|
I'd say to report the issue to lightdm-webkit2-greeter instead, but seems like the repository has been archived. I guess that, unless someone is willing to fork it and fix this issue, its days may be numbered. |
lightdm-webkit2-greeter hasn't been updated in years, so no, this hasn't been fixed; perhaps WebKit reverted a breaking change for webkit2-greeter. But as mcatanzaro says, it may break again in the future.
Yeah, I already did that xd |
and others
I power on my computer, LightDM loads up, I type in my password and it simply does nothing, besides not letting me interact with the text box anymore. I had to switch to another tty and change lightdm.conf to use lightdm-gtk-greeter to log in. Does anyone have an idea of what is happening?
My /var/log/lightdm/lightdm.log.old: http://0x0.st/oWzr.txt
My /var/log/lightdm/seat0-greeter.log.old: http://0x0.st/oWzz.txt
My /var/log/lightdm/x-0.log.old: http://0x0.st/oWzi.txt
The text was updated successfully, but these errors were encountered: