From mboxrd@z Thu Jan  1 00:00:00 1970
From: Michael Tremer <michael.tremer@ipfire.org>
To: development@lists.ipfire.org
Subject: Re: Core update 132 - Tor does not start after update
Date: Thu, 23 May 2019 13:13:16 +0100
Message-ID: <C22EBA1A-01F2-4804-A619-7FB78B48513D@ipfire.org>
In-Reply-To: <decc8a88c95940a258efde80db4510740adb2d2c.camel@ipfire.org>
MIME-Version: 1.0
Content-Type: multipart/mixed; boundary="===============0048645172796555731=="
List-Id: <development.lists.ipfire.org>

--===============0048645172796555731==
Content-Type: text/plain; charset="utf-8"
Content-Transfer-Encoding: quoted-printable

Did you try installing libseccomp?

> On 23 May 2019, at 13:12, ummeegge <ummeegge(a)ipfire.org> wrote:
>=20
> Hi all,
> wanted to report that after the update to Core 132 testing and a system
> reboot that Tor does not starts anymore. Error is
>=20
> /usr/bin/tor: error while loading shared libraries: libseccomp.so.2: cannot=
 open shared object file: No such file or directory
>=20
> Best,
>=20
> Erik
>=20


--===============0048645172796555731==--