Display scaling bug

[apxapob]

Steps to reproduce

requirements: 2 monitors with different dpi and resolution.

1) Set different scale factors on your monitors.(I have 200% on main and 125% on secondary) 2) Open telegram window on main monitor. 3) Turn off your main monitor 4) Turn it on.

Result:

Expected behaviour

I expect telegram to render correctly.

Actual behaviour

Operating system

Windows 11

Version of Telegram Desktop

5.3.1

Installation source

Static binary from official website

Crash ID

no

Logs

no

[kode54]

Similar but different effect happens on Linux desktops with mixed DPI: When toggling off the HiDPI (scale 2.0) monitor, the TDesktop window becomes scale 1.0, then doesn't pick up the scale 2.0 when relocated onto the 2.0 display, either manually by dragging, or automatically by the output restore features of the compositor when the output is momentarily removed.

[ilya-fedin]

@apxapob is this still happening with 5.6?

[apxapob]

@apxapob is this still happening with 5.6?

yep still happening.

[ilya-fedin]

Does it stop happening if you enable system window frame in settings?

[apxapob]

Does it stop happening if you enable system window frame in settings?

yeah, happening with system window frame enabled too

[ilya-fedin]

Can you reproduce the same issue with qBittorrent?

[apxapob]

Can you reproduce the same issue with qBittorrent?

qBittorrent has similar issue. When I turn off the monitor the window goes to the second monitor and has broken layout. And when I turn on the first monitor layout is fine, but it shows everything like it has 100% scaling, not 200%. The ui becomes too small.

[ilya-fedin]

Oh, so backporting Qt 6 changes is probably useless given that qBittorent which uses Qt 6 is bugged, too...

[ilya-fedin]

Can you check which exactly Qt version qBittorent uses right now (in about dialog)?

[apxapob]

Can you check which exactly Qt version qBittorent uses right now (in about dialog)?

Qt: 6.3.0

[ilya-fedin]

Qt: 6.3.0

Are you sure your qbittorrent is latest? I see Qt 6.7.3 is mentioned on their website...

[Aokromes]

Qt: 6.3.0

Are you sure your qbittorrent is latest? I see Qt 6.7.3 is mentioned on their website...

on latest qbittorrent it's indeed 6.7.3

https://i.imgur.com/7uh8QPu.png

[ilya-fedin]

i wonder whether latest qbittorrent bugs

[apxapob]

Updated qbittorrent. The same situation on Qt 6.7.3

[ilya-fedin]

ok, thanks

[ilya-fedin]

Does this happen with 5.6.1?

[apxapob]

I don't know. Where can I check that?

[ilya-fedin]

I don't know. Where can I check that?

I don't quite understand the question. How did you check previously?

[apxapob]

oh sorry. I thought I need to find an app with Qt 5.6.1 In telegram 5.6.1 the bug still happens.

[ilya-fedin]

What do you do to get out of this state? Does resizing window help? Does moving the window a little bit (the relevant event should be sent on mouse button release) help? Does changing Windows settings (e.g. enabling/disabling dark mode) and then moving the window a little bit help?

[apxapob]

I usually just restart telegram. Also I can fix it by changing screen scale factor. Anything else doesn't help.

[ilya-fedin]

Anything else doesn't help.

None of the things I suggested to try?

[apxapob]

Yeah.

[ilya-fedin]

Hm. I wonder whether the relevant message is sent only with native titlebar. Can you try moving the window with it?

An important thing is to try switch the system dark mode if just moving doesn't work as it sends the event that forces Qt to update its screen list (and then on the end of window move Qt should update window's associated screen).

[apxapob]

Tried that. Didn't help.

[ilya-fedin]

Does this happen with 5.6.2?

[apxapob]

This is funny. Telegram 5.6.2 crashes when I turn the monitor on. Which is better because I don't have to shut it down by myself=)

[ilya-fedin]

Can you provide crash id of the crash report (you have to enable beta installation in settings for crash reporter to appear, DON'T wait for an update)?

[apxapob]

Crash ID: 3c7ec04c-7038-4481-9c8d-1ba3b03086c3

[ilya-fedin]

Can you re-test the bug when you will get 5.6.3?

[apxapob]

yeah sure

[apxapob]

Yay! I checked 5.6.3 - The bug is finally fixed!