PHP 8.1.2-1ubuntu2.13 in 22.04 LTS: broken class autoloading due to opcache bug
Bug #2032615 reported by
tgoeg
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
php8.1 (Ubuntu) |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Class autoloading in PHP <8.1.6 is broken due to an opcache bug.
This is known to affect multiple products (https:/
Please provide a usable PHP8.1 version >= 8.1.6, this affects a lot of users and products.
Thanks!
To post a comment you must log in.
Hi tgoeg,
Thanks for taking the time to report this bug and help us improve Ubuntu.
However, note that this is either a regression or a duplicate of LP: #1983205.
We fixed this issue in Ubuntu 22.04 in php 8.1.2-1ubuntu2.5. Therefore, the version mentioned in the bug title should be fixed.
Moreover, as discussed with the Drupal community in the LP bug linked above, we also addressed LP: #1989196 in php 8.1.2-1ubuntu2.6, still in Ubuntu 22.04, to append the debian_revision part of the php package version to the PHP_VERSION predefined constant.
This means that checking the PHP_VERSION within PHP should now give you enough information to understand if a specific bug has been addressed in your PHP.
I am also seeing some discussions going on in
- https:/ /www.drupal. org/project/ drupal/ issues/ 3258987 /www.drupal. org/project/ drupal/ issues/ 3307248 /www.drupal. org/forum/ support/ post-installati on/2023- 01-04/ubuntu- 2204-how- to-upgrade- php-to- 816-or- later
- https:/
- https:/
With recent discussion related to this bug.
In special, see https:/ /www.drupal. org/project/ drupal/ issues/ 3307248# comment- 15182072.
While this is supposed to be fixed (note that there are upstream tests running during build time to verify this), there is at least one user reporting a regression in the Drupal forums. I wonder if this is a user error (wrong version/ configuration/ etc) or an actual regression.
To verify this, we would need a reproducer. Would you be able to provide one?
I am marking this bug incomplete for now, until a reproducer is provided. Once you can provide one, please, set this bug status back to new. Without a reproducer, this should be considered a duplicate of the bug linked above.