What plans/timeline, if any, does Manjaro have regarding systemd-homed?

Systemd (245) features homed and is currently in unstable I think. Will Manjaro be implementing the systemd-homed way of organising home folders or will this be left to individuals? Will it even be possible to use homed if Manjaro doesn't do it by default?

1 Like

i make a test this morning, we can use homed with manjaro :slightly_smiling_face:
EDIT: exists now wiki page

Manjaro use it by default? No or in a few years


In that case, how should I understand the following:

systemd-homed.service - Home Manager
     Loaded: loaded (/usr/lib/systemd/system/systemd-homed.service; static; vendor preset: disabled)
     Active: active (running) since Sun 2020-03-08 09:36:54 CET; 15min ago
       Docs: man:systemd-homed.service(8)
   Main PID: 632 (systemd-homed)
     Status: "Processing requests..."
      Tasks: 1 (limit: 9102)
     Memory: 2.1M
     CGroup: /system.slice/systemd-homed.service
             └─632 /usr/lib/systemd/systemd-homed

yes, this service is by default active (by systemd)

but we have nothing in pam, nothing with calamares et nothing in manjaro-settings.
And manjaro never used luks by default (only ready), so why would he change his policy now?

And it's complicated since these users are not included in etc/group or etc/passwd - so for many(all today) programs they are not linux users.

1 Like

Thanks for the explanation!
I admitt that I have to read up on systemd's ins amd outs. But for now, can I assume it to be safe to disable this service?

not found ! systemctl enable and disable not work, is not a unit systemd service :scream:

Worked on my end:

sudo systemctl disable --now systemd-homed.service

systemctl status systemd-homed.service
● systemd-homed.service - Home Manager
     Loaded: loaded (/usr/lib/systemd/system/systemd-homed.service; static; vendor preset: disabled)
     Active: inactive (dead) since Sun 2020-03-08 10:13:44 CET; 8s ago
       Docs: man:systemd-homed.service(8)
    Process: 632 ExecStart=/usr/lib/systemd/systemd-homed (code=exited, status=0/SUCCESS)
   Main PID: 632 (code=exited, status=0/SUCCESS)
     Status: "Shutting down..."
sudo systemctl mask systemd-homed.service
Created symlink /etc/systemd/system/systemd-homed.service → /dev/null.


1 Like

In case you are on the stable branch your systemd version should be 2.42.

test in virtualbox with xfce unstable :wink:

k, that's odd then. : )

Loaded: loaded (/usr/lib/systemd/system/systemd-homed.service; static; vendor preset: disabled)

Must have been a typo, that unit definatly exists?

1 Like

Did you use gnome edition? I'm on cinnamon which uses Lightdm display manager. Everything works fine except for autologin doesn't work. I suspect it's just a problem with Lightdm. Any thoughts?

from journal:

Mar 18 16:08:13 lightdm[536]: pam_succeed_if(lightdm-autologin:auth): requirement "user ingroup autologin" was met by user "greg"
Mar 18 16:08:13 lightdm[536]: gkr-pam: no password is available for user
Mar 18 16:08:13 systemd-homed[465]: greg: changing state inactive → activating-for-acquire
Mar 18 16:08:13 systemd-homework[538]: None of the supplied plaintext passwords unlocks the user record's hashed passwords.
Mar 18 16:08:13 systemd-homed[465]: Activation failed: Required key not available
Mar 18 16:08:13 systemd-homed[465]: greg: changing state activating-for-acquire → inactive
Mar 18 16:08:13 systemd-homed[465]: Got notification that all sessions of user greg ended, deactivating automatically.
Mar 18 16:08:13 systemd-homed[465]: Home greg already deactivated, no automatic deactivation needed.
Mar 18 16:08:14 lightdm[536]: Stopping PAM conversation, interaction requested but not supported
Mar 18 16:08:14 lightdm[536]: pam_systemd_home(lightdm-autologin:account): conversation failed
Mar 18 16:08:14 lightdm[536]: pam_systemd_home(lightdm-autologin:account): Failed to prompt for password/prompt.
Mar 18 16:08:14 lightdm[536]: Error reading existing Xauthority: Failed to open file “/home/greg/.Xauthority”: Permission denied
Mar 18 16:08:14 lightdm[536]: Error writing X authority: Failed to open X authority /home/greg/.Xauthority: Permission denied

I used directory storage not LUKS:

 sudo homectl inspect greg
   User name: greg
       State: inactive
 Disposition: regular
 Last Change: Wed 2020-03-18 14:33:13 GMT
 Last Passw.: Wed 2020-03-18 10:14:39 GMT
    Login OK: yes
 Password OK: yes
         UID: 60132
         GID: 60132 (greg)
 Aux. Groups: wheel
   Directory: /home/greg
     Storage: directory (no encryption)
  Image Path: /home/greg.homedir
   Removable: no
       Shell: /bin/bash
 Mount Flags: nosuid nodev exec
   Disk Size: 151.4G
   Disk Free: 81.0G
  Disk Floor: 5.0M
Disk Ceiling: 5.0T
  Good Auth.: 2
   Last Good: Wed 2020-03-18 14:33:17 GMT
   Bad Auth.: 9
    Last Bad: Wed 2020-03-18 16:08:14 GMT
    Next Try: anytime
 Auth. Limit: 30 attempts per 1min
   Passwords: 1
  Local Sig.: yes
Autom. Login: yes
     Service: io.systemd.Home

Forum kindly sponsored by