Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

Created attachment 1433549 [details]
ff backtrace

Description of problem:
New FF 60ESR segfault at start

Version-Release number of selected component (if applicable):
firefox-60.0-4.el7_5

How reproducible:
100%

Steps to Reproduce:
1. start firefox
2.
3.

Actual results:
segfault at startup

Expected results:


Additional info:
see attached backtrace

OK with -7 build works fine except of bz1574501.

This bug is against unreleased/testing builds, closing as we're not going to use this #BZ for any public purpose.

I checked again and the issue is fixed with -7 build but is it back with -11 which is the last build in brew I can find.

Reopening

I was wrong id did not disappear in -7 it just take long to raise. It is still there.

Hi Martin,

can you provide the DocText for this BZ, please? Thanks a lot.

Jura

Hi Martin,
can you use the following format to provide the Doc Text, please?


http://jenkinscat.gsslab.pnq.redhat.com:8080/job/Errata_Lore%20(html-single)/lastStableBuild/artifact/tmp/en-US/html-single/index.html#known_issue

Thanks a lot,

Jura

Hello Martin,

if this bug has to be documented, could you please set the Doc Type and fill in the Doc Text?

If you need a reference for filling up the Doc Text field, use this:
http://jenkinscat.gsslab.pnq.redhat.com:8080/job/Bugzilla%20Cheatsheet/lastSuccessfulBuild/artifact/BZ_cheatsheet.html#ReleaseNotes

If you have any other questions, please contact me.

Best regards,
Adam Kvítek

Hello Martin,

This is a second reminder considering documentation of this bug.

If this bug has to be documented, could you please set the Doc Type and fill in the Doc Text?

If you need a reference for filling up the Doc Text field, use this:
http://jenkinscat.gsslab.pnq.redhat.com:8080/job/Bugzilla%20Cheatsheet/lastSuccessfulBuild/artifact/BZ_cheatsheet.html#ReleaseNotes

If you have any other questions, please contact me.

Best regards,
Adam Kvítek

*** Bug 1619829 has been marked as a duplicate of this bug. ***

Sorry we don't have a fix for that.