Jezer Mejía

Does this occurs when **logged in** (inside a Desktop Environment/Window Manager) or inside the **LightDM environment** (when trying to log in)?

I can't even run `nody-greeter` in Fedora, the window is never shown... Sincerely, I don't know why.

`lightdm-webkit2-greeter` and LightDM itself doesn't allow nor recommend to "inspect" the home folder, no matter you change the permissions. You need to change the default `background_images` path to one that...

You could use [nody-greeter](https://github.com/JezerM/nody-greeter), one of the successors of lightdm-webkit2-greeter, and my [Aether fork](https://github.com/JezerM/Aether), which fixes the incompatibility issues. This greeter has multi-monitor support, though it would only replicate the...

Actually, this is possible, but not the most convenient thing to have. **LightDM GTK+ Greeter** does something similar, accessing to the background property each LightDMUser object has. But as far...

You can set your icon with [mugshot](https://github.com/bluesabre/mugshot), or your DE configuration. Also, you can copy your desired image to your home directory as: `~/.face`, and it should work.

Seems to be an upstream error about [node-gyp-bins](https://github.com/nodejs/node-gyp/issues/2713). I'll look for a solution soon~

No, sorry, I haven't had time to see through this error. Also, it seems there is a [PR](https://github.com/nodejs/node-gyp/pull/2721) trying to solve it in nody-gyp, but it hasn't been completed nor...

@D3vil0p3r, the issue is not that the Display Manager doesn't spawn, the issue is actually that lightdm-webkit2-greeter tries to connect to the Display Manager (LightDM) through webkit2 extensions and it...

Exactly, that's because lightdm-webkit2-greeter cannot connect to the LightDM daemon. LightDM can show the greeter without being connected as the greeter (lightdm-webkit2-greeter) can choose when to connect; the main issue...