"Failed at step NAMESPACE" errors

[Michael Stapelberg]

Hi Wouter,

Wouter Van Hemel <wouter-debian at publica.duodecim.org> writes:
> Here are traces of rtkit-daemon and colord.
I think the relevant part is:

2355  mount(NULL, "/", NULL, MS_REC|MS_SLAVE, NULL) = 0
2355  mount("/tmp/systemd-colord.service-X9oeC69/tmp", "/tmp", NULL, MS_BIND|MS_REC, NULL) = 0
2355  mount("/var/tmp/systemd-colord.service-XOPqaZF/tmp", "/var/tmp", NULL, MS_BIND|MS_REC, NULL) = -1 ENOENT (No such file or directory)
2355  socket(PF_LOCAL, SOCK_DGRAM|SOCK_CLOEXEC, 0) = 3
2355  getsockopt(3, SOL_SOCKET, SO_SNDBUF, [212992], [4]) = 0
2355  setsockopt(3, SOL_SOCKET, 0x20 /* SO_??? */, [8388608], 4) = 0
2355  setsockopt(3, SOL_SOCKET, SO_SNDTIMEO, "\n\0\0\0\0\0\0\0\0\0\0\0\0\0\0\0", 16) = 0
2355  connect(3, {sa_family=AF_LOCAL, sun_path="/run/systemd/journal/socket"}, 29) = 0
2355  sendmsg(3, {msg_name(0)=NULL, msg_iov(9)=[{"PRIORITY=3\nSYSLOG_FACILITY=3\nCODE_FILE=../src/core/execute.c\nCODE_LINE=1536\nCODE_FUNCTION=exec_spawn\nSYSLOG_IDENTIFIER=systemd\n", 127}, {"MESSAGE_ID=641257651c1b4ec9a8624d7a40a9e1e7", 43}, {"\n", 1}, {"EXECUTABLE=/usr/lib/colord/colord", 33}, {"\n", 1}, {"MESSAGE=Failed at step NAMESPACE spawning /usr/lib/colord/colord: Operation not permitted", 89}, {"\n", 1}, {"ERRNO=1", 7}, {"\n", 1}], msg_controllen=0, msg_flags=0}, MSG_NOSIGNAL) = 303

Not sure why it says “Operation not permitted”, could be that this is a
bug, as the error code is ENOENT in the trace.

In any case, I think that confirms that your strange /tmp configuration
is the cause for this. I suggest opening a bug upstream to see if they
care about supporting your setup.

-- 
Best regards,
Michael