Failed to start User Manager for UID 1000

efog4 · 2026-10-09 20:46:41

I noticed when I boot the single red entry in the sprawl of green entries says:

 [FAILED] Failed to start User Manager for UID 1000.

and when I run 'systemctl status user@1000.service'

 × user@1000.service - User Manager for UID 1000
     Loaded: loaded (/usr/lib/systemd/system/user@.service; static)
    Drop-In: /usr/lib/systemd/system/user@.service.d
             └─10-login-barrier.conf
     Active: failed (Result: exit-code) since <time and date>; 16s ago
 Invocation: c2ea951c220d43f8a7becdd82763280e
       Docs: man:user@.service(5)
    Process: 619 ExecStart=/usr/lib/systemd/systemd --user (code=exited, status=1/FAILURE)
   Main PID: 619 (code=exited, status=1/FAILURE)
      Error: code: 2 (No such file or directory)
   Mem peak: 3.6M
        CPU: 23ms

Oct 09 13:27:21 archlinux systemd[1]: Starting User Manager for UID 1000...
Oct 09 13:27:21 archlinux (systemd)[619]: pam_warn(systemd-user:setcred): function=[pam_sm_setcred] flags=0x8002 serv>
Oct 09 13:27:21 archlinux (systemd)[619]: pam_unix(systemd-user:session): session opened for user era(uid=1000) by er>
Oct 09 13:27:21 archlinux systemd[619]: Failed to allocate manager object: No such file or directory
Oct 09 13:27:21 archlinux systemd[1]: user@1000.service: Main process exited, code=exited, status=1/FAILURE
Oct 09 13:27:21 archlinux systemd[1]: user@1000.service: Failed with result 'exit-code'.
Oct 09 13:27:21 archlinux systemd[1]: Failed to start User Manager for UID 1000.

Whenever I search for this issue people discuss stop jobs which is not related to my issue so I'd appreciate any direction if there is something in the wiki I should read.

This might be unnecessary context but I just exec into the compositor after this is run upon login:

export XDG_RUNTIME_DIR=/run/user/$(id -u)

if [ ! -d "$XDG_RUNTIME_DIR" ]; then
   mkdir -p "$XDG_RUNTIME_DIR"
   chmod 700 "$XDG_RUNTIME_DIR"
fi

if [ ! "$DBUS_SESSION_BUS_ADDRESS" ]; then
   export $(dbus-launch)
fi

I'm unsure if it's related but what pushed me to create a forum post in case something were wrong:
recently I'm trying to use pyrpland folloiwng this on mangowm and I created a service in ~/.config/systemd/user and when I run the service:

 systemctl enable --user --now pyprland.service

 Failed to connect to user scope bus via local transport: No such file or directory

From what I can tell pyprland supports use with other window managers but if this is unrelated I'll sort it out in discussions re: mango.

Overall I am confused on what might be wrong because otherwise things have been working fine so I'm unsure where the hiccup is.

seth · 2026-10-09 21:13:25

after this is run upon login

Why? How?
Basically don't do that.

efog4 · 2026-10-09 21:24:54

seth wrote:

How?

if [ -z "$WAYLAND_DISPLAY" ] && [ "$(tty)" = "/dev/tty1" ];  then
 source ~/.bashrc
  endomph mango
fi

in .bash_profile and in .bashrc is this:

endomph() {

export XDG_RUNTIME_DIR=/run/user/$(id -u)

if [ ! -d "$XDG_RUNTIME_DIR" ]; then
   mkdir -p "$XDG_RUNTIME_DIR"
   chmod 700 "$XDG_RUNTIME_DIR"
fi

if [ ! "$DBUS_SESSION_BUS_ADDRESS" ]; then
   export $(dbus-launch)
fi



pipewire 2>/dev/null &
pipewire-pulse 2>/dev/null &
wireplumber 2>/dev/null &

dunst 2>/dev/null &
if [ -n "$1" ]; then
exec $1 2>/dev/null
fi

}

