https://bugs.kde.org/show_bug.cgi?id=380495
--- Comment #5 from YOSHINO Yoshihito <yy.y.ja...@gmail.com> --- (In reply to David Edmundson from comment #4) > [01:15] <yyoshino_> d_ed: actually I do not figure out the problem on > wayland in pre-5.3.90 - On my machine startplasmacompositor seems to work > well both with or without this patch > > > I'm a bit lost. Do we think this patch needed or not? Yes, the patch is needed. Sorry I have mistyped, to clarify: On my X environment - startkde works well when the patch is applied. On my wayland envionment - startplasmacompositor works even without the patch due to another reason, but is not that good - not fully working. Because uim (an input method system I'm using) is currently broken on wayland, its daemon process crashes on startup and ksplash does not hang but the input method does not function. On my wayland environment I could not reproduce the original (pre-5.3.95) problem on wayland the commit https://cgit.kde.org/plasma-workspace.git/commit/?id=56d2c15b9acb9c4b57398b281685807c3191f622 has tried to fix. > There is another (possibly simpler?) way to solve this. We could background > immediately and then replace all the kill $ksplash_pid with kquitapp5 and > the DBus name. I would use the dbus quit interface, while I don't know at first glance why it does not work on my machine, with a following error: > Error: org.freedesktop.DBus.Error.UnknownObject > No such object path '/MainApplication' -- You are receiving this mail because: You are watching all bug changes.
