Bug 244661

Summary: x11/plasma5-plasma: kcm_kscreen crashes when open it from systemsettings5
Product: Ports & Packages Reporter: Serge Volkov <sv>
Component: Individual Port(s)Assignee: freebsd-kde (group) <kde>
Status: Closed FIXED    
Severity: Affects Only Me CC: d8zNeCFG, kde, tcberner
Priority: --- Keywords: crash, needs-qa
Version: LatestFlags: tcberner: maintainer-feedback+
koobs: merge-quarterly?
Hardware: amd64   
OS: Any   
URL: https://bugs.kde.org/show_bug.cgi?id=417548
Attachments:
Description Flags
dmesg.boot
none
List of installed packages
none
kcrash report none

Description Serge Volkov 2020-03-07 21:42:07 UTC
Hello All!

I noticed a problem. When I open the Screen dialog from the plasma5 System Settings, it crashes. If I open the same dialog with a command `kcmshell5 kcm_kscreen`, then everything is fine. I have the latest packages installed.

Does anyone else have such a problem? And are there any suggestions for a solution?
Comment 1 Kubilay Kocak freebsd_committer freebsd_triage 2020-03-08 01:40:03 UTC
@Serge Could you please provide additional information including:

- Exact FreeBSD version (uname -a) output
- pkg version -v output (as an attachment)
- /var/run/dmesg.boot output (as an attachment)

Obtaining a backtrace of the crashing process (and providing it as an attachment) would also be great.
Comment 2 Kubilay Kocak freebsd_committer freebsd_triage 2020-03-08 01:42:49 UTC
@Serge Could you please provide additional information including:

- Exact FreeBSD version (uname -a) output
- pkg version -v output (as an attachment)
- /var/run/dmesg.boot output (as an attachment)

Obtaining a backtrace of the crashing process (and providing it as an attachment) would also be great.
Comment 3 Tobias C. Berner freebsd_committer freebsd_triage 2020-03-08 07:03:49 UTC
Moin moin 

Do you mean the 'Display configuration' where you configure the monitor arrangement and such?


mfg Tobias
Comment 4 Martin Birgmeier 2020-03-08 07:05:49 UTC
I have the same issue.

FreeBSD mizar.xyzzy 12.1-RELEASE-p2 FreeBSD 12.1-RELEASE-p2 #3 r357330M: Fri Jan 31 14:39:48 CET 2020     root@v904.xyzzy:/.../hal/z/OBJ/FreeBSD/amd64/releng/12.1/amd64.amd64/sys/XYZZY_SMP  amd64

I don't get a core dump, instead the kcrash handler is running...

-- Martin
Comment 5 Martin Birgmeier 2020-03-08 07:07:43 UTC
And yes, it is "Display and Monitor"

I am running the closed-source nvidia driver btw.

-- Martin
Comment 6 Tobias C. Berner freebsd_committer freebsd_triage 2020-03-08 07:16:37 UTC
(In reply to Martin Birgmeier from comment #5)
Hm, works just fine for me on nvidia [1]

Are your packages all up-to-date?

mfg Tobias

[1] https://people.freebsd.org/~tcberner/pictures/screen_settings.png
Comment 7 Serge Volkov 2020-03-08 08:31:53 UTC
Created attachment 212249 [details]
dmesg.boot
Comment 8 Serge Volkov 2020-03-08 08:32:32 UTC
Created attachment 212250 [details]
List of installed packages
Comment 9 Serge Volkov 2020-03-08 08:33:27 UTC
Created attachment 212251 [details]
kcrash report
Comment 10 Serge Volkov 2020-03-08 08:37:28 UTC
Yes, it is "Display and Monitor".

uname -a
FreeBSD ulbsd 12.1-RELEASE-p2 FreeBSD 12.1-RELEASE-p2 ULBSD  amd64

And I use VESA or i915kms.ko drivers. The result is the same.
Comment 11 Serge Volkov 2020-03-08 08:44:38 UTC
(In reply to Tobias C. Berner from comment #6)

Yes, Display and Monitor works fine if View Style of System Settings is "Sidebar View". If the Style of System Settings is "Icon View", then Display and Monitor crashes.
Comment 12 Serge Volkov 2020-03-08 08:50:16 UTC
But in "Sidebar View" mode System Settings crashes if select "Night Color" in Display and Monitor section.
Comment 13 Tobias C. Berner freebsd_committer freebsd_triage 2020-03-08 08:50:50 UTC
(In reply to Serge Volkov from comment #11)
Indeed, switching to Icon View makes it crash.

Have you checked upstream for similar reports already?



mfg Tobias
Comment 14 Martin Birgmeier 2020-03-08 08:51:29 UTC
Interesting... same here, works from sidebar up to a certain point - "night color" crashes.
Comment 15 Tobias C. Berner freebsd_committer freebsd_triage 2020-03-08 09:12:00 UTC
The issue seems to be that we at the moment cannot provide the 'geolocation' dataengine, and the night-shift plugins' qml depends on it.

You can quickly edit 
/usr/local/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml
and remove the  
CC.Geolocation {
   [...]
}
block to confirm this.


mfg Tobias
Comment 16 commit-hook freebsd_committer freebsd_triage 2020-03-08 09:21:15 UTC
A commit references this bug:

Author: tcberner
Date: Sun Mar  8 09:20:24 UTC 2020
New revision: 528006
URL: https://svnweb.freebsd.org/changeset/ports/528006

Log:
  x11/kf5-plasma-framewors: add upstream fix for dataengine initialization

  This fixes a crash in the systemsettings 'night colors' screen configuration

  PR:		244661
  Reported by:	Serge Volkov <sv@ulstu.ru>, Martin Birgmeier <d8zNeCFG@aon.at>

Changes:
  head/x11/kf5-plasma-framework/Makefile
  head/x11/kf5-plasma-framework/distinfo
Comment 17 Martin Birgmeier 2020-03-08 09:25:09 UTC
Thank you Tobias for finding this.

Regarding the KDE issue entry - could this also solve bug #236174 which I now experience again since some time?

-- Martin
Comment 18 Serge Volkov 2020-03-08 10:26:58 UTC
(In reply to Tobias C. Berner from comment #15)

Removing the CC.Geolocator block in /usr/local/share/kpackage/kcms/kcm_nightcolor/contents/ui/main.qml solves the problem.

Thank you!
Comment 19 Tobias C. Berner freebsd_committer freebsd_triage 2020-03-08 10:31:31 UTC
(In reply to Serge Volkov from comment #18)
With the update kf5-kcmutils port (see commit above) it should work unmodified too :)

mfg Tobias
Comment 20 Serge Volkov 2020-03-08 10:38:35 UTC
(In reply to Tobias C. Berner from comment #19)

> With the update kf5-kcmutils port (see commit above) it should work unmodified too :)

Thank you, Tobias! I understood.
Comment 21 Tobias C. Berner freebsd_committer freebsd_triage 2020-03-08 20:18:16 UTC
(In reply to Martin Birgmeier from comment #17)
Hm, could be -- I also sometimes get them on my notebook too unfortunately; so let's see if they are gone :)