Op 15-05-2021 om 16:06 schreef Marcus Meissner:
On Fri, May 14, 2021 at 07:35:09PM +0200, Jogchum Reitsma wrote:
Op 14-05-2021 om 18:43 schreef Simon Becherer:
Hi
My ghostscript is 9.53.3-4.1, my libpcre2-8.so.0 is 10.36-2.1.
Both have supplier Factory, not Tumbleweed, but I guess that makes no difference? Version numbers are the same.
Am 14.05.21 um 18:22 schrieb Jogchum Reitsma: that will lead into problems, do not use factory if you are a user (or if you know exactly what you do). first i suggest remove factory or disable it in yast. second, swicth EVERY package from factory back to tumbleweed. then try again.
simoN
I wasn't even aware I still had that repo active... But disabled it now. after that, the both packages automagically have now TW as supplier.
Forced re-install once again, problem stays the same... is there an apparmor profile active on ghostscript perhaps?
Ciao, Marcus
Hmm, up till an hour ago my only knowledge of apparmor was how it is pronounced, so I did some googling. There is a file /etc/apparmor.d/ghostscript on my system. aa-status mentions ghostscript is in enforce mode. And /var/log/audit/audit.log contains the message type=AVC msg=audit(1621101856.180:23935): apparmor="DENIED" operation="file_mmap" profile="ghostscript" name="/usr/local/lib64/libpcre2-8.so.0.8.0" pid=28013 comm="gs" requested_mask="m" denied_mask="m" fsuid=0 ouid=0 so indeed here's the cause of the problem I suppose. Thanks a lot, would/could never have guessed it... No idea why the denail to read libpcre2-8.so.0 is imposed on ghostscript; the profile is dated 18th of April 2021, so I suppose that's the time the restrictions where enabled. Now I have to learn how to delete this restriction. Deleting /etc/apparmor.d/ghostscript is a way I would think, but is that a wise decision? After all, there will be a reason why the restrictions are imposed upon ghostscript.