From: TinfoilSubmarine <TinfoilSubmarine@users.noreply.github.com>
To: ml@inbox.vuxu.org
Subject: [ISSUE] All PHP versions with imagick enabled (`extension=imagick`) segfault
Date: Fri, 02 Feb 2024 22:50:37 +0100 [thread overview]
Message-ID: <gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48500@inbox.vuxu.org> (raw)
[-- Attachment #1: Type: text/plain, Size: 1399 bytes --]
New issue by TinfoilSubmarine on void-packages repository
https://github.com/void-linux/void-packages/issues/48500
Description:
### Is this a new report?
Yes
### System Info
Void 6.6.11_1 x86_64 AuthenticAMD uptodate rrmFFFFFFFFFFFFFFFFFFF
### Package(s) Affected
php8.1-imagick-3.7.0_9, php8.2-imagick-3.7.0_9, php8.3-imagick-3.7.0_2
### Does a report exist for this bug with the project's home (upstream) and/or another distro?
https://github.com/Imagick/imagick/issues/609
https://github.com/Imagick/imagick/issues/636
### Expected behaviour
Using the PHP executable should suceed.
### Actual behaviour
Segfaults immediately no matter what:
```
$ php -a
zsh: segmentation fault php -a
$ php
zsh: segmentation fault php
$ php --version
zsh: segmentation fault php --version
```
### Steps to reproduce
1. Install any php version available in void-packages as well as the relevant imagick (e.g. `xi php8.3-imagick`).
2. Enable imagick in php.ini: `extension=imagick`.
3. Run the `php` executable with any arguments.
next reply other threads:[~2024-02-02 21:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-02 21:50 TinfoilSubmarine [this message]
2024-02-02 21:52 ` TinfoilSubmarine
2024-02-02 21:53 ` TinfoilSubmarine
2024-02-02 22:07 ` classabbyamp
2024-02-02 22:15 ` TinfoilSubmarine
2024-02-03 2:20 ` sgn
2024-02-03 4:48 ` oreo639
2024-02-03 4:49 ` oreo639
2024-02-03 4:50 ` oreo639
2024-02-03 4:52 ` oreo639
2024-02-03 4:54 ` oreo639
2024-02-03 4:54 ` oreo639
2024-02-03 4:55 ` oreo639
2024-02-03 4:57 ` oreo639
2024-02-03 5:06 ` oreo639
2024-02-03 8:29 ` oreo639
2024-02-04 19:34 ` TinfoilSubmarine
2024-02-04 19:34 ` [ISSUE] [CLOSED] " TinfoilSubmarine
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=gh-mailinglist-notifications-41a7ca26-5023-4802-975b-f1789d68868e-void-packages-48500@inbox.vuxu.org \
--to=tinfoilsubmarine@users.noreply.github.com \
--cc=ml@inbox.vuxu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).