Bug 420549

Summary:	Telepathy-kde 20.04 causes long delay to plasma login completion
Product:	[Frameworks and Libraries] telepathy	Reporter:	MikeC <mike.cloaked>
Component:	general	Assignee:	Telepathy Bugs <kde-telepathy-bugs>
Status:	RESOLVED FIXED
Severity:	normal	CC:	322997am, alexandref75, answer2019, b.buschinski, davidroth9, demm, lex, natherul0, rdieter
Priority:	NOR
Version:	20.04
Target Milestone:	Future
Platform:	Arch Linux
OS:	Linux
Latest Commit:		Version Fixed In:
Attachments:	Bootchart for plasma on Arch as of today

Description MikeC 2020-04-25 09:25:17 UTC

SUMMARY
With telepathy-kde 20.04-1 plasma desktop login via sddm has a delay of around 30 seconds after initial desktop loads before the panel loads and login completes

STEPS TO REPRODUCE
1. Upgrade plasma kde-applications from 19.12.3-1 to 20.04-1
2. Login to plasma desktop
3. Login begins but hangs for around 30 seconds before the panel appears and login completes.

OBSERVED RESULT
Login has additional abnormal 30 second delay

EXPECTED RESULT
Login should complete almost instantly as normal

SOFTWARE/OS VERSIONS
 
Linux/KDE Plasma: Arch Linux telepathy-kde* 20.04-1
(available in About System)
KDE Plasma Version: 5.18.4.1-1
KDE Frameworks Version: 5.69.0-2
Qt Version: qt5-base 5.14.2-1

ADDITIONAL INFORMATION

May be unrelated but the telepathy-kde-meta package for the previous version was missing:

$ ls /var/cache/pacman/pkg/telepathy-kde-meta*
/var/cache/pacman/pkg/telepathy-kde-meta-19.12-1-any.pkg.tar.xz
/var/cache/pacman/pkg/telepathy-kde-meta-20.04-1-any.pkg.tar.zst

Workaround:

Downgrading all telepathy-kde packages to 19.12.3-1 except telepathy-kde-meta resolves the problem, and login to the plasma desktop becomes fast and normal again.

Comment 1 David Roth 2020-04-25 10:56:11 UTC

To be a bit more specific the KdedIntegrationModule seems to timeout during invocation

Apr 25 11:18:22 arch-videl dbus-daemon[866]: [session uid=1000 pid=866] Activating service name='org.freedesktop.Telepathy.Client.KTp.KdedIntegrationModule' requested by ':1.10' (uid=1000 pid=921 comm="/usr/lib/telepathy/mission-control-5 ")

Apr 25 11:20:22 arch-videl dbus-daemon[866]: [session uid=1000 pid=866] Failed to activate service 'org.freedesktop.Telepathy.Client.KTp.KdedIntegrationModule': timed out (service_start_timeout=120000ms)

Comment 2 MikeC 2020-04-25 12:01:20 UTC

Yes I have the analogous entry in my log:

$ sudo journalctl -b -1 | grep KdedIntegrationModule
Apr 24 15:46:51 home1 dbus-daemon[583]: [session uid=1000 pid=583] Activating service name='org.freedesktop.Telepathy.Client.KTp.KdedIntegrationModule' requested by ':1.17' (uid=1000 pid=675 comm="/usr/lib/telepathy/mission-control-5 ")
Apr 24 15:48:51 home1 dbus-daemon[583]: [session uid=1000 pid=583] Failed to activate service 'org.freedesktop.Telepathy.Client.KTp.KdedIntegrationModule': timed out (service_start_timeout=120000ms)
Apr 24 15:49:00 home1 plasma_waitforname[899]: org.kde.knotifications: WaitForName: Service was not registered within timeout

Comment 3 answer2019 2020-04-25 18:51:45 UTC

same here.
Distr: Gentoo.
affected package kde-apps/ktp-kded-module (KDE Telepathy workspace integration)
& some more symtoms: in ps ax listed: Z  0:00 [dbus-daemon] <defunct>  
+ freezed krunner after launched plasma panel

Comment 4 Lex Onderwater 2020-04-26 13:58:15 UTC

Ran into a similar issue but than with Krunner waiting 2 minutes for KdedIntegrationModule to be loaded. Turns out that the module filename is incorrect, so a quick fix is:

$ cd /usr/lib/qt/plugins/kf5/kded/
$ sudo ln -sv ktp_integration.so ktp_integration_module.so

See also https://bugs.archlinux.org/task/66420 and https://phabricator.kde.org/D28604

Comment 5 natherul0 2020-04-26 17:11:10 UTC

*** Bug 420591 has been marked as a duplicate of this bug. ***

Comment 6 322997am 2020-04-26 17:47:53 UTC

Created attachment 127898 [details]
Bootchart for plasma on Arch as of today

Comment 7 MikeC 2020-04-29 15:51:21 UTC

The workaround in comment #4 creating a soft link for ktp_integration_module.so does resolve the problem for me also.  Perhaps it is simply a typo in the source code that results in this issue?

Comment 8 MikeC 2020-04-30 19:12:10 UTC

This issue is resolved in the updated package: telepathy-kde-integration-module 20.04.0-2