Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1749441 - firefox does run with old profile after upgrade to F31 - do the check based on version name instead of build time
Summary: firefox does run with old profile after upgrade to F31 - do the check based o...
Keywords:
Status: CLOSED EOL
Alias: None
Product: Fedora
Classification: Fedora
Component: firefox
Version: 32
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Martin Stransky
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On: 1749107
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-05 15:49 UTC by Martin Stransky
Modified: 2021-05-25 15:05 UTC (History)
16 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1749107
Environment:
Last Closed: 2021-05-25 15:05:12 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

Description Martin Stransky 2019-09-05 15:49:05 UTC
+++ This is follow up of Bug #1749107 +++

Description of problem:

I upgraded my system from F30 to F31 today (no updates-testing).
firefox-wayland refuses to start saying
"You've launched an older version of Firefox" and offers
either "Create New Profile" or "Quit". If a new is created, it
runs OK with this profile.

The upgrade was:
    Upgrade firefox-68.0.2-1.fc31.x86_64     @fedora
    Upgraded    firefox-68.0.2-1.fc30.x86_64 @@System
so the version didn't go down.


Version-Release number of selected component (if applicable):
firefox-68.0.2-1.fc31.x86_64

How reproducible:
I tried a few times, and the error is always the same.

Let's do the check based on version name instead of build time.

Comment 1 Kamil Páral 2019-09-06 08:31:09 UTC
Removing the blocker proposal from this bug, it got inherited when cloning bug 1749107.

Comment 2 Ben Cotton 2020-02-11 17:54:53 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 32 development cycle.
Changing version to 32.

Comment 3 Fedora Program Management 2021-04-29 15:57:27 UTC
This message is a reminder that Fedora 32 is nearing its end of life.
Fedora will stop maintaining and issuing updates for Fedora 32 on 2021-05-25.
It is Fedora's policy to close all bug reports from releases that are no longer
maintained. At that time this bug will be closed as EOL if it remains open with a
Fedora 'version' of '32'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 32 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 4 Ben Cotton 2021-05-25 15:05:12 UTC
Fedora 32 changed to end-of-life (EOL) status on 2021-05-25. Fedora 32 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.


Note You need to log in before you can comment on or make changes to this bug.