Ok for me to close it as "won't fix". Just use mod-fastcgi instead of mod-perl.
Christian, no need to thank me for reporting this bug, giving all the detailed
reports, and hinting mod-perl as the triggering cause of this segmentation
fault.
Best regards.
Roberto
--
You received this bug
Even when closing this as "won't Fix" as agreed I really want to thank
you @Kjell for your participation and detailed reports. Good bugs are
rare and this is one.
** Changed in: apache2 (Ubuntu)
Status: Incomplete => Won't Fix
--
You received this bug notification because you are a
Bryce,
In my case when I re-set it up in the container I had to do it manually
(method wasn't chosen by the package).
I would assume mod_perl often gets chosen because of https://rt-
wiki.bestpractical.com/wiki/ManualApacheConfig which has examples for
mod_perl but not for the others, as well as
Roberto and Kjell,
Thanks for your continued investigation into this issue. It sounds like
you've found an effective workaround by removing mod_per and using
fastcgi or similar. It is interesting to hear that upstream considers
mod_perl to not be a supportable configuration. For the Ubuntu
Kjell, indeed the configuration you're showing in comment #13 is indeed
a mod_perl config, so if the issue goes away with that removed, it fits
Roberto's findings.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
