qBittorrent
qBittorrent copied to clipboard
qt6 builds can cause graphical artifacts on certain monitors (QTBUG-109850)
qBittorrent & operating system versions
qBittorrent: 4.5.0 x64 OS: Windows 11 22H2 (10.0.22621) x64 Qt: 6.4.0 libtorrent-rasterbar: 1.2.18.0
What is the problem?
I already reported conclusions about this issue for 7-Zip in this post (Russian and English versions): https://sourceforge.net/p/sevenzip/bugs/2199/#f869
So part of text written below is just copy-paste from that post, instead of screenshots and some edits
Unfortunately, I could not find on the Internet why this happens, but I did my own "investigation"
A month ago, I bought a monitor with a screen resolution of 2560x1440 and a refresh rate of 165 Hz I will not stretch this story, I drew test pictures, and after tests on different monitors, operating systems, video cards..., I came to the conclusion that the pattern that the selection has in the qBittorrent somehow leads to the appearance of artifacts on the monitor (they cannot be seen in the screenshots, but they can be seen in a photo or video, especially in macro-mode) My theory is that interfaces (HDMI, DisplayPort) have a compression problem - it is difficult for them to process this pattern, and therefore they transmit it with errors The higher the refresh rate, and the more pixels of the pattern on the screen - the more clearly these artifacts are visible
The problem only when using builds with qt6 All ok with qt5 - it uses a pattern that does not cause artifacts
The simplest solution - is to get away from using "dotted" patterns when selecting and use solid lines instead
Photos of the problem, as well as test files with patterns* are attached: https://imgur.com/a/ZG1bMgr (qBittorrent issue) https://imgur.com/a/h7nhYzz (7-zip issue with test files)
- Files with patterns should be opened at 1:1 scale (100% size), the size of the image viewer window can be any
Steps to reproduce
-
Open qt5 build
-
Select item in torrents list and click on empty space
-
No visible artifacts
-
Open qt6 build
-
Select item in torrents list and click on empty space
-
Visible artifacts
Additional context
No response
Log(s) & preferences file(s)
No response
@DmitriyFrogo Although I can confirm what you've shown, it would be best to report this to Qt themselves & feedback the report here for reference please, as you've shown it happens in other apps too so this appears to not be specifically an issue with qBittorrent itself.
@xavier2k6 Hope I did everything right :D https://bugreports.qt.io/browse/QTBUG-109850
Still reprodicible @DmitriyFrogo on 4.6.0 ?
Still reprodicible @DmitriyFrogo on 4.6.0 ?
Yes. No one is interested in this problem :D
The simplest solution - is to get away from using "dotted" patterns when selecting and use solid lines instead
https://sourceforge.net/p/sevenzip/bugs/2199/#f869
@DmitriyFrogo It looks like a hardware issue. You could consider filing a complaint with your monitor manufacturer.
@DmitriyFrogo It looks like a hardware issue. You could consider filing a complaint with your monitor manufacturer.
All the monitors I've tested have this problem More likely a problem with compression technology used in monitors More hertz and screen resolution = more noticeable If you have default 60 Hz display, it's hard to notice this glitches
I can live with this problem It's a problem for the future, where more people prefer high refresh rate displays with 2K+ screen resolution over 1080@60
This is a weird issue. Upstream Qt ticket isn't getting any love. Should we label this 'Qt bugs' ?
Upstream Qt are asking for a minimal example to reproduce this issue.
Upstream Qt are asking for a minimal example to reproduce this issue.
I wrote out an example 👍🏻
@DmitriyFrogo can you bump upstream bug please ? TIA
@DmitriyFrogo can you bump upstream bug please ? TIA
I tried this artifact https://github.com/qbittorrent/qBittorrent/actions/runs/7862950427 Seems like it fixed now, because new design no longer uses "dots" pattern
@luzpaz can you explain more, what I need to do, if I misunderstood you?
Closing - Resolved in newer Qt version, haven't experienced it again.