Bug 244318

Summary:	x11/kf5-kded: crash on session start
Product:	Ports & Packages	Reporter:	Martin Birgmeier <d8zNeCFG>
Component:	Individual Port(s)	Assignee:	freebsd-kde (group) <kde>
Status:	Closed FIXED
Severity:	Affects Only Me	CC:	arrowd, jimp, lobo, robbak, sv
Priority:	---	Flags:	arrowd: maintainer-feedback+
Version:	Latest
Hardware:	Any
OS:	Any

Description Martin Birgmeier 2020-02-22 18:15:28 UTC

Scenario:
- FreeBSD 12.1-RELEASE-p2 #3 r357330M
- ports updated to latest using portmaster

Result:
- Since a while kcrash shows a crash when starting a session. In xorg-session.log I find the following:

[0]% egrep -i 'kded|crash' .local/share/sddm/xorg-session.log 
kdeinit5: preparing to launch 'libkdeinit5_kded5'
Could not open kded5 using a library: Cannot load library libkdeinit5_kded5: (Shared object "libkdeinit5_kded5" not found, required by "kdeinit5")
kdeinit5: Launched KDED, pid = 2329 result = 0
Initializing  "kded_touchpad" :  "kcminit_touchpad"
KCrash: Attempting to start /usr/local/bin/kded5 from kdeinit
kdeinit5: Got EXEC_NEW '/usr/local/bin/kded5' from wrapper.
kdeinit5: preparing to launch '/usr/local/bin/kded5'
KCrash: crashing... crashRecursionCounter = 2
KCrash: Application Name = kded5 path = /usr/local/bin pid = 2329
KCrash: Arguments: /usr/local/bin/kded5 
KCrash: Attempting to start /usr/local/lib/libexec/drkonqi from kdeinit
org.kde.plasma: invalid metadata "/usr/local/lib/qt5/plugins/kcm_kded.so"
org.kde.plasma: invalid metadata "/usr/local/lib/qt5/plugins/kded_touchpad.so"
org.kde.plasma: invalid metadata "/usr/local/lib/qt5/plugins/kded_printmanager.so"
[0]% 

-- Martin

Comment 1 Gleb Popov freebsd_committer

2020-03-16 03:21:24 UTC

I had a problem like that. Try following:

1. pkg info -x activity
2. If there is kactivitysomething installed, remove this package only with -f.
3. Try logging again.

This made the crash gone for me.

Comment 2 Martin Birgmeier 2020-03-16 16:43:31 UTC

Interesting, thank you.

I have

[0]# pkg info -x activity                              
plasma5-kactivitymanagerd-5.18.3
[0]# pkg query %rn-%rv plasma5-kactivitymanagerd-5.18.3 
plasma5-plasma-workspace-5.18.3
plasma5-plasma-5.18.3
kf5-kactivities-stats-5.67.0
[0]# 

So plasma5-kactivitymanagerd is needed by three other packages.

Is it the one you deinstalled forcibly?

-- Martin

Comment 3 Gleb Popov freebsd_committer

2020-03-16 16:45:21 UTC

(In reply to Martin Birgmeier from comment #2)
Yep, do `pkg remove plasma5-kactivitymanagerd-5.18.3`.

Comment 4 Gleb Popov freebsd_committer

2020-05-17 12:15:25 UTC

Now I have plasma5-kactivitymanagerd package installed and kded5 doesn't crash anymore.

Martin, can you still reproduce the problem?

Comment 5 Martin Birgmeier 2020-05-17 17:53:26 UTC

Just finished recompiling and reinstalling all the plasma/kde stuff... and indeed, the crash seems gone (after the first startup with the brand-newly installed ports).

Let's close this.

-- Martin

Comment 6 Mario Lobo 2020-05-18 14:39:52 UTC

I have:

pkg info plasma5-kactivitymanagerd
plasma5-kactivitymanagerd-5.18.5
Name           : plasma5-kactivitymanagerd
Version        : 5.18.5
Installed on   : Mon May 11 11:34:34 2020 -03
Origin         : x11/plasma5-kactivitymanagerd
Architecture   : FreeBSD:13:amd64

And the crash still happens when starting a session.

Only a kded5.core file and 

/var/log/messages:May 18 09:22:54 Papi kernel: pid 1234 (kded5), jid 0, uid 0: exited on signal 11 (core dumped)

Comment 7 Martin Birgmeier 2020-05-19 17:12:11 UTC

Actually I also still have these crashes. I have no idea why there was no such crash right after installing the latest KF5/KDE updates (via portmaster). Maybe because the machine was not rebooted but just sddm restarted.

-- Martin

Comment 8 Mario Lobo 2020-05-19 19:39:22 UTC

This is all I get after the crash, besides the core file:

Application: kded5 (kded5), signal: Bus error
[KCrash Handler]
#8  0x00000008087644e4 in  () at /usr/local/lib/libgio-2.0.so.0
[Inferior 1 (process 1172) detached]

Comment 9 robbak 2020-05-20 02:04:05 UTC

(In reply to Mario Lobo from comment #8)
I have similar crashes in plasmashell. Not always exactly the same, but caused by qt50sqldrivers-sqlit pulling sme of its shared library functions from databases/sqlite3, and others from security/heimdal's sqlite3 library.

Post on the kde-freebsd mailing list - https://mail.kde.org/pipermail/kde-freebsd/2020-May/033969.html

Comment 10 Gleb Popov freebsd_committer

2020-06-10 07:11:16 UTC

Funny thing - compiling glib20 with debugging enabled makes crash go away and thus makes it impossible to analyze the crash.

kded5 from KDE master also doesn't reproduce it. If anyone has reliable reproducing steps, please share.

Comment 11 jimp 2020-07-15 14:45:45 UTC

Just hit a similar crash after updating a workstation

Based on the comments in this PR I was able to solve it, but had some noteworthy events along the way:

* Reconfigured ports which wanted Kerberos to disable or otherwise not use Heimdal (e.g. p5-Authen-SASL)

* Recompiled/reinstalled those ports, or removed if unneeded (e.g. p5-gssapi)

* Removed heimdal

* Recompiled qt5-sqldrivers-sqlite3 as well as plasma5-kactivitymanagerd, kf5-kactivities, and kf5-kactivities-stats for good measure

* Discovered that net/qt5-network had latched onto libgssapi.so.3 but had no registered dependency, recompiled that one, too.

* Now plasmashell works again (alt-F2, kstart5 plasmashell)

Comment 12 Gleb Popov freebsd_committer

2020-09-29 17:48:26 UTC

The glib20 update has been committed. Anyone can still reproduce the issue?

Comment 13 Martin Birgmeier 2020-09-29 17:59:39 UTC

I know that I had the crash until a few days ago. However, greping for kded in zfs snapshots of my home directory in .local/share/sddm/xorg-session.log reveals that the last time kcrash reported kded crashing was on Sep. 24. On this day /var/log/messages shows the update:

Sep 24 17:49:36 mizar pkg-static[77311]: glib-2.56.3_9,1 deinstalled
Sep 24 17:49:37 mizar pkg-static[77335]: glib-2.66.0_1,1 installed

So I assume the crashes have indeed stopped since then.

I'll close this issue.

Thank you for the work!

-- Martin