https://bugs.kde.org/show_bug.cgi?id=511430
Bug ID: 511430
Summary: Splash screens close before plasmashell has finished
initializing when using a high refresh rate monitor
Classification: Plasma
Product: plasmashell
Version First 6.5.1
Reported In:
Platform: openSUSE
OS: Linux
Status: REPORTED
Severity: wishlist
Priority: NOR
Component: Splash Screens
Assignee: [email protected]
Reporter: [email protected]
Target Milestone: 1.0
SUMMARY
I was trying to figure out why the splash screens for KDE Plasma were closing
after only about a second after logging in. This happens before all of the
desktop components were initialized. When this happens, all I can see is my
wallpaper and mouse, desktop components aren't fully loaded in for at least a
second or two. I did a fresh install of openSUSE Tumbleweed to try and
reproduce any steps that I had done to get to this issue and noticed that the
issue only persists when I changed my monitors refresh rate from 60Hz to 180Hz.
At 60hz, the splash screens will remain visible until the Plasma desktop has
fully loaded its components.
STEPS TO REPRODUCE
1. Change refresh rate of monitor to 180Hz.
OBSERVED RESULT
Splash screens no longer wait until the Plasma desktop has fully loaded.
EXPECTED RESULT
Splash screen should remain on screen until the Plasma desktop has fully
loaded.
SOFTWARE/OS VERSIONS
Linux: openSUSE Tumbleweed
KDE Plasma Version: 6.5.1
KDE Frameworks Version: 6.19.0
Qt Version: 6.10.0
HARDWARE INFORMATION
CPU: AMD Ryzen 9 9900X3D
GPU: AMD Radeon RX 9070 XT
RAM: 96GB (2x48GB) DDR5
Monitor 1: ASUSTek COMPUTER INC VG259Q3A
Monitor 2: HP Inc. OMEN 25i
ADDITIONAL INFORMATION
I have not dug into this very thoroughly once I found out what was causing the
issue, but if this ends up not being easily reproduce-able for other Plasma
desktop users I can provide more information and/or try and replicate the issue
on other distributions running the KDE Plasma desktop on bare metal. Please let
me know if there is any more information needed from me.
--
You are receiving this mail because:
You are watching all bug changes.
