Reply to topic

Stuck in the last step of splash screen for ~30 seconds

jinliu
Registered Member
Posts
6
Karma
0
I'm using the plasma-desktop package in Archlinux AUR. The startup process stucks in the last step of splash (progress bar is full) for about 30 seconds, then the desktop appears.
The system journal just before/after the pause:

7月 16 21:24:53 jin-zenbook bash[384]: load abbr
7月 16 21:24:53 jin-zenbook kdeinit5[450]: Fetched layout groups from X server: layouts: ("us") variants: ("")
7月 16 21:24:53 jin-zenbook kdeinit5[450]: Fetched layout groups from X server: layouts: ("us") variants: ("")
7月 16 21:24:53 jin-zenbook kdeinit5[450]: Fetched layout groups from X server: layouts: ("us") variants: ("")
7月 16 21:24:53 jin-zenbook kdeinit5[450]: Fetched layout groups from X server: layouts: ("us") variants: ("")
7月 16 21:24:53 jin-zenbook kdeinit5[450]: Fetched layout groups from X server: layouts: ("us") variants: ("")
7月 16 21:24:53 jin-zenbook kdeinit5[450]: Fetched layout groups from X server: layouts: ("us") variants: ("")
7月 16 21:24:53 jin-zenbook kdeinit5[450]: Fetched layout groups from X server: layouts: ("us") variants: ("")
7月 16 21:24:53 jin-zenbook kdeinit5[450]: Fetched layout groups from X server: layouts: ("us") variants: ("")
7月 16 21:24:53 jin-zenbook bash[384]: libpng warning: iCCP: known incorrect sRGB profile
7月 16 21:25:20 jin-zenbook systemd-timesyncd[188]: Using NTP server 216.239.36.15:123 (time3.google.com).
7月 16 21:25:20 jin-zenbook systemd-timesyncd[188]: interval/delta/delay/jitter/drift 32s/+0.354s/0.055s/0.000s/+0ppm
7月 16 21:25:31 jin-zenbook kdeinit5[450]: Fetched layout groups from X server: layouts: ("us") variants: ("")
7月 16 21:25:33 jin-zenbook kwin_x11[510]: check_startup
7月 16 21:25:33 jin-zenbook kwin_x11[510]: User timestamp, ASN: 53277
7月 16 21:25:33 jin-zenbook kwin_x11[510]: User timestamp, final: 'ID: 31457351 ;WMCLASS: "plasmashell" : "plasmashell" ;Caption: "Plasma" ' : 532
7月 16 21:25:33 jin-zenbook kwin_x11[510]: Activation: No client active, allowing
7月 16 21:25:33 jin-zenbook kwin_x11[510]: screens: 1 desktops: 1
7月 16 21:25:33 jin-zenbook kwin_x11[510]: Done.
7月 16 21:25:33 jin-zenbook kwin_x11[510]: KWin::Client(0x2bc5500) true false false
7月 16 21:25:33 jin-zenbook kwin_x11[510]: PERMITTED 'ID: 31457351 ;WMCLASS: "plasmashell" : "plasmashell" ;Caption: "Plasma" ' true
7月 16 21:25:33 jin-zenbook kwin_x11[510]: check_startup
7月 16 21:25:33 jin-zenbook kwin_x11[510]: User timestamp, ASN: 53442
7月 16 21:25:33 jin-zenbook kwin_x11[510]: User timestamp, final: 'ID: 31457370 ;WMCLASS: "plasmashell" : "plasmashell" ;Caption: "Plasma <2>
7月 16 21:25:33 jin-zenbook kwin_x11[510]: Activation: Belongs to active application
7月 16 21:25:33 jin-zenbook kwin_x11[510]: screens: 1 desktops: 1

Since the messages immediately before/after the pause are "Fetched layout groups from X server", could it be something about my keyboard layout?

Thanks,
Jin
User avatar einar
Administrator
Posts
3400
Karma
7
OS
Are there any messages sent to ~/.xsession-errors?


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
jinliu
Registered Member
Posts
6
Karma
0
No, all messages are in systemd-journal. No .xsession-errors file.

After further investigation, I found that the desktop actually loads in less than 3 seconds, but plasmashell failed to call KSplashQML.setStage("desktop") in shellcorona.cpp for unknown reason, so ksplash didn't exit until the built-in 30s timeout.

I worked around the problem by watching kwin log, wait for plasmashell window to appear, and call ksplashqml:
Code: Select all
#!/bin/bash

while ! (journalctl -b _COMM=kwin_x11 | grep -q 'WMCLASS: "plasmashell" : "plasmashell"'); do
        sleep 1
done
qdbus org.kde.KSplash /KSplash org.kde.KSplash.setStage desktop
User avatar einar
Administrator
Posts
3400
Karma
7
OS
This would IMO warrant a bug filed on bugs.kde.org. If you do, please provide detailed information on your setup.


"Violence is the last refuge of the incompetent."
Image
Plasma FAQ maintainer - Plasma programming with Python
jinliu
Registered Member
Posts
6
Karma
0
Fixed in Plasma 5.0.1.
enoop
Registered Member
Posts
101
Karma
0
I'm still getting this problem, I can see that the desktop is loaded because I can see through the splash screen on the left side. I have to kill the splash screen, otherwise it takes quite a while for it to close on its own.

 
Reply to topic

Bookmarks



Who is online

Registered users: Baidu [Spider], Bing [Bot], Google [Bot], judithh, lueck, Majestic-12 [Bot], Sogou [Bot], TristanDee