gs problem with libpcre2
Hi, Running TW, (latest snapshot of today), gs bails out with gs gs: error while loading shared libraries: libpcre2-8.so.0: failed to map segment from shared object I've had this problem for a while (first mentioned it here as "convert fila to open libpcre2-8.so.0" on April 26), but several snapshots later the problem is still there. I've done a forced update of both gs and libpcre, but same result.. Anyone experiencing this? regards, Jogchum
Hello Jogchum, Am Donnerstag, 13. Mai 2021, 19:35:17 CEST schrieb Jogchum Reitsma:
Running TW, (latest snapshot of today), gs bails out with
gs gs: error while loading shared libraries: libpcre2-8.so.0: failed to map segment from shared object
I've had this problem for a while (first mentioned it here as "convert fila to open libpcre2-8.so.0" on April 26), but several snapshots later the problem is still there.
I've done a forced update of both gs and libpcre, but same result..
Anyone experiencing this?
No, works fine here. Just tried to display a pdf with gs, works. What type of document do you want to display? Cheers Axel
Op 14-05-2021 om 13:58 schreef Axel Braun:
Hello Jogchum,
Am Donnerstag, 13. Mai 2021, 19:35:17 CEST schrieb Jogchum Reitsma:
Running TW, (latest snapshot of today), gs bails out with
gs gs: error while loading shared libraries: libpcre2-8.so.0: failed to map segment from shared object
I've had this problem for a while (first mentioned it here as "convert fila to open libpcre2-8.so.0" on April 26), but several snapshots later the problem is still there.
I've done a forced update of both gs and libpcre, but same result..
Anyone experiencing this? No, works fine here. Just tried to display a pdf with gs, works. What type of document do you want to display?
It's a pdf, also. But even if I don't give it any input (just type 'gs' and <Return> in the terminal), it fails immediately... 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. regards, Jogchum
Cheers Axel
Hi Am 14.05.21 um 18:22 schrieb Jogchum Reitsma:
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.
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
regards, Jogchum
Cheers Axel
-- www.becherer.de
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... regards, Jogchum
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
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.
On Sat, May 15, 2021 at 08:24:29PM +0200, Jogchum Reitsma wrote:
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
Wouldn't it be nice/conventional to have a time-stamp to match the errant activity against? Daniel
* Daniel Morris
On Sat, May 15, 2021 at 08:24:29PM +0200, Jogchum Reitsma wrote:
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
Wouldn't it be nice/conventional to have a time-stamp to match the errant activity against?
but you do have, just not converted to the format you desire. 1621101856.180 https://www.epochconverter.com/ -- (paka)Patrick Shanahan Plainfield, Indiana, USA @ptilopteri http://en.opensuse.org openSUSE Community Member facebook/ptilopteri Photos: http://wahoo.no-ip.org/piwigo paka @ IRCnet freenode
On Mon, May 17, 2021 at 08:32:08AM -0400, Patrick Shanahan wrote:
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
Wouldn't it be nice/conventional to have a time-stamp to match the errant activity against?
but you do have, just not converted to the format you desire. 1621101856.180
Doh! Thank you. Daniel
Daniel Morris wrote:
On Mon, May 17, 2021 at 08:32:08AM -0400, Patrick Shanahan wrote:
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
Wouldn't it be nice/conventional to have a time-stamp to match the errant activity against?
but you do have, just not converted to the format you desire. 1621101856.180
Doh! Thank you.
date -d @1621101856.180
Op 15-05-2021 om 16:06 schreef Marcus Meissner:
<snip> is there an apparmor profile active on ghostscript perhaps?
Ciao, Marcus
So I added the line /usr/local/lib64/libpcre2-8.so* m, to /etc/apparmor.d/ghostscript, and ran apparmor_parser -r /etc/apparmor.d/ghostscript Problem solved! Thanks again a lot! regards, Jogchum
participants (7)
-
Axel Braun -
Daniel Morris -
Jogchum Reitsma -
Marcus Meissner -
Patrick Shanahan -
Peter Suetterlin -
Simon Becherer