Re: Schwarzes Fenster von Tor
Am 08.11.19 um 18:47 schrieb Ulf Volmer:
On 08.11.19 19:37, Siegfrid Brandstätter wrote:
Ein Danke auch von mir, aber leider habe ich nicht verstanden was ich
machen soll.
(Dein Quoting ist irgendwie durcheinander)
Ja leider, habe ich auch gemerkt, Thunderbird!
# aa-disable /etc/apparmor.d/torbrowser.Browser.firefox
bash: aa-disable: Kommando nicht gefunden.
Du möchtest die Datei als root mit dem Editor öffnen und dort die Zeile
/dev/shm/org.mozilla.*.* rw,
einfügen. Gefolgt von einem
sudo systemctl restart apparmor.service
Dann hatte ich es doch richtig verstanden, aber nach dem unten kommt das:
$ sudo systemctl restart apparmor.service
[sudo] Passwort für tester1:
Job for apparmor.service failed because the control process exited with
error code.
See "systemctl status apparmor.service" and "journalctl -xe" for details.
$ systemctl status apparmor.service
● apparmor.service - Load AppArmor profiles
Loaded: loaded (/lib/systemd/system/apparmor.service; enabled;
vendor preset: enabled)
Active: failed (Result: exit-code) since Fri 2019-11-08 18:59:54
WET; 45s ago
Docs: man:apparmor(7)
https://gitlab.com/apparmor/apparmor/wikis/home/
Process: 15051 ExecStart=/lib/apparmor/apparmor.systemd reload
(code=exited, status=1/FAILURE)
Main PID: 15051 (code=exited, status=1/FAILURE)
# journalctl -xe
Nov 08 18:59:54 debian audit[15112]: AVC apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/bin/freshclam" pid=15112
comm="apparmor_parser"
Nov 08 18:59:54 debian apparmor.systemd[15051]: Skipping profile in
/etc/apparmor.d/disable: usr.bin.thunderbird
Nov 08 18:59:54 debian audit[15116]: AVC apparmor="STATUS"
operation="profile_replace" info="same as current profile, skipping"
profile="unconfined" name="/usr/bin/man" pid=15116 comm="apparmor_parser"
usw.
-- An ExecStart= process belonging to unit apparmor.service has exited.
--
-- The process' exit code is 'exited' and its exit status is 1.
Nov 08 18:59:54 debian apparmor.systemd[15051]: Error: At least one
profile failed to load
Nov 08 18:59:54 debian systemd[1]: apparmor.service: Failed with result
'exit-code'.
-- Subject: Unit failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- The unit apparmor.service has entered the 'failed' state with result
'exit-code'.
Nov 08 18:59:54 debian systemd[1]: Failed to start Load AppArmor profiles.
-- Subject: A start job for unit apparmor.service has failed
-- Defined-By: systemd
-- Support: https://www.debian.org/support
--
-- A start job for unit apparmor.service has finished with a failure.
--
-- The job identifier is 5060 and the job result is failed.
Nov 08 18:59:54 debian sudo[15045]: pam_unix(sudo:session): session
closed for user root
Nov 08 19:02:57 debian su[15214]: pam_unix(su:auth): authentication
failure; logname=tester1 uid=1000 euid=0 tty=pts/3 ruser=tester1 rhost=
user=root
Nov 08 19:02:59 debian su[15214]: FAILED SU (to root) tester1 on pts/3
Nov 08 19:03:09 debian su[15222]: (to root) tester1 on pts/3
Nov 08 19:03:09 debian su[15222]: pam_unix(su:session): session opened
for user root by tester1(uid=1000)
lines 1039-1084/1084 (END)
--
Beste Grüße
Sigi
Reply to: