Bug#952896: more information
severity 952896 normal
reassign 952896 libqt5webenginecore5
thanks
It turns out that this only occurs if the QtWebEngineProc does not have
setrlimit access. As this is an unusual configuration that will affect few
people the severity is lower. Also it looks like it might be a bug in
libqt5webenginecore5.
type=PROCTITLE msg=audit(08/03/20 15:10:07.361:266829) : proctitle=/usr/lib/
x86_64-linux-gnu/qt5/libexec/QtWebEngineProcess --type=renderer --disable-in-
process-stack-traces --disable-gpu-memory-
type=SYSCALL msg=audit(08/03/20 15:10:07.361:266829) : arch=x86_64
syscall=prlimit64 success=no exit=EACCES(Permission denied) a0=0x0 a1=0x2
a2=0x7ffcab89c560 a3=0x0 items=0 ppid=446392 pid=446578 auid=rjc uid=rjc
gid=rjc euid=rjc suid=rjc fsuid=rjc egid=rjc sgid=rjc fsgid=rjc tty=pts12
ses=16 comm=QtWebEngineProc exe=/usr/lib/x86_64-linux-gnu/qt5/libexec/
QtWebEngineProcess subj=rjc:staff_r:staff_t:s0-s0:c0.c1023 key=(null)
type=AVC msg=audit(08/03/20 15:10:07.361:266829) : avc: denied { setrlimit }
for pid=446578 comm=QtWebEngineProc scontext=rjc:staff_r:staff_t:s0-
s0:c0.c1023 tcontext=rjc:staff_r:staff_t:s0-s0:c0.c1023 tclass=process
permissive=0
Above is the decoded audit log entry, the prlimit64() system call failing is
the cause of this.
The expected behaviour is that inability to set rlimits will not cause an
infinite loop of screen flashing.
Is it just a failure of this call that causes such a loop or will other
failures of QtWebEngineProc cause an infinite loop?
Is kmail repeatedly calling QtWebEngineProc when it fails? If so that would
be a kmail bug.
--
My Main Blog http://etbe.coker.com.au/
My Documents Blog http://doc.coker.com.au/
Reply to: