I am using systemd rather than upstart, but the bug is the same: cron
depends on remote-fs.target, autofs depends on remote-fs.target, so they
start together. The result is that the job is run with the working
directory set to /var/spool/cron.
What cron should be waiting for is home directories be
Done. I found someone else reporting a problem that had the same
underlying cause, which led to an interesting conversation with a
developer. You can read it here:
https://gitlab.freedesktop.org/dbus/dbus/-/issues/343
The tl;dr version is to use dbus 1.14.x in which the code path that
triggers the
Public bug reported:
Ubuntu release: Ubuntu 22.04.2 LTS (but also tested on Ubuntu 20.04.6 LTS)
dbus version: 1.12.20-2ubuntu4.1
This is related to
https://bugs.launchpad.net/ubuntu/+source/sssd/+bug/2023598, in which an
sssd was upgraded before its libraries. This caused dbus-daemon to
crash, wh
Public bug reported:
If a user is over quota, or if the home directory disk is full, they get
logged out straight after logging in, when the home directory is on NFS.
No information is presented to the user that would let them know the
problem.
This is because of an error in the way that lightdm
4 matches
Mail list logo
