Bug 2415167
| Summary: | SeaMonkey 2.53.22 crashes with SIGILL on exit | ||
|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | A. Galama <agalama> |
| Component: | seamonkey | Assignee: | Dmitry Butskoy <dmitry> |
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
| Severity: | unspecified | Docs Contact: | |
| Priority: | unspecified | ||
| Version: | 43 | CC: | agalama, dmitry, gecko-bugs-nobody, iannbugzilla, jhorak, utilitymail |
| Target Milestone: | --- | ||
| Target Release: | --- | ||
| Hardware: | x86_64 | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | seamonkey-2.53.23-1.fc43 | Doc Type: | --- |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2026-01-09 17:21:17 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
A. Galama
2025-11-15 06:57:00 UTC
Could you please also test how the "generic Linux version" (from my copr build) behaves in the same environment? This will help determine whether the problem is with the code itself or if it is a build environment issue (the "generic" version is built under epel8, and have some libraries bundled). Get it here: https://download.copr.fedorainfracloud.org/results/buc/seamonkey-generic/epel-8-x86_64/09770992-seamonkey/seamonkey-2.53.22-1.el8.x86_64.rpm Well, upstream can reproduce it as well, but cannot resolve right now due to lack of time. In a hope you have enough time -- could you bisect the issue using the official nightly builds from https://archive.seamonkey-project.org/nightly/2025/index.html ? (Sorry if this is too ambitious a request. :) ) Sorry, I have absolutely no clue what to do with a "nightly build". I've found that to reproduce the crash you need to trigger the Anubis bot check which https://bodhi.fedoraproject.org/ uses. For me the easiest way to do that is by creating a new profile each time you test With checking nightlies, the one from 2025-08-18 works, the one from 2025-08-19 crashes. FEDORA-2026-f54e4ee85a (seamonkey-2.53.23-1.fc43) has been submitted as an update to Fedora 43. https://bodhi.fedoraproject.org/updates/FEDORA-2026-f54e4ee85a FEDORA-2026-f54e4ee85a has been pushed to the Fedora 43 testing repository. Soon you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --refresh --advisory=FEDORA-2026-f54e4ee85a` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2026-f54e4ee85a See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates. seamonkey-2.53.23-1.fc43 fixes the problem for me. Thanks! FEDORA-2026-f54e4ee85a (seamonkey-2.53.23-1.fc43) has been pushed to the Fedora 43 stable repository. If problem still persists, please make note of it in this bug report. *** Bug 2428564 has been marked as a duplicate of this bug. *** |