So I just remove

export XDG_RUNTIME_DIR=/run/user/$(id -u)

if [ ! -d "$XDG_RUNTIME_DIR" ]; then
   mkdir -p "$XDG_RUNTIME_DIR"
   chmod 700 "$XDG_RUNTIME_DIR"
fi

if [ ! "$DBUS_SESSION_BUS_ADDRESS" ]; then
   export $(dbus-launch)
fi

update:
Okay I think that was vestigial from a previous compositor I was using that did not work until I did that I'm not entirely sure why it worked at the time. So removing it seemed to have no effect but rebooting still shows the same issue.

but removing

 export XDG_RUNTIME_DIR=/run/user/$(id -u)

prevents the compositor from starting so that stays for now.

oh and removing the export ${dbus-launch) causes this:

 notify-send hellop

Failed to show notification: Error spawning command line “dbus-launch --autolaunch=4ff1d7e2548846838715a75e0c7cc8da --binary-syntax --close-stderr”: Child process exited with code 1

so thats why that one was in there

Last edited by efog4 (2026-10-09 21:34:21)

seth · 2026-10-09 21:34:03

pipewire is socket activated, don't run any of that either (incl. wireplumber)
dunst is dbus activated an in any event would require a running display server, so you can't run that before running mango (and don't have to run it at all)

If the issue remains please post your complete system journal for the boot:

sudo journalctl -b | nc termbin.com 9999

Should we go over the entire bashrc in case there's other cruft?

seth · 2026-10-09 21:35:29

prevents the compositor from starting so that stays for now.

This basically means your logind integration is (still) broken and manually exporting the variable there is just plastering over the actual problem.

efog4 · 2026-10-09 21:53:07

Thank you for helping me

im sure it may be similar to the other plastering but as an update removing the wireplumber and pulse prevents sound output, pavucontrol, and connection to bluetooth audio devices. I think at one point I had in my compositor auto start script and since it seemed to work for either the .bash_profile or the compositor autostart I opted to just keep it with the other things i was starting to prep the environment for housekeeping.

complete journalctl -b

And regarding the rest of .bashrc I don't think it'd be necessary but I'll share it in the case that someone would find it amusing

endomph() {

export XDG_RUNTIME_DIR=/run/user/$(id -u)

#pipewire 2>/dev/null &
#pipewire-pulse 2>/dev/null &
#wireplumber 2>/dev/null &

#emacs --daemon 2>/dev/null
#dunst 2>/dev/null &
if [ -n "$1" ]; then
exec $1 2>/dev/null
fi

}

netcon() {
sudo -n /usr/bin/netcon.sh
}

mout() {
 man $1 | col -b | less -R | tac
}

seth · 2026-10-09 22:00:29

hostnamectl # do you have a static one

You're running resolved and named, pretty sure that will screw DNS and dbus is hostname sensitive.
=> You need to sort that out.

efog4 · 2026-10-09 22:03:10

Ok I'll figure that out.

thanks !

just realized its been exactly one year since i registered

Last edited by efog4 (2026-10-09 22:09:24)

Arch Linux

#1 2026-10-09 20:46:41

Failed to start User Manager for UID 1000

#2 2026-10-09 21:13:25

Re: Failed to start User Manager for UID 1000

#3 2026-10-09 21:24:54

Re: Failed to start User Manager for UID 1000

#4 2026-10-09 21:34:03

Re: Failed to start User Manager for UID 1000

#5 2026-10-09 21:35:29

Re: Failed to start User Manager for UID 1000

#6 2026-10-09 21:53:07

Re: Failed to start User Manager for UID 1000

#7 2026-10-09 22:00:29

Re: Failed to start User Manager for UID 1000

#8 2026-10-09 22:03:10

Re: Failed to start User Manager for UID 1000

Board footer