From: ummeegge <ummeegge@ipfire.org>
To: development@lists.ipfire.org
Subject: Core update 132 - Tor does not start after update
Date: Thu, 23 May 2019 14:12:14 +0200 [thread overview]
Message-ID: <decc8a88c95940a258efde80db4510740adb2d2c.camel@ipfire.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 282 bytes --]
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
/usr/bin/tor: error while loading shared libraries: libseccomp.so.2: cannot open shared object file: No such file or directory
Best,
Erik
next reply other threads:[~2019-05-23 12:12 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 12:12 ummeegge [this message]
2019-05-23 12:13 ` Michael Tremer
2019-05-23 12:30 ` ummeegge
2019-05-23 12:31 ` Michael Tremer
2019-05-23 12:41 ` ummeegge
2019-05-23 12:56 ` ummeegge
2019-05-23 17:47 ` ummeegge
2019-05-24 5:37 ` ummeegge
2019-05-26 15:05 ` ummeegge
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=decc8a88c95940a258efde80db4510740adb2d2c.camel@ipfire.org \
--to=ummeegge@ipfire.org \
--cc=development@lists.ipfire.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox