Re: [systemd-devel] logind: Activating session/opening seat fails in systemd v254
On Fri, Feb 16, 2024 at 9:45 AM Lennart Poettering wrote: > > On Do, 15.02.24 22:16, Nils Kattenbeck (nilskem...@gmail.com) wrote: > > > Hi everyone, > > > > I am working on a kiosk-type device which is supposed to start a > > weston instance upon boot. > > Our images were previously based on Debian 12 and Fedora 38, now we > > are working on unifying them. Between the two old image variants the > > systemd units were mostly identical, however, on Fedora 39 with > > systemd 254 they no longer work. Weston/libseat now fails with the > > message: "Could not activate session: Permission denied". (Also see > > the logind logs at the end). > > Neither Weston nor libseat (whatever that is) are a systemd > thing. Please contact the relevant projects for help? I was asking this mailing list because it is not completely unheard of that systemd changes (or deprecates and subsequently removes) some aspects of how environments etc are set up sometimes. However, since the initial mail I have been able to try out different combinations of systemd and weston and could pinpoint this to a change in weston, which no longer uses logind directly but instead uses libseat as an abstraction. > libseat (whatever that is) Libseat is a library to allow using (e)logind and seatd with a common interface: https://github.com/kennylevinsen/seatd/blob/master/libseat/backend/logind.c Sadly it seems unable to properly activate the session according to my logs. (Previous weston versions also supported directly using logind but they removed it in newer versions.) Kind regards, Nils
Re: [systemd-devel] logind: Activating session/opening seat fails in systemd v254
On Do, 15.02.24 22:16, Nils Kattenbeck (nilskem...@gmail.com) wrote: > Hi everyone, > > I am working on a kiosk-type device which is supposed to start a > weston instance upon boot. > Our images were previously based on Debian 12 and Fedora 38, now we > are working on unifying them. Between the two old image variants the > systemd units were mostly identical, however, on Fedora 39 with > systemd 254 they no longer work. Weston/libseat now fails with the > message: "Could not activate session: Permission denied". (Also see > the logind logs at the end). Neither Weston nor libseat (whatever that is) are a systemd thing. Please contact the relevant projects for help? Lennart -- Lennart Poettering, Berlin
[systemd-devel] logind: Activating session/opening seat fails in systemd v254
Hi everyone, I am working on a kiosk-type device which is supposed to start a weston instance upon boot. Our images were previously based on Debian 12 and Fedora 38, now we are working on unifying them. Between the two old image variants the systemd units were mostly identical, however, on Fedora 39 with systemd 254 they no longer work. Weston/libseat now fails with the message: "Could not activate session: Permission denied". (Also see the logind logs at the end). I have been looking through the NEWS file and release announcement to see if I could spot any change which could have this impact but nothing stood out. Maybe someone else has a clue and remembers any recent change. This must have been a change between v253 and v254 as Fedora 38 is using the former and f39 is using the latter. Any help would be appreciated as I have worked on this for a few days now without success. (I can also try to create a MWE and publish the repo. It is build using mkosi so reproducing should be easy.) Kind regards, Nils
