Bug 448666 - Animations change speed with refresh rate when using an AMD GPU
Summary: Animations change speed with refresh rate when using an AMD GPU
Status: RESOLVED DUPLICATE of bug 446637
Alias: None
Product: plasmashell
Classification: Plasma
Component: general (show other bugs)
Version: 5.23.5
Platform: Neon Linux
: NOR normal
Target Milestone: 1.0
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-01-17 18:04 UTC by Riccardo Robecchi
Modified: 2022-05-24 17:45 UTC (History)
6 users (show)

See Also:
Latest Commit:
Version Fixed In:

Attachments
Add an attachment

Note You need to log in before you can comment on or make changes to this bug.
Description Riccardo Robecchi 2022-01-17 18:04:18 UTC 
SUMMARY
Animations are rendered too fast when the display is set to use a resolution below the native one. In my case, I am using a desktop computer with a 4K screen (3840 x 2160)  set to FHD (1920 x 1080). Most animations where there's a spinning element, like the one on login and the notification timer, are way faster than they should.
I am using X11 on an AMD RX 5700 GPU with latest stable Mesa.


STEPS TO REPRODUCE
1. Connect your PC to a screen
2. Set resolution below the native one

OBSERVED RESULT
Animations are too fast.

EXPECTED RESULT
Animations are rendered at the same speed as normal.

SOFTWARE/OS VERSIONS
Linux: KDE neon
KDE Plasma Version:  5.23.5
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.3

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2022-01-20 21:26:10 UTC 
See also Bug 419421 and Bug 446637.

Did you also change the refresh rate? Or just the resolution?
Comment 2 Riccardo Robecchi 2022-01-20 22:15:35 UTC 
(In reply to Nate Graham from comment #1)
> See also Bug 419421 and Bug 446637.
> 
> Did you also change the refresh rate? Or just the resolution?

I only changed the resolution. The only refresh rate available, for some reason, is 30 Hz.
Comment 3 Nate Graham 2022-01-21 02:58:42 UTC 
But when you use the native resolution at 30hz refresh rate, everything is fine?
Comment 4 Riccardo Robecchi 2022-02-12 15:05:10 UTC 
(In reply to Nate Graham from comment #3)
> But when you use the native resolution at 30hz refresh rate, everything is
> fine?

It looks like the issue was the refresh rate and the resolution had nothing to do it at all. Also, it appears like I found another bug while investigating this.
The animations e.g. of the notification timeout appear to depend on the refresh rate, so they are normal at 60 Hz, double the length at 30 Hz and half the length at 120 Hz. This is independent of resolution.

What initially caused me to think the issue was related to resolution is bug 450087 which I just opened.
Comment 5 Nate Graham 2022-02-14 17:31:17 UTC 
Does it happen on Wayland too?
Comment 6 Riccardo Robecchi 2022-02-14 18:07:37 UTC 
(In reply to Nate Graham from comment #5)
> Does it happen on Wayland too?

No idea, I don't use Wayland as I simply can't start the session (it just displays a black screen with a cursor). As most of the software I use is not compatible with it, I never really bothered to understand why.
Comment 7 Nate Graham 2022-03-22 15:48:14 UTC 
*** Bug 451252 has been marked as a duplicate of this bug. ***
Comment 8 drokergeek 2022-03-22 16:33:34 UTC 
I've just tested under X11 and Wayland:
My timer for notifications is set for 5 seconds (the default)
X11: under 144Hz it lasts like 1.5s, 120Hz like 2s, 60Hz like 5s
Wayland: under 144Hz it lasts like 4s, under 120Hz like 5s, under 60Hz like
Comment 9 drokergeek 2022-03-22 16:36:17 UTC 
Sorry, doesn't allow me to edit. Wayland 60Hz is about 6 seconds
Comment 10 Nate Graham 2022-05-24 17:43:00 UTC 
*** Bug 454289 has been marked as a duplicate of this bug. ***
Comment 11 Nate Graham 2022-05-24 17:45:15 UTC 

*** This bug has been marked as a duplicate of bug 446637 ***