starred/qBittorrent

Fork 0

mirror of https://github.com/qbittorrent/qBittorrent.git synced 2026-03-02 22:57:32 -05:00

Show transfers with tracker errors with a different colour in the list #13972

New issue

Open

opened 2026-02-22 00:32:26 -05:00 by deekerman · 4 comments

deekerman commented

2026-02-22 00:32:26 -05:00

Owner

Originally created by @bubbajonez on GitHub (Nov 14, 2022).

Suggestion

It would be immensely useful to have torrents in the transfers list show a different, warning colour when they have tracker errors.

I realize you can check the side bar for tracker errors, but that's not nearly as immediate and intuitive to spot as the above method, especially when one is hiding the side bar by default for screen real estate purposes.

In torrent clients which use this feature, as soon as one opens the transfers window, one will immediately know which torrents aren't connecting to their trackers, which is a must for private tracker users and allows them to appropriately and efficiently deal with such situations, vital when ratio and seeding times might be involved, or simply tracker downtimes. But as it in qBittorrent presently, it's easy for tracker errors to go unnoticed for hours or even days before the user spots them and takes action, which is a big disadvantage.

Thank you for considering.

Use case

No response

Extra info/examples/attachments

No response

Originally created by @bubbajonez on GitHub (Nov 14, 2022). ### Suggestion It would be immensely useful to have torrents in the transfers list show a different, warning colour when they have tracker errors. I realize you can check the side bar for tracker errors, but that's not nearly as immediate and intuitive to spot as the above method, especially when one is hiding the side bar by default for screen real estate purposes. In torrent clients which use this feature, as soon as one opens the transfers window, one will immediately know which torrents aren't connecting to their trackers, which is a must for private tracker users and allows them to appropriately and efficiently deal with such situations, vital when ratio and seeding times might be involved, or simply tracker downtimes. But as it in qBittorrent presently, it's easy for tracker errors to go unnoticed for hours or even days before the user spots them and takes action, which is a big disadvantage. Thank you for considering. ### Use case _No response_ ### Extra info/examples/attachments _No response_

deekerman added the

Feature request

Duplicate

labels

2026-02-22 00:32:26 -05:00

deekerman commented

2026-02-22 00:32:34 -05:00

Author

Owner

@thalieht commented on GitHub (Nov 14, 2022):

Related/duplicate of #9849 #11238 #5228

@thalieht commented on GitHub (Nov 14, 2022): Related/duplicate of #9849 #11238 #5228

deekerman commented

2026-02-22 00:32:34 -05:00

Author

Owner

@stalkerok commented on GitHub (Nov 15, 2022):

In fact, a very necessary feature, allows you to respond as quickly as possible.

@stalkerok commented on GitHub (Nov 15, 2022): In fact, a very necessary feature, allows you to respond as quickly as possible.

deekerman commented

2026-02-22 00:32:34 -05:00

Author

Owner

@isaacolsen94 commented on GitHub (May 26, 2024):

Did this every get implemented?

@isaacolsen94 commented on GitHub (May 26, 2024): Did this every get implemented?

deekerman commented

2026-02-22 00:32:34 -05:00

Author

Owner

@xavier2k6 commented on GitHub (May 24, 2025):

ANNOUNCEMENT!

For anybody coming across this "Feature Request" & would like/love to see a potential implementation in the future!
Here are some options available to you:

Please select/click the 👍 &/or ❤ reactions in the original/opening post of this ticket.
Please feel free (If you have the "skillset") to create a "Pull Request" implementing what's being requested in this ticket.
(new/existing contributors/developers are always welcome)

DO:

Provide constructive feedback.
Display how other projects implemented same/similar etc.

DO NOT:

Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s).
(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)

@xavier2k6 commented on GitHub (May 24, 2025): ## ANNOUNCEMENT! For anybody coming across this **_"Feature Request"_** & would like/love to see a potential implementation in the future! **Here are some options available to you:** 1. Please select/click the 👍 **&/or** ❤ `reactions` in the original/opening post of this ticket. 2. Please feel free _(If you have the "skillset")_ to create a **_"Pull Request"_** implementing what's being requested in this ticket. **_(new/existing contributors/developers are always welcome)_** ____ **DO:** * Provide constructive feedback. * Display how other projects implemented same/similar etc. **DO NOT:** * Add a "Bump", "me too", "2nd/3rd" etc. or "criticizing" comment(s). **(These will be disregarded/hidden as "spam/abuse/off-topic" etc. as they don't provide anything constructive.)**