|
Bugzilla – Full Text Bug Listing |
| Summary: | Firefox 82 crashes on some pages | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Tumbleweed | Reporter: | Pavel Šimerda <pavlix> |
| Component: | Firefox | Assignee: | Mozilla Bugs <mozilla-bugs> |
| Status: | RESOLVED DUPLICATE | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Normal | ||
| Priority: | P5 - None | CC: | gfx-bugs, pavlix, ptesarik |
| Version: | Current | ||
| Target Milestone: | --- | ||
| Hardware: | Other | ||
| OS: | Other | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
|
Description
Pavel Šimerda
2020-11-29 14:37:02 UTC
It must be somewhat related to GL. $ unset MOZ_ENABLE_WAYLAND $ /usr/lib64/firefox/firefox The above sequence gets rid of the crashes. Not wayland enabled. Not /usr/bin/firefox. I wonder if this is somehow related to bug 1179298. Do you have Chromium installed on your system? (In reply to Petr Tesařík from comment #2) > I wonder if this is somehow related to bug 1179298. Do you have Chromium > installed on your system? I have Chromium installed. That bug report unfortunately doesn't have instructions to check & workaround. Not really. :-( You'll need to update chromium. And make sure the change - Remove erroneous call to ldconfig which causes Firefox crashes (boo#1179298) is in. I believe we can close this as duplicate. Updates are available for openSUSE since end of November 2020. That has been the fix. --- chromium.spec (revision 1502) +++ chromium.spec (revision 1503) @@ -795,12 +795,10 @@ %post %icon_theme_cache_post %desktop_database_post -/sbin/ldconfig %{_libdir}/chromium %postun %icon_theme_cache_postun %desktop_database_postun -/sbin/ldconfig %{_libdir}/chromium %files %license LICENSE *** This bug has been marked as a duplicate of bug 1179298 *** I confirm that I no longer see this issue in updated Tumbleweed.
> Updates are available for openSUSE since end of November 2020.
However, this bug was reported at the end of November using a fully updated and restarted Tumbleweed! How is that possible?
You reported it one day before fixed updates for openSUSE Leap were available. I don't know when it has been fixed for Tumbleweed. |