Bug 248030 - x11/kde5 kded5 closed unexpectedly
Summary: x11/kde5 kded5 closed unexpectedly
Status: Closed FIXED
Alias: None
Product: Ports & Packages
Classification: Unclassified
Component: Individual Port(s) (show other bugs)
Version: Latest
Hardware: amd64 Any
: --- Affects Only Me
Assignee: freebsd-kde (group)
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2020-07-16 21:44 UTC by Scott Loga
Modified: 2020-07-21 17:36 UTC (History)
1 user (show)

See Also:
tcberner: maintainer-feedback+

Attachments
KDE Crash Handler Output (5.43 KB, text/plain)
2020-07-16 21:44 UTC, Scott Loga 		no flags Details
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Scott Loga 2020-07-16 21:44:13 UTC 
Created attachment 216501 [details]
KDE Crash Handler Output

FreeBSD Version - 12.1-RELEASE-p7
kde5-5.19.3.20.04.3
qt5.15.0

Hardware: Lenovo T480

Each time the laptop is rebooted, the following message appears in the KDE Crash Handler:

We are sorry, kded5 closed unexpectedly.
You cannot report this error, because kded5 does not provide a bug reporting address.

Details:

Executable: kded5 PID: 2862 Signal: Segmentation fault (11) Time: 7/16/20 4:20:42 PM CDT

Included as an attachment is the developer information from the KDE Crash Reporter.

If more information is required, please don't hesitate to reachout.

Regards,

Scott
Comment 1 Scott Loga 2020-07-20 14:51:18 UTC 
The latest pkg update on 07/19/2020 fixed this bug.

Not sure who to thank but it is very appreciated.

73, Scott
Comment 2 Tobias C. Berner freebsd_committer freebsd_triage 2020-07-21 17:36:03 UTC 
Moin moin 

Glad to hear it got away -- I still think there's some flakiness in the baloo startup or something that can lead to crashes on start.


mfg Tobias