Bug 2300183
| Summary: | 127.0.6533.72 koji build crashes occasionally and consistently when usernamespaces are disabled | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | secureblue <secureblueadmin> |
| Component: | chromium | Assignee: | Than Ngo <than> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | urgent | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 40 | CC: | dwalsh, lvrabec, mmalik, omosnacek, pkoncity, spotrh, suraj.ghimire7, than, vmojzis, yaneti, zpytela |
| Target Milestone: | --- | Keywords: | Regression |
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | chromium-127.0.6533.88-2.fc40 chromium-127.0.6533.88-2.fc39 | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2024-08-03 01:50:13 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
secureblue
2024-07-27 06:42:52 UTC
There's no change in chromium-127 from fedora side which could cause this regression. This issue is gone if you set domain_can_mmap_files auf true. setsebool -P domain_can_mmap_files 1 It looks like a selinux issue! @than While your fix does work, it doesn't explain the issue. 1. I was able to reproduce this on F39, which has a different selinux-policy version than F40. So unless something simultaneously changed between both, selinux-policy isn't the underlying cause. 2. I am unable to reproduce with the official Google Chrome v127 rpm. So, the issue is something that Fedora is doing, likely in conjunction with an upstream change. This issue should be moved back to chromium. move back to chromium for further investigations FEDORA-2024-ff743391c3 (chromium-127.0.6533.88-2.fc39) has been submitted as an update to Fedora 39. https://bodhi.fedoraproject.org/updates/FEDORA-2024-ff743391c3 FEDORA-2024-3a1a0a664e (chromium-127.0.6533.88-2.fc40) has been submitted as an update to Fedora 40. https://bodhi.fedoraproject.org/updates/FEDORA-2024-3a1a0a664e FEDORA-2024-ff743391c3 has been pushed to the Fedora 39 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-ff743391c3` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-ff743391c3 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-3a1a0a664e has been pushed to the Fedora 40 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2024-3a1a0a664e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2024-3a1a0a664e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. FEDORA-2024-3a1a0a664e (chromium-127.0.6533.88-2.fc40) has been pushed to the Fedora 40 stable repository. If problem still persists, please make note of it in this bug report. FEDORA-2024-ff743391c3 (chromium-127.0.6533.88-2.fc39) has been pushed to the Fedora 39 stable repository. If problem still persists, please make note of it in this bug report. |