Error building from source on Fedora 43 with GNOME 49.2

[rosscondie]

I followed the instructions to build from source and after dropped into a tty to test it out.

I ran sudo systemctl stop gdm and then sudo systemctl start lidm and everything looked good. I tried to log into both Niri and GNOME sessions and was met with a different error than what I encountered following the COPR build issue:

exec error: Permission denied
failure calling session

I am not quite sure how to debug this properly so I am happy to provide more logs if needed.

I did some GPT debugging and it mentioned something about XDG_RUNTIME_DIR being missing from the moarEnv() function in src/auth.c and also that pam_systemd.so was only in anaconda so PAM isn't setting up systemd-logind integration.

I did try adding these both but it still gave me the same error.

[javalsai]

I did some GPT debugging and it mentioned something about XDG_RUNTIME_DIR being missing from the moarEnv() function in src/auth.c

It's currently commented out, or at least was, but because I managed to make PAM provide that env variable, it should be present in the actual environment, I highly doubt that's the case.

and also that pam_systemd.so was only in anaconda so PAM isn't setting up systemd-logind integration.

There's no straight systemd dependency in lidm and I don't think I'll ever do. It actually just uses the login PAM header by default (which can be tweaked at build time, more info in docs/PACKAGERS.md iirc).

That should correspond with /etc/pam.d/login if you wanna check the contents, it depends on the distro but should integrate enough. Also, knowing the security side of fedora, the issue is likely with some PAM thing like this.

---

For debugging further, no need to systemctl start/stop every time, you should be able to just go into a TTY and run lidm as root every time you need. But careful, because the TTY login might provide the environment lidm is missing to get in the first place, just check the issue happens like this too.

Also, you can provide LIDM_LOG env to log to that given path (e.g. sudo LIDM_LOG=/tmp/mylogs lidm), BUT the logging is quite bare-bones and I think it barely logs anything relating to PAM, so I doubt you'll get anything out of this.

As a takeaway I'll try to add some debugging for env related stuff in lidm after this, I usually just inject some code in my machine but I can't go around asking people to meddle with the code this much.

---

Also, because I don't let shell sessions perform the complete login process, they shouldn't add much env over lidm. That might be helpful to debug too, instead of launching gnome or a graphical session, try a shell and check what's missing in env (like XDG_RUNTIME_DIR).

Finally, thanks for going through so much trouble to debug it for me 🙏. Idk how ppl find the energy to deal with it when my code is so messy.

[grialion]

That should correspond with /etc/pam.d/login if you wanna check the contents, it depends on the distro but should integrate enough. Also, knowing the security side of fedora, the issue is likely with some PAM thing like this.

I just checked and running the new branch yields different environment lists as a service, and as running from a shell. Stace logs look identical.
I can't wrap my head around PAM, so I'll just leave this here.

[javalsai]

I tried to log into both Niri and GNOME sessions

Could this be both #101 and #97??

[rosscondie]

For me the niri.desktop entry calls niri-session without the space so I don't think that would be related:

[Desktop Entry]
Name=Niri
Comment=A scrollable-tiling Wayland compositor
Exec=niri-session
Type=Application
DesktopNames=niri

and running gnome-session doesn't do anything for me from a tty either.

[javalsai]

Can you check on the latest changes??

Recently merged a PR that fixed several stuff related to this.

[rosscondie]

I rebuilt the latest from source but still get the same permission denied error. When trying to login to both GNOME and Niri sessions.