https://bugs.kde.org/show_bug.cgi?id=420248
Bug ID: 420248
Summary: plasmawindowed org.kde.plasma.networkmanagement takes
awfully long to show a window under Sway WM / Wayland
Product: plasmashell
Version: 5.18.4
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: generic-wayland
Assignee: plasma-b...@kde.org
Reporter: devuran...@gmx.net
Target Milestone: 1.0
SUMMARY
plasmawindowed takes a very long time to show a window.
STEPS TO REPRODUCE
1. Start a Sway WM session from SDDM
2. Open a terminal and execute `plasmawindowed
org.kde.plasma.networkmanagement`
3. Wait
OBSERVED RESULT
Immediately after start the following is printed:
qt5ct: using qt5ct plugin
org.kde.plasmaquick: Applet preload policy set to 1
Then nothing happens for a long time (approx 30s).
Then the following is printed:
Couldn't start kglobalaccel from org.kde.kglobalaccel.service:
QDBusError("org.freedesktop.DBus.Error.NoReply", "Did not receive a reply.
Possible causes include: the remote application did not send a reply, the
message bus security policy blocked the reply, the reply timeout expired, or
the network connection was broken.")
Again nothing happens for a long time (another 30s?).
Then the following is printed and the window appears at approximately the same
time:
org.kde.plasma: requesting config for "Networks" without a containment!
qml: 0
DBusMenu disabled for this application
EXPECTED RESULT
The window appears immediately.
SOFTWARE/OS VERSIONS
Operating System: Gentoo Linux
KDE Plasma Version: 5.18.4
KDE Frameworks Version: 5.69.0
Qt Version: 5.14.2
Kernel Version: 5.6.4
OS Type: 64-bit
Processors: 8 × AMD Ryzen 5 2400G with Radeon Vega Graphics
Memory: 13.5 GiB of RAM
Sway WM Version: 1.4
ADDITIONAL INFORMATION
Other KDE applications also take a long time to start. I most notably remember
Okular taking its time to start. KMail on the other hand starts almost
instantly.
--
You are receiving this mail because:
You are watching all bug changes.
