mirrors/apparmor.d
1
0
Fork 0
mirror of https://github.com/roddhjav/apparmor.d.git synced 2024-11-15 07:54:17 +01:00
Code Issues Actions Packages Projects Releases Wiki Activity
11cc454fe2
apparmor.d/docs/issues.md
Alexandre Pujol c0780edee1
docs: multiple english corrections. 
Co-authored-by: Thomas LAURENT <thomas.laurent@ucdconnect.ie>
2023-01-31 21:13:35 +00:00

1.3 KiB
Raw Blame History

title
Known issues

Known issues

!!! info

Known bugs are tracked on the meta issue **[#75](https://github.com/roddhjav/apparmor.d/issues/74)**.

Pacman "could not get current working directory"

$ sudo pacman -Syu
...
error: could not get current working directory
:: Processing package changes...
...

This is a feature, not a bug! It can safely be ignored. Pacman tries to get your current directory. You will only get this error when you run pacman in your home directory.

According the Archlinux guideline, on Archlinux, packages cannot install files under /home/. Therefore the pacman profile purposely does not allow access of your home directory.

This provides a basic protection against some packages (on the AUR) that may have rogue install script.

Gnome can be very slow to start.

Gnome can be slow to start. This is a known bug, help is very welcome.

The complexity is that:

  • It works fine without AppArmor
  • It works fine on most system (including test VM)
  • It seems to be dbus related
  • On archlinux, the dbus mediation is not enabled. So, there is nothing special to allow.