Yes, cockpit fails to start: cockpit-wsinstance-https-factory.socket: Job cockpit-wsinstance-https-factory.socket/start failed with result 'dependency'. cockpit.service: Job cockpit.service/start failed with result 'dependency'. cockpit-wsinstance-https-factory.socket: Control process exited, code=exited, status=217/USER cockpit-wsinstance-https-factory.socket: Failed to resolve user cockpit-ws: No such process cockpit-wsinstance-http.socket: Failed with result 'exit-code'. Failed to listen on Socket for Cockpit Web Service http instance. Dependency failed for Cockpit Web Service. Dependency failed for Socket for Cockpit Web Service https instance factory.
This is on Ubuntu 22.04. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2073776 Title: cockpit-ws 321-1~bpo22.04.1 changes user to cockpit-wsinstance but systemd units still use cockpit-ws as the username To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/cockpit/+bug/2073776/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
