Bug 229471
| Summary: | x11/lightdm core dumps | ||
|---|---|---|---|
| Product: | Ports & Packages | Reporter: | Manuel Stühn <freebsd> |
| Component: | Individual Port(s) | Assignee: | Ben Woods <woodsb02> |
| Status: | Closed FIXED | ||
| Severity: | Affects Only Me | CC: | madpilot, matthias, mishin, seschwar, timp87 |
| Priority: | --- | Flags: | woodsb02:
maintainer-feedback+
woodsb02: merge-quarterly+ |
| Version: | Latest | ||
| Hardware: | Any | ||
| OS: | Any | ||
|
Description
Manuel Stühn
2018-07-02 08:11:19 UTC
Hello Manuel, thanks for reporting this issue. I experience the same core dump when running lightdm 1.24 (from pkg 2018Q3) built on FreeBSD 11.2. Before, I had used lightdm 1.24 built on FreeBSD 11.1 on the same FreeBSD 11.2 system and it worked. Did you already go further with a solution or a workaround for this? Kind regards, Matthias Hi Matthias, no, i did not track this further. BR Manuel I tried to compile lightdm (and lightdm-gtk-greeter) with gcc8 (maybe another gcc version is acceptable too) instead of clang and the lightdm is working again.
For that I made just following changes to /etc/make.conf:
---
.if (!empty(.CURDIR:M/usr/ports/x11/lightdm*))
CC:=${CC:C,^cc,/usr/local/bin/gcc8,1}
CXX:=${CXX:C,^c\+\+,/usr/local/bin/g++8,1}
.endif
A commit references this bug: Author: woodsb02 Date: Mon Feb 4 10:26:15 UTC 2019 New revision: 492108 URL: https://svnweb.freebsd.org/changeset/ports/492108 Log: x11/lightdm: Include pkg-message explaining how to fix LightDM coredumps PR: 229471 Submitted by: madpilot Reported by: Manuel St?hn <freebsd@justmail.de> MFH: 2019Q1 Changes: head/x11/lightdm/Makefile head/x11/lightdm/pkg-message Hi Manuel, Matthias, Alexander - can you please test if the solution in this pkg-message fixes this issue for you? LightDM needs the maximum amount of memory a daemon may request to be locked into main memory using mlock(2) to be increased above the FreeBSD default. Without doing this, LightDM will often crash when the service is started. To increase this limit, run the following commands: # sed -i '' -e 's/memorylocked=128M/memorylocked=256M/' /etc/login.conf # cap_mkdb /etc/login.conf A commit references this bug: Author: woodsb02 Date: Mon Feb 4 10:35:47 UTC 2019 New revision: 492110 URL: https://svnweb.freebsd.org/changeset/ports/492110 Log: MFH: r492108 x11/lightdm: Include pkg-message explaining how to fix LightDM coredumps PR: 229471 Submitted by: madpilot Reported by: Manuel St?hn <freebsd@justmail.de> Approved by: ports-secteam (miwi) Changes: _U branches/2019Q1/ branches/2019Q1/x11/lightdm/Makefile branches/2019Q1/x11/lightdm/pkg-message Closing this bug as this fixes it for me, but will re-open if anyone reports it doesn't work for them. Ideally we would do one of the following: 1. change the default value of this login.conf parameter on FreeBSD so that it works by default with LightDM, or 2. modify the LightDM code so it doesn't require a higher limit on locked memory for daemons. For item 1, I will open a discussion about this on the the FreeBSD-current mailing list. It might then be suitable in future releases of FreeBSD. For item 2, the following line in the source code is responsible for this daemon locking all memory to prevent it from being paged to disk. The reason provided in the code comments is that this daemon deals with passwords, so prevent them from being written to disk in swap. https://github.com/CanonicalLtd/lightdm/blob/1.28.0/src/session-child.c#L251 It might be possible for the code to only lock the memory which holds passwords. This should be reported and fixed upstream. (In reply to Ben Woods from comment #7) Hello, Ben! Have you had an opportunity to follow up your proposals and pass them to lightdm? You've got into the same trouble in lightdm-gtk-greeter and created a merge request https://code.launchpad.net/~timp87/lightdm-gtk-greeter/opt-mem-lock/+merge/373117 |
