Artix Linux Forum

I installed the artix fork of dinit-userservd (https://github.com/Xynonners/dinit-userservd (https://github.com/Xynonners/dinit-userservd)), started the service, and added "session optional pam_dinit_userservd.so" to /etc/pam.d/login, but the dinit user instance still doesn't spawn. What might I be missing here?

Do you have your user services set up (i.e. service descriptions in place), including a `boot` service?

Yes, I've been using dinit user services for a while now by autostarting dinit in KDE.

Anything in /var/log/dinit-userservd.log?

It's completely empty. The process dinit-userservd itself starts just fine though, it just doesn't spawn the user dinit instance for whatever reason.

dinit-userserv is a fork of what is now called turnstile.
Maybe this can help https://github.com/chimera-linux/turnstile/issues/6.

It does work for me. Make sure your /etc/security/login is correct with modules in the right order. Mine looks like:

#%PAM-1.0

auth required pam_securetty.so
auth requisite pam_nologin.so
auth include system-local-login
account include system-local-login
session include system-local-login
session optional pam_dinit_userservd.so
password include system-local-login

If that's what you also have and it doesn't work, I guess you would need to debug it. See if you can find if PAM itself has logged anything; perhaps try running strace on the dinit-userservd process.

Same here and I used the /etc/security/login above.

Do you use "strace dinitctl restart dinit-userservd" to debug?

You need to trace dinit-userservd, not dinitctl. I was thinking along the lines of:

• login on a virtual terminal as root, strace the dinit-userservd process by its pid
• seperately log in as user
• go back to the root terminal and check the trace for activity

If you see activity in the trace, hopefully it gives some clue to what's going wrong. If there's no activity it means your PAM configuration isn't right or the pam_dinit_userservd.so PAM module isn't working properly; in either case the PAM logs are probably the best bet.

same issue here with dinit-userservd. service itself starts, but user services do not run. /var/log/dinit-userservd.log does not show anything and /etc/security/login does not exist in my case. well, is should be in /etc/pam.d/login but still it cannot run user service or write anything to its logfile.

running the dir with dinit as user works fine.

UPDATE:
well i got it fixed. from the reddit post, 'session optional pam_dinit_userservd.so' should be in '/etc/pam.d/system-login' (at least for me) and not in /etc/pam.d/login as the original guide suggested. now dinit-runservd spawns dinit --user correctly and runs users services fine.

new issue though. as using this method will cause "dinitctl" to loose the socket of dinit when you logout from the session and log back in. you needed to reboot in order for this to work again. not sure how to deal with that yet.

Putting it in login works for me, but that's with console login. If you're using a display manager it could be different. I think system-login is probably more correct; that seems to get included by other logins anyway.

However:


I'm pretty sure elogind is managing the runtime dir, so I believe it's important to make sure that the elogind pam module is listed before the dinit-userservd module. With that arrangement, it all works fine and I don't get this problem. On the other hand if I put them the other way around, dinitctl never has a socket to work with, so this doesn't seem to be exactly the same as what you're describing.

well, i guess my problem because i was using greetd/greetd-gtkgreet combo as my login manager.  somehow it breaks the user session. logging in through TTY work fine. not tested yet if things still work when switching to another user.

Using /etc/pam.d/system-login worked but some services that normally works now fail.

cat /etc/pam.d/system-login 
#%PAM-1.0

auth       required   pam_shells.so
auth       requisite  pam_nologin.so
auth       include    system-auth

account    required   pam_access.so
account    required   pam_nologin.so
account    include    system-auth

password   include    system-auth

session    optional   pam_loginuid.so
session    optional   pam_keyinit.so       force revoke
session    include    system-auth
session    optional   pam_motd.so
session    optional   pam_mail.so          dir=/var/spool/mail standard quiet
session    optional   pam_umask.so
-session   optional   pam_elogind.so
session    required   pam_env.so           user_readenv=1
-session    optional   pam_rundir.so
session optional pam_dinit_userservd.so

Also after logging out it wasn't working anymore, dinitctl couldn't find the dinit instance.
I ran pkill dinit, there was a process, and after logging out the instance was fine.
I logged out a few times looks like it is always like that.

picom:

[ 09/28/23 21:32:52.123 main FATAL ERROR ] Can't open display.

pasystray:

option parsing failed: Cannot open display: 
option parsing failed: Cannot open display: 
option parsing failed: Cannot open display: 

wireplumber:

Error acquiring bus address: Cannot autolaunch D-Bus without X11 $DISPLAY
M 21:32:51.530117            pw.core ../pipewire/src/pipewire/core.c:180:destroy_proxy: 0x55855eb08730: leaked proxy 0x55855ebaa280 id:4
M 21:32:51.530226        wireplumber ../wireplumber/src/main.c:364:on_disconnected: disconnected from pipewire
Error acquiring bus address: Cannot autolaunch D-Bus without X11 $DISPLAY
M 21:32:51.736933            pw.core ../pipewire/src/pipewire/core.c:180:destroy_proxy: 0x558fe612b550: leaked proxy 0x558fe61c46d0 id:3
M 21:32:51.736994        wireplumber ../wireplumber/src/main.c:364:on_disconnected: disconnected from pipewire
Error acquiring bus address: Cannot autolaunch D-Bus without X11 $DISPLAY
M 21:32:51.934022            pw.core ../pipewire/src/pipewire/core.c:180:destroy_proxy: 0x55cf5a326550: leaked proxy 0x55cf5a3be9b0 id:3
M 21:32:51.934076        wireplumber ../wireplumber/src/main.c:364:on_disconnected: disconnected from pipewire
Error acquiring bus address: Cannot autolaunch D-Bus without X11 $DISPLAY
M 21:32:52.135160            pw.core ../pipewire/src/pipewire/core.c:180:destroy_proxy: 0x56508faf3690: leaked proxy 0x56508fb8f870 id:3
M 21:32:52.135249        wireplumber ../wireplumber/src/main.c:364:on_disconnected: disconnected from pipewire

@kikblaster

what loginmanager are you using?

it appears that when using only tty to login/logout, the '/run/user/$UID' does not gets wipe hence dinitctl in user-mode works. while when using loginmanager (i've used greetd and ly) '/run/user/$UID'  is wiped out. and no matter how dinit-userservd is restarted it can never respawn a dinit instance for the currently logged-in user.

https://aur.archlinux.org/packages/tinydm-dinit
tinydm.

Please note that dinit-userservd has never been supported, and the "Artix fork" of it has been unmaintained for some time. However, turnstile nowadays is practically distro-neutral and has distro interoperability as its priority.

Hence, to make it easier for all interested users to try it (and also that I actually am using it right now to test it), I've added all turnstile-related packages along with some example services (dbus, pipewire, wireplumber, mpd) that actually works in my case to the [galaxy] repo under the turnstile-experimental group, so you would need to enable it in /etc/pacman.conf. I hope the addition becomes a useful data point for turnstile developers for bugs, quirks, and whatnot. Also, if possible (albeit unrelated to dinit), I hope it gets another service manager backend (such as s6).

Please note that this does not mean I'm officially supporting turnstile (yet, at least).

thanks. just did a quick test (installed and enabled turnstile-experimental and all modules) and session appears to be working fine after login/logout and login back.

Since turnstile-0.1.8-3, the system dinit service of turnstile has been separated from the turnstile main package (it should be on turnstile-dinit now), you will need to install it separately.

Also, because turnstile is primarily concerned with user services, there's no reason to restrict turnstile to depend on dinit, preventing users with other init systems to try it. Therefore all user service packages and turnstile itself will only depend on dinit-base so you would only need the dinit binaries (also the fact that dinit is the only turnstile backend, for now).

On an aside note (albeit unrelated to dinit), turnstile-openrc package has been added to galaxy so users with OpenRC as their init system can try it.

I installed turnstile, enabled the service and rebooted.

User dinit cannot conncet to the socket, there is no dinit process at all, but dinitctl shows it fine:

[{+}     ] turnstiled (pid: 579)

Have you set the PAM config? Either install pambase-turnstile or edit /etc/pam.d/system-login directly.

I now installed pambase-turnstile and it is as before.
I also rebooted.

What's the output of these commands?
$ cat /etc/pam.d/system-login
# cat /var/log/turnstiled.log

turnstile-0.1.8-3 works fine on my end. no real complains for now. will probably soon move my user-daemons there and others...

I was using turnstile-0.1.8-2, now I updated to turnstile-0.1.8-3.
There is a problem with some KDE things that prevented me to update:

:: Starting full system upgrade...
[...]
:: knotifications5 and knotifications are in conflict. Remove knotifications? [y/N] y
:: kwindowsystem5 and kwindowsystem are in conflict. Remove kwindowsystem? [y/N] y
:: kconfig5 and kconfig are in conflict. Remove kconfig? [y/N] 

It works as dinit-userserv the same service that normally works are now failing.
Does it need to run dbus service? I am using instead "exec dbus-launch --exit-with-session bspwm".

  cat /etc/pam.d/system-login
#%PAM-1.0

auth       required   pam_shells.so
auth       requisite  pam_nologin.so
auth       include    system-auth

account    required   pam_access.so
account    required   pam_nologin.so
account    include    system-auth

password   include    system-auth

session    optional   pam_loginuid.so
session    optional   pam_keyinit.so       force revoke
session    include    system-auth
session    optional   pam_motd.so
session    optional   pam_mail.so          dir=/var/spool/mail standard quiet
session    optional   pam_umask.so
-session   optional   pam_turnstile.so
-session   optional   pam_elogind.so
session    required   pam_env.so           user_readenv=1
-session    optional   pam_rundir.so

cat /var/log/turnstiled.log
srv: pam_close_session: Cannot make/remove an entry for the specified sessiondinit: In multiple cgroups, cannot determine cgroup root path
dinit: Could not open dependency directory '/usr/lib/dinit.d/user/boot.d' for system service.
[  OK  ] system
[  OK  ] picom
[  OK  ] pipewire.user
[  OK  ] pasystray
[  OK  ] pipewire-pulse.user
[  OK  ] wireplumber.user
[  OK  ] boot
Service 'boot' started.
dinit: Service picom process terminated with exit code 1
[STOPPD] picom
[  OK  ] picom
dinit: Service picom process terminated with exit code 1
[STOPPD] picom
dinit: Service wireplumber.user process terminated with exit code 70
dinit: Service pasystray process terminated with exit code 1
[STOPPD] pasystray
[  OK  ] pasystray
dinit: Service wireplumber.user process terminated with exit code 70
dinit: Service pasystray process terminated with exit code 1
[STOPPD] pasystray
[  OK  ] picom
dinit: Service picom process terminated with exit code 1
[STOPPD] picom
[  OK  ] pasystray
dinit: Service pasystray process terminated with exit code 1
[STOPPD] pasystray
dinit: Service wireplumber.user process terminated with exit code 70
[  OK  ] picom
dinit: Service picom process terminated with exit code 1
dinit: Service picom restarting too quickly; stopping.
[STOPPD] picom
[  OK  ] pasystray
dinit: Service wireplumber.user process terminated with exit code 70
dinit: Service wireplumber.user restarting too quickly; stopping.
dinit: Service wireplumber.user restarting too quickly; stopping.
[STOPPD] wireplumber.user
dinit: Service pasystray process terminated with exit code 1
dinit: Service pasystray restarting too quickly; stopping.
[STOPPD] pasystray
[  OK  ] wireplumber.user
dinit: Service wireplumber.user process terminated with exit code 70
dinit: Service wireplumber.user process terminated with exit code 70
dinit: Service wireplumber.user process terminated with exit code 70
dinit: Service wireplumber.user process terminated with exit code 70
dinit: Service wireplumber.user restarting too quickly; stopping.
dinit: Service wireplumber.user restarting too quickly; stopping.
[STOPPD] wireplumber.user
[  OK  ] picom
dinit: Service picom process terminated with exit code 1
[STOPPD] picom
[  OK  ] picom
dinit: Service picom process terminated with exit code 1
[STOPPD] picom
[  OK  ] picom
dinit: Service picom process terminated with exit code 1
[STOPPD] picom
[  OK  ] picom
dinit: Service picom process terminated with exit code 1
dinit: Service picom restarting too quickly; stopping.
[STOPPD] picom
[  OK  ] pasystray
dinit: Service pasystray process terminated with exit code 1
[STOPPD] pasystray
[  OK  ] pasystray
dinit: Service pasystray process terminated with exit code 1
[STOPPD] pasystray
[  OK  ] pasystray
dinit: Service pasystray process terminated with exit code 1
[STOPPD] pasystray
[  OK  ] pasystray
dinit: Service pasystray process terminated with exit code 1
dinit: Service pasystray restarting too quickly; stopping.
[STOPPD] pasystray
[STOPPD] boot
[STOPPD] system
[STOPPD] pipewire.user
[STOPPD] pipewire-pulse.user
dinit: In multiple cgroups, cannot determine cgroup root path
dinit: Could not open dependency directory '/usr/lib/dinit.d/user/boot.d' for system service.
[  OK  ] system
[  OK  ] pipewire.user
[  OK  ] pasystray
[  OK  ] picom
[  OK  ] pipewire-pulse.user
[  OK  ] wireplumber.user
[  OK  ] boot
Service 'boot' started.
dinit: Service picom process terminated with exit code 1
[STOPPD] picom
dinit: Service pasystray process terminated with exit code 1
[STOPPD] pasystray
[  OK  ] picom
[  OK  ] pasystray
dinit: Service picom process terminated with exit code 1
[STOPPD] picom
dinit: Service pasystray process terminated with exit code 1
[STOPPD] pasystray
dinit: Service wireplumber.user process terminated with exit code 70
dinit: Service wireplumber.user process terminated with exit code 70
[  OK  ] picom
[  OK  ] pasystray
dinit: Service picom process terminated with exit code 1
[STOPPD] picom
dinit: Service pasystray process terminated with exit code 1
[STOPPD] pasystray
dinit: Service wireplumber.user process terminated with exit code 70
[  OK  ] pasystray
[  OK  ] picom
dinit: Service picom process terminated with exit code 1
dinit: Service picom restarting too quickly; stopping.
[STOPPD] picom
dinit: Service pasystray process terminated with exit code 1
dinit: Service pasystray restarting too quickly; stopping.
[STOPPD] pasystray
dinit: Service wireplumber.user process terminated with exit code 70
dinit: Service wireplumber.user restarting too quickly; stopping.
dinit: Service wireplumber.user restarting too quickly; stopping.
[STOPPD] wireplumber.user
[STOPPD] boot
[STOPPD] system
[STOPPD] pipewire-pulse.user
[STOPPD] pipewire.user

Re: KDE things, try again. We just updated a bunch of its packages and it might take a while until it reaches your mirror.

Do you have turnstiled system service enabled? From your turnstile log that looks like the turnstiled service isn't enabled at all.

Also, dbus, pipewire{,-pulse}, and wireplumber, have dinit user service package in [galaxy], you can use it and enable them instead of making your own (from your logs it looks like you made your own pipewire/wireplumber service). (Also the dbus user service package eliminates the need to use dbus-launch, you should be able to just startx).

I just tried KDE packages still as before.
Did Arch renamed k... to k...5 maybe?

As I said before I enabled the service:

[{+}     ] turnstiled (pid: 579)

I use tinydm that uses autologin (https://git.sr.ht/~kennylevinsen/autologin) under the hood.

I am now using the services from galaxy, do you need to copy them in ~/.config/dinit/? I did that.

Can't use picom and pasystray:

[[+]     ] boot
[{+}     ] system
[{+}     ] pipewire (pid: 594)
[{+}     ] dbus (pid: 584)
[     {X}] picom (exit status: 1)
[     {X}] pasystray (exit status: 1)
[{+}     ] wireplumber (pid: 596)
[{+}     ] pipewire-pulse (pid: 595)

Still no picomn log I think it is as before, related to the display as pasystray, latter's log is as before:

option parsing failed: Cannot open display: 

And I can't use epiphany not sure if it is related to dbus:

(epiphany:3469): libenchant-WARNING **: 21:49:58.636: Error loading plugin: libvoikko.so.1: cannot open shared object file: No such file or directory

src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)

Failed to create GBM buffer of size 1952x888: Invalid argument
src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)

Failed to create GBM buffer of size 1952x888: Invalid argument
src/nv_gbm.c:99: GBM-DRV error (nv_gbm_bo_create): DRM_IOCTL_NVIDIA_GEM_ALLOC_NVKMS_MEMORY failed (ret=-1)

Failed to create GBM buffer of size 1952x888: Invalid argument
Failed to create EGL images for DMABufs with file descriptors -1, -1 and -1

is you picom and pasystray service files even have logging enabled? and is the binary itself run with verbose/debug options?

type = process
command = picom
logfile = $HOME/.local/share/dinit/picom.log
restart = true

type = process
command = pasystray --notify=all
logfile = $HOME/.local/share/dinit/pasystray.log
restart = true

I can launch them manually fine.
They used to work before.
picom log:

[ 10/05/23 20:41:34.074 main FATAL ERROR ] Can't open display.

I checked epiphany again I can't use it also when starting dbus differently.
Some time ago I was using since a problem with librewolf but recently I never used it.

Very nice to have user dinit instance spawned automatically and dbus service I don't need anymore the wrapper to start bspwm.