Alexey Lebedeff

@yorickvP Yes, it's exposed - e.g. search for `GitSHA1` in https://raw.githubusercontent.com/commercialhaskell/lts-haskell/master/lts-12.16.yaml If non-breaking updates are OK, why you've enabled the sandboxing? =)

I was checking the environment where `uwsm start` runs, and comparing it to the `session.slice` environment before `uwsm start` (I've got it by changing Exec in wayland session .desktop file)....

Sadly, the inconsistent environment story makes uwsm unsuitable as a drop-in replacement for direct starting of a compositor by a display manager. I went through some pam modules to see...

Out of curiosity I've checked what KDE does to set and clean-up variables, and where it does it in it's lifecycle. - It fetches current env from systemd, and remembers...

Yes, everything just works with the latest commit. I've removed all my hacks. Thank you!

@GabeDuarteM You can try adding ``dbus-update-activation-environment --systemd PAM_KWALLET5_LOGIN`` before `uwsm start`. That's what I did before the fix was merged.

I've tested it, with 4.0.6 from alpine repo, with only this patch applied on top. Now it's fine, the amount of disk reads is approximately the same as the seeding...