Hi Michael, On Wed, 6 Apr 2016 21:39:25 +0200, Michael Biebl <bi...@debian.org> wrote: > Am 06.04.2016 um 20:33 schrieb Stephen Kitt: > > On Wed, 6 Apr 2016 14:25:30 +0200, Michael Biebl <bi...@debian.org> > > wrote: > >> CapabilityBoundingSet= > >> > >> ProtectSystem= > >> > >> ProtectHome= > >> > >> One-by-one. Run systemctl daemon-reload after each modification and try > >> to start the service. > > > > It works if I comment out ProtectSystem... > > Interesting. The .service file hasn't changed between .91 and .92. > Are you sure, .91 works properly? Can you try .93 which was uploaded today?
Reverting to .91 still shows the issue, and upgrading to .93 or .94 doesn't fix it. So I'm guessing this is caused by something else which got upgraded between the installation of .91-3 and the installation of .92-1... That's quite a large haystack on this particular system, but I did notice a systemd/udev upgrade (229-2 to 229-3). I don't blame everything on systemd, but since I suppose system protection uses systemd features, I tried downgrading all the systemd/udev packages to 229-2, but that didn't fix the issue either (although I didn't try rebooting — would that make a difference?). On Wed, 6 Apr 2016 21:42:11 +0200, Michael Biebl <bi...@debian.org> wrote: > I see you use sbuilder. I vaguely remember that we had issues in systemd > with sbuilder in the past. Can you reproduce the issue if sbuilder is > disabled/uninstalled? I uninstalled sbuild and unmounted all the corresponding filesystems, but system protection still doesn't work. So in summary: * this affects .91-3, .92-1, .93-1 and .94-1; * ... so it's probably caused by something else (which is why I haven't updated the "found" info on this bug); * downgrading systemd/udev doesn't fix it; * removing sbuild doesn't fix it. Regards, Stephen
pgpJkELA5j3pC.pgp
Description: OpenPGP digital signature
