Bug 479824

Summary: The splash screen was shown for about 20 s when starting Plasma 5.92.0 while Plasma completed startup after 3-5 s with splash screen set to None
Product: [Plasma] plasmashell Reporter: Matt Fagnani <matt.fagnani>
Component: generic-performanceAssignee: Plasma Bugs List <plasma-bugs>
Status: RESOLVED DUPLICATE    
Severity: normal CC: nate
Priority: NOR Keywords: qt6
Version: 5.92.0   
Target Milestone: 1.0   
Platform: Fedora RPMs   
OS: Linux   
Latest Commit: Version Fixed In:
Sentry Crash Report:
Attachments: Journal for Plasma 5.92.0 session startup where the splash screen was shown for 20 s

Description Matt Fagnani 2024-01-14 23:36:38 UTC
Created attachment 164907 [details]
Journal for Plasma 5.92.0 session startup where the splash screen was shown for 20 s

SUMMARY

The splash screen was shown for about 20 s each time I've logged in to Plasma 5.92.0 on Wayland in a Fedora Rawhide/40 KDE Plasma installation. When I moved the mouse to the top left of the screen while the splash screen was shown after 3-5 s, the desktop was shown to have completed startup in one of the overview windows. There were amdgpu errors in the journal like "kwin_wayland_wrapper[1641]: amdgpu: amdgpu_cs_ctx_create2 failed. (-13)" when kwin_wayland was starting as the Plasma and sddm compositors which continued as the splash screen was shown and after the desktop appeared.

Jan 14 17:00:22 kwin_wayland[1641]: No backend specified, automatically choosing drm
Jan 14 17:00:22 wireplumber[1669]: <WpPortalPermissionStorePlugin:0x55eb35e93a20> Failed to call Lookup: GDBus.Error:org.freedesktop.portal.Error.NotFound: No entry for camera
Jan 14 17:00:22 kwin_wayland_wrapper[1641]: amdgpu: amdgpu_cs_ctx_create2 failed. (-13)
Jan 14 17:00:22 kwin_wayland_wrapper[1641]: amdgpu: amdgpu_cs_ctx_create2 failed. (-13)
Jan 14 17:00:22 kwin_wayland[1641]: OpenGL vendor string:                   AMD
Jan 14 17:00:22 kwin_wayland[1641]: OpenGL renderer string:                 AMD Radeon R5 Graphics (radeonsi, carrizo, LLVM 17.0.6, DRM 3.56, 6.7.0-68.fc40.x86_64)
Jan 14 17:00:22 kwin_wayland[1641]: OpenGL version string:                  4.6 (Core Profile) Mesa 23.3.3
Jan 14 17:00:22 kwin_wayland[1641]: OpenGL shading language version string: 4.60
Jan 14 17:00:22 kwin_wayland[1641]: Driver:                                 Unknown
Jan 14 17:00:22 kwin_wayland[1641]: GPU class:                              Unknown
Jan 14 17:00:22 kwin_wayland[1641]: OpenGL version:                         4.6
Jan 14 17:00:22 kwin_wayland[1641]: GLSL version:                           4.60
Jan 14 17:00:22 kwin_wayland[1641]: Mesa version:                           23.3.3
Jan 14 17:00:22 kwin_wayland[1641]: Requires strict binding:                no
Jan 14 17:00:22 kwin_wayland[1641]: Virtual Machine:                        no
Jan 14 17:00:22 kwin_wayland[1641]: Timer query support:                    yes

There were journal errors showing plasmashell aborting shell load because kactivitymanagerd wasn't running yet.

Jan 14 17:00:25 plasmashell[1857]: kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Jan 14 17:00:25 plasmashell[1857]: kde.plasmashell: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.
Jan 14 17:00:25 kactivitymanagerd[1918]: kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11
Jan 14 17:00:25 kactivitymanagerd[1918]: kf.windowsystem: virtual void KX11Extras::connectNotify(const QMetaMethod&) may only be used on X11
Jan 14 17:00:25 systemd[1521]: Started plasma-kactivitymanagerd.service - KActivityManager Activity manager Service.
Jan 14 17:00:25 plasmashell[1857]: kde.plasmashell: Aborting shell load: The activity manager daemon (kactivitymanagerd) is not running.
Jan 14 17:00:25 plasmashell[1857]: kde.plasmashell: If this Plasma has been installed into a custom prefix, verify that its D-Bus services dir is known to the system for the daemon to be activatable.

plasma-ksplash.service ran for 32 s.

systemctl status --user plasma-ksplash.service
○ plasma-ksplash.service - Splash screen shown during boot
     Loaded: loaded (/usr/lib/systemd/user/plasma-ksplash.service; static)
    Drop-In: /usr/lib/systemd/user/service.d
             └─10-timeout-abort.conf
     Active: inactive (dead)

Jan 14 17:00:21 localhost.localdomain systemd[1521]: Starting plasma-ksplash.service - Splash screen shown during boot...
Jan 14 17:00:53 localhost.localdomain systemd[1521]: Finished plasma-ksplash.service - Splash screen shown during boot.
Jan 14 17:00:53 localhost.localdomain systemd[1521]: plasma-ksplash.service: Consumed 3.215s CPU time.

I'll attach the journal for this Plasma session startup.

I set the splash screen to None in System Settings, logged out and logged in. Plasma completed startup after 3-5 s without a splash screen. The splash screen was shown for 3-5 s when starting Plasma 5.27.10 and earlier on the same system. 

STEPS TO REPRODUCE
1. Boot a Fedora Rawhide/40 KDE Plasma installation updated to 2024-1-14
2. Log in to Plasma 5.92.0 on Wayland

OBSERVED RESULT
The splash screen was shown for about 20 s when starting Plasma 5.92.0 while Plasma completed startup after 3-5 s with splash screen set to None

EXPECTED RESULT
The splash screen should have been shown for 3-5 s when starting Plasma 5.92.0, and then the desktop would be shown

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora Rawhide/40
(available in About System)
KDE Plasma Version: 5.92.0
KDE Frameworks Version: 5.248.0
Qt Version: 6.6.1

ADDITIONAL INFORMATION
Comment 1 Nate Graham 2024-01-17 22:07:02 UTC

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