Skip to content

Userscripts engine is not working on stable version on Rolling Release systems (Garuda Linux) #1791

@gleyconJ

Description

@gleyconJ

Hello, Otter Browser team.

I am opening this issue to report that the native userscripts feature appears to be non-functional on the stable version of the browser when running on a modern rolling-release operating system.

Problem Description

User scripts can be added normally through the Tools > Addons panel, and they persist in the list after restarting the browser. However, they produce absolutely no effect on webpages. The functionality seems to be completely disabled in practice, although the management interface works.

System Environment

  • Operating System: Garuda Linux (Arch-based, rolling release, fully updated as of September 2025)
  • Desktop Environment: KDE Plasma 6
  • Otter Version: 1.0.03 (the latest stable version available in the official repositories)

Troubleshooting Steps Taken

Before opening this issue, I performed a series of tests to isolate the cause of the problem:

  1. Tested with Multiple Scripts: I tried several scripts from different sources (Greasy Fork and custom-written scripts), including:
    • Global dark mode scripts (using both filter: invert and GM_addStyle).
    • Site-specific scripts (e.g., a dark theme for Wikipedia).
    • A minimal, custom-written test script that only changed the background and text color, to ensure there were no errors in the code.
  2. Technically Corrected Scripts: Scripts that used less robust CSS injection methods (createElement('style')) were rewritten to use GM_addStyle, but they still failed to work.
  3. File Management: I confirmed that the .user.js files are saved correctly in the ~/.config/otter/profiles/default/userscripts/ directory.

None of the tested scripts had any visual or functional effect.

Hypothesis

My suspicion is that an incompatibility exists between the stable version of Otter (from 2022) and the newer libraries of a rolling-release system like Garuda (Qt versions, etc., from 2025). It is likely that this incompatibility has silently broken the userscripts execution engine.

Could you please confirm if this is expected behavior or if there are any other debugging steps I could try?

Thank you for your excellent work on this browser!

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