Bug 454232 - Prompt log out dialog is laggy under Wayland
Summary: Prompt log out dialog is laggy under Wayland
Status: RESOLVED DUPLICATE of bug 418194
Alias: None
Product: ksmserver
Classification: Unmaintained
Component: general (show other bugs)
Version: 5.24.90
Platform: Arch Linux Linux
: NOR normal
Target Milestone: ---
Assignee: David Edmundson
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-05-22 18:58 UTC by Cristóbal Veas
Modified: 2022-05-23 20:19 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments
For some reason in the video the lag isn't so much noticeable. (1005.12 KB, video/mp4)
2022-05-22 18:58 UTC, Cristóbal Veas
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Cristóbal Veas 2022-05-22 18:58:50 UTC
Created attachment 149119 [details]
For some reason in the video the lag isn't so much noticeable.

SUMMARY
The prompt log out dialog (where you can also choose if you want to shutdown or restart your PC or just put it to sleep) is laggy when using KDE Plasma under Wayland.

STEPS TO REPRODUCE
1. Open "System Settings" and go to "Energy Saving".
2. In the "Button events handling" section go to "When power button pressed" and there choose "Prompt log out dialog".
3. Apply the changes and then use the power button to make the prompt log out dialog appear.
4. Use the cursor or the arrow keys to move across the buttons.

OBSERVED RESULT
The animations and the cursor are laggy.

EXPECTED RESULT
The animations are smooth and the cursor isn't laggy.

SOFTWARE/OS VERSIONS
Operating System: Arch Linux
KDE Plasma Version: 5.24.90
KDE Frameworks Version: 5.94.0
Qt Version: 5.15.4
Kernel Version: 5.17.9-arch1-1 (64-bit)
Graphics Platform: Wayland
Processors: 4 × Intel® Core™ i3-2350M CPU @ 2.30GHz
Memory: 7.7 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 3000

ADDITIONAL INFORMATION
This didn't happen in KDE Plasma 5.24. The bug is only reproducible under Wayland.
Comment 1 Nate Graham 2022-05-23 20:19:04 UTC
*** This bug has been marked as a duplicate of bug 418194 ***