Bug 440884

Summary:	dolphin slow launch on wayland
Product:	[Applications] dolphin	Reporter:	Mikel Pérez <io>
Component:	general	Assignee:	Dolphin Bug Assignee <dolphin-bugs-null>
Status:	RESOLVED WORKSFORME
Severity:	normal	CC:	kfm-devel, meven29, nate
Priority:	NOR	Keywords:	wayland
Version:	21.04.2
Target Milestone:	---
Platform:	Other
OS:	Linux
Latest Commit:		Version Fixed In:

Description Mikel Pérez 2021-08-12 00:57:53 UTC

SUMMARY
dolphin takes a lot of time to open on wayland

STEPS TO REPRODUCE
1. launch dolphin
2. wait for the main window to appear

OBSERVED RESULT
the window takes about 30 seconds to appear. the following is printed on the terminal:

kf.xmlgui: KActionCollection::setComponentName does not work on a KActionCollection containing actions! "dolphin"
(takes its ~30 seconds here with no output)
kf.dbusaddons: 'kdeinit5' is taking more than 30 seconds to start.
(dolphin window appears)

EXPECTED RESULT
instant dolphin window

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 34
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2

Comment 1 Nate Graham 2021-08-12 16:45:39 UTC

Are you using Dolphin in a Plasma environment, or in GNOME or another DE?

Comment 2 Mikel Pérez 2021-08-14 00:26:47 UTC

(In reply to Nate Graham from comment #1)
> Are you using Dolphin in a Plasma environment, or in GNOME or another DE?

Plasma 5.22.4

Comment 3 Mikel Pérez 2021-08-14 00:28:54 UTC

(In reply to Mikel Pérez from comment #2)

plasma wayland

Comment 4 Méven Car 2021-08-14 11:11:51 UTC

What happen if you launch in a terminal kdeinit5 while this blocking occurs ?

Do you experience this all the time ?

Do you use network file systems mount ?

I know about a rarely occurring similar bug in X11 but due to X11 intricacies.

Comment 5 Mikel Pérez 2021-10-19 15:36:16 UTC

(In reply to Méven Car from comment #4)
> What happen if you launch in a terminal kdeinit5 while this blocking occurs ?
> 
> Do you experience this all the time ?
> 
> Do you use network file systems mount ?
> 
> I know about a rarely occurring similar bug in X11 but due to X11
> intricacies.

sorry for not answering then but it seems fixed