Mute black color in stalled dl/up icons #6343

New issue

Closed

opened 2026-02-21 18:21:42 -05:00 by deekerman · 2 comments

deekerman commented

2026-02-21 18:21:42 -05:00

Owner

Originally created by @whyleee on GitHub (Nov 21, 2017).

New skin/stalledDL.png and skin/stalledUP.png icons use #000000 color that is too contrast to other qBittorent icons. This is especially true for torrents which are stalled, so not active and should not bring much attention in the list.

Please consider muting the black color of these icons to some soft black or dark gray, eg #232b2b or lighter like #414141.

Originally created by @whyleee on GitHub (Nov 21, 2017). New `skin/stalledDL.png` and `skin/stalledUP.png` icons use `#000000` color that is too contrast to other qBittorent icons. This is especially true for torrents which are stalled, so not active and should not bring much attention in the list. Please consider muting the black color of these icons to some soft black or dark gray, eg `#232b2b` or lighter like `#414141`.

deekerman

2026-02-21 18:21:42 -05:00

closed this issue
added the
GUI

autoCloseOldIssue

Look and feel
labels

deekerman commented

2026-02-21 18:21:45 -05:00

Author

Owner

@Cqoicebordel commented on GitHub (Nov 22, 2017):

That would be nice, but you have to keep in mind that some people are using a dark theme. And those arrows lack a lot of contrast. Reducing it would be even more dangerous (not just the arrows, mind you, but it's a good spot to start) (see #7773)

@Cqoicebordel commented on GitHub (Nov 22, 2017): That would be nice, but you have to keep in mind that some people are using a dark theme. And those arrows lack a lot of contrast. Reducing it would be even more dangerous (not just the arrows, mind you, but it's a good spot to start) (see #7773) ![low-contrast](https://user-images.githubusercontent.com/2286246/33136399-63a8325e-cfa5-11e7-96f0-c593e932252b.png)

deekerman commented

2026-02-21 18:21:47 -05:00

Author

Owner

@sledgehammer999 commented on GitHub (Oct 29, 2020):

This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable.
If you experience the reported problem or similar in the latest version, please open a new issue report with the requested information in the issue template.

A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression.
Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar.
Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression.

Thank you for your contributions.

@sledgehammer999 commented on GitHub (Oct 29, 2020): This issue has been closed and locked for being too old, and thus either most likely resolved in recent versions or no longer applicable. If you experience the reported problem or similar in the **latest** version, please open a new issue report with the requested information in the issue template. A new issue report with relevant updated data gathered from the latest version is preferable to necroing an old report with a comment like "still happens in version x.y.z", even if you think the bug is the same, or suspect of a regression. Due to the changes made to the qBittorrent code and its dependencies over time, the exact cause of your problem could be totally different than the original one, despite the visible symptoms of the bug being similar. Thus, providing relevant updated information is crucial to find and fix the root cause of a recurrent problem or regression. Thank you for your contributions.