Draft: systemd/systemd-services: include user-mobi.phosh.Shell.service

required to start Phosh

Closes #3460 (closed) Closes #3464 (closed)

mentioned in issue #3464 (closed)

I'm not exactly sure, why it is now required and not before, but the user service seems to be required to start Phosh directly from gnome-session.

approved this merge request

approved this merge request

approved this merge request

Needs conflicts to be fixed.

Took the liberty to rebase and resolve the conflicts.

marked this merge request as draft

added 54 commits

• a0ab0dae...c90592c9 - 52 commits from branch postmarketOS:master
• 4b3c1c38 - systemd/systemd-services: include user-mobi.phosh.Shell.service (MR 6044)
• d9458350 - systemd/systemd-services: fix libexecdir of user-xdg-desktop-portal-phosh.service (MR 6044)

Compare with previous version

Tested this MR via mrtest, also running into #3464 (comment 463725)

mentioned in merge request !6070 (closed)

mentioned in issue #3476

The issue with this MR is:

Okay yah, can reproduce it, for some reason it did work for me before.

For once mobi.phosh.Shell.target is needed, that's pretty easy to include in systemd-services. But also /usr/lib/systemd/user/gnome-session@phosh.target.d/session.conf is required, that does not sound nice to include in systemd-services.

Most likely it makes sense to fork phosh and move the systemd files in a subpackage directly.i

See #3464 (comment 463728)

So it most likely makes more sense to solve this issue another way hence closing this MR, most likely with forking phosh and adding a -systemd subpackage. Even more great would be if we didn't have to fork and Alpine could offer the -systemd subpackage.

I suggest we fork it from alpine for now, so we have a working version again in pmOS edge.

We can do the proper -systemd subpackage and remove the fork once #2804 is done (we are actually making good progress there!)

and thanks for all the work with looking into this, etc!

closed

This one is only needed if phosh isn't started via a display manager. It's mostly for debugging.

AFAIK we start without a DM and directly enable phosh.service

I'd recommend to use a DM as otherwise you don't go through the whole pam stack. pmOS did that with lightdm before, isn't that a thing anymore? On Debian we use phog (soon phrog, just waiting for NEW processing in by Debian's ftp-masters). That will also be required for phosh's first boot experience, etc soon. As it uses greetd users can also set up autologin, etc if desired.

Not sure why, but we could theoretically also run it using tinydm, see also tinydm#11.

The DM has the user credentials for the different PAM phases, a systemd unit doesn't (as it doesn't have the password/pin) so I think there would always be difference but likely I'm missing something?

Yeah we had issues with not having the user's keyring unlocked properly on boot before... and we would get that again if we used tinydm. Using phrog sounds to me like the best way forward here.

Thanks for the feedback Guido!

@agx / @ollieparanoid I got greetd working with the gtkgreeter. But when I try to run the phrog greeter, I get the following error:

Jan 25 20:25:48 xiaomi-beryllium phrog[1001]: Error: failed to detect Wayland compositor globals
Jan 25 20:25:48 xiaomi-beryllium phrog[1001]: Caused by:
Jan 25 20:25:48 xiaomi-beryllium phrog[1001]:     Could not find wayland compositor
Jan 25 20:25:48 xiaomi-beryllium greetd[992]: error: check_children: greeter exited without creating a session
Jan 25 20:25:48 xiaomi-beryllium systemd[1]: greetd.service: Deactivated successfully.

Any idea what could the reason be?

btw just wanted to update here. I will see if i can debug it further and probably ask in the phrog repo too.

It can't detect the necessary Wayland globals (the startup checks if the running compositor is phoc). How are you launching phrog. This is what Debian uses:

• launch script: https://salsa.debian.org/DebianOnMobile-team/phrog/-/blob/debian/latest/debian/bin/phrog
• greetd config that launches the script: https://salsa.debian.org/DebianOnMobile-team/phrog/-/blob/debian/latest/debian/config/greetd/phrog.toml

I'll file an isuse to include such config upstream.

@joelselvaraj see https://github.com/samcday/phrog/pull/80 . A good place for questions is also Phosh's matrix room, Sam (phrog's upstream) hangs out there too: https://matrix.to/#/#phosh:sigxcpu.org

mentioned in merge request !6106

mentioned in merge request !6108 (merged)

mentioned in issue build.postmarketos.org#152 (closed)