Skip to content

Persistent “Update available” popup after upgrade + Extensions inactive after restart until toggled #476

@vsdfgsrf4r44-png

Description

@vsdfgsrf4r44-png

Summary

I am seeing two recurring issues on Windows with Midori (Firefox ESR based):

  1. A persistent “Update available” popup keeps appearing even after downloading the latest installer from the website and performing an upgrade.
  2. After restarting Midori, my Firefox extensions are not active. They only start working after I manually disable and re-enable each extension once.

Environment

  • OS: Windows 10 (64-bit)
  • Midori version: 11.6 (64-bit)
  • Firefox base shown in About: 128.13.0 ESR
  • Installation type: upgraded via latest installer from website (v2.1.0)

Problem 1: Update popup persists

Steps to reproduce

  1. Install/upgrade Midori using the newest installer from the official website.
  2. Start Midori.
  3. The “Update available” popup appears again.

Expected behavior

No update popup if the latest version is already installed.

Actual behavior

Popup keeps appearing on every start (or repeatedly), even after an upgrade.

Notes

  • In the update settings, it also shows “Failed to check for updates” sometimes.
  • It looks like a stuck update state or update flag that does not clear after upgrading via installer.

Problem 2: Extensions inactive after restart until toggled

Steps to reproduce

  1. Install and enable one or more Firefox extensions.
  2. Restart Midori.
  3. Extensions are not active.
  4. Manually disable and re-enable an extension.
  5. Extension starts working.

Expected behavior

Extensions should be active immediately after restart, without manual toggling.

Actual behavior

Extensions appear enabled in the UI, but functionality is inactive until toggled off/on once.

What I tried

  • Downloaded latest installer from the website and upgraded (issue persists).
  • Restarted the browser multiple times.

Request

Could you please advise:

  • How Midori Desktop updates are expected to work on Windows (installer-only vs in-app), and how to stop the persistent update popup if already up to date.
  • Whether the extension startup issue is a known bug (add-on startup cache, profile corruption, scope settings), and what the recommended fix is.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions