mirror of
https://github.com/qbittorrent/qBittorrent.git
synced 2026-03-02 22:57:32 -05:00
Jackett search plugin should be disabled by default #15581
Labels
No labels
Accessibility
AppImage
Bounty
Build system
CI
Can't reproduce
Code cleanup
Confirmed bug
Confirmed bug
Core
Crash
Data loss
Discussion
Docker
Documentation
Duplicate
Feature
Feature request
Feature request
Feature request
Filters
Flatpak
GUI
Has workaround
I2P
Invalid
Libtorrent
Look and feel
Meta
NSIS
Network
Not an issue
OS: *BSD
OS: Linux
OS: Windows
OS: macOS
PPA
Performance
Project management
Proxy/VPN
Qt bugs
Qt6 compat
RSS
Search engine
Security
Temp folder
Themes
Translations
Triggers
Waiting diagnosis
Waiting info
Waiting upstream
Waiting web implementation
Watched folders
WebAPI
WebUI
autoCloseOldIssue
No milestone
No project
No assignees
1 participant
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
starred/qBittorrent#15581
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Originally created by @drws on GitHub (Mar 16, 2024).
qBittorrent & operating system versions
qBittorrent: 4.6.3 x64
Operating system: Arch Linux x64
Qt: 5.15.12
libtorrent-rasterbar: 1:2.0.9
What is the problem?
When search plugins are installed the Jackett search plugin gets enabled by default along with other ones. The problem is that many users don't have Jackett server and this only leads to error being displayed in the search results until Jackett is manually disabled. The solution is probably simply to not enable Jackett by default. Or possibly even detect its availability and act accordingly - just not blindly enable it by default, which leads to errors with default configuration.
Steps to reproduce
Additional context
No response
Log(s) & preferences file(s)
No response
@luzpaz commented on GitHub (Mar 22, 2024):
Indeed. This is a good point.
If jackett is not running then the user sees something like this:
@Ichicoro commented on GitHub (Nov 3, 2025):
any update on this?