Control: clone 848842 -2
Control: retitle 848842 tracker-extract: crashes with SIGSYS in mlock
Control: retitle -2 tracker-extract: dumps core repeatedly if seccomp raises
SIGSYS
On Mon, 19 Dec 2016 at 22:39:29 -0800, Ben Longbons wrote:
> Remember, SIGSYS is catchable, and the siginfo_t
On Tue, Dec 20, 2016 at 12:55 AM, Michael Biebl wrote:
> It's most certainly related to the new seccomp based sandbox.
Michael, the three latest commits on tracker master from December 17
(not commited to the 1.10 branch) look significant too. On Ubuntu,
there were reports of
Package: tracker-extract
Version: 1.10.3-1
Followup-For: Bug #848842
Dear Maintainer,
> severity 848842 important
If this isn't 'critical', I have no idea what is. Should I have waited
until the rest of the OS was swapped out so that I *couldn't* kill it?
Just because it's `Priority: optional`
Am 20.12.2016 um 06:42 schrieb Ben Longbons:
> Package: tracker-extract
> Version: 1.10.3-1
> Severity: critical
> File: /usr/lib/tracker/tracker-extract
> Justification: breaks the whole system
>
> Dear Maintainer,
>
> During a recent apt run, my system became almost completely
> unresponsive.
Package: tracker-extract
Version: 1.10.3-1
Severity: critical
File: /usr/lib/tracker/tracker-extract
Justification: breaks the whole system
Dear Maintainer,
During a recent apt run, my system became almost completely
unresponsive.
Luckily I was able to get to another terminal, find the offender
5 matches
Mail list logo