Ubuntu Mate 17.10 + user manager error UID1000 ...need help!

Support & Help Requests
1

Hi!

I got some issues after Upgrade my Ubuntu mate 17.04 to 17.10:

● [email protected] - User Manager for UID 1000
Loaded: loaded (/lib/systemd/system/[email protected]; static; vendor preset: enabled)
Drop-In: /lib/systemd/system/[email protected]
└─timeout.conf
Active: failed (Result: protocol) since Sun 2018-01-14 20:37:20 CET; 5min ago
Process: 1772 ExecStart=/lib/systemd/systemd --user (code=exited, status=1/FAILURE)
Main PID: 1772 (code=exited, status=1/FAILURE)

Jan 14 20:37:20 amd systemd[1]: Starting User Manager for UID 1000…
Jan 14 20:37:20 amd systemd[1772]: pam_unix(systemd-user:session): session opened for user nwo by (uid=0)
Jan 14 20:37:20 amd systemd[1772]: Signature not found in user keyring
Jan 14 20:37:20 amd systemd[1]: Failed to start User Manager for UID 1000.
Jan 14 20:37:20 amd systemd[1]: [email protected]: Unit entered failed state.
Jan 14 20:37:20 amd systemd[1]: [email protected]: Failed with result ‘protocol’.

…how to fix it? Please help! Thanks!

2

I found a solution:

it was the .ecryptfs in common-auth / common-password etc. [/etc/pam.d]

I removed it and now the error message for UID1000 is gone but a new error is there:

…when i run systemctl status [email protected]:

Active: active (running) since Sun 2018-01-14 21:48:40 CET; 3min 0s ago
Main PID: 1157 (systemd)
Status: “Startup finished in 31ms.”
Tasks: 2
CGroup: /user.slice/user-1000.slice/[email protected]
└─init.scope
├─1157 /lib/systemd/systemd --user
└─1161 (sd-pam)

Jan 14 21:48:40 amd systemd[1157]: Reached target Paths.
Jan 14 21:48:40 amd systemd[1157]: dbus.socket: Failed to listen on sockets: Address already in use
Jan 14 21:48:40 amd systemd[1157]: Failed to listen on D-Bus User Message Bus Socket.
Jan 14 21:48:40 amd systemd[1157]: dbus.socket: Unit entered failed state.

andy idea?

3

Now I have fix it.

Completely installed DBUS new and fix it with dbus.service and dbus.socket from Mate Live DVD.