Upgrading to (K)Ubuntu 18.04.5 LTS basically broke the system as X was
not restarting correctly (black screen instead of lightdm display or
even infinite loop of X crashes based on BIOS/EFI config).
This is critical for non-savvy users as my parents.
The issue is the same as can be seen in
Thanks
Adding
* soft memlock 262144
* hard memlock 262144
in /etc/security/limits.conf
solved the same problem with lightdm and X not starting on Ubuntu 18.04
running on a motherboard with VIA KM400 integrated graphics.
--
You received this bug notification because you are a member of Ubuntu
What torel proposed in https://bugs.launchpad.net/ubuntu/+source/unity-
greeter/+bug/1662244/comments/14 avoids the segfault:
* soft memlock 262144
* hard memlock 262144
Should all lightdm users manually put that in limits.conf, or should we
expect some update?
--
You received this bug
Hi, a recent systemd update in 18.04 makes slick-greeter segfault.
So all Ubuntu MATE 18.04 users now get black screens instead of lightdm.
It's related to memory limits so I'm cross-referencing it here:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1830746
This didn't help:
[LightDM]
(in lightdm.conf)
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662244
Title:
lightdm causes all greeters to fail to start
To manage notifications about this bug go to:
Does setting:
[LightDM]
lock-memory=false
Workaroud this issue?
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662244
Title:
lightdm causes all greeters to fail to start
To manage notifications
Seen on 18.04.1. WorkARound?
* soft memlock 262144
* hard memlock 262144
# End of file
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662244
Title:
lightdm causes all greeters to fail to start
This is BTW almost exactly the same what 'hugepages' does --
*increasing* memlock limits to 262144 kB.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662244
Title:
lightdm causes all greeters to
Please reopen. This just bit me on 17.10, using some manually
configured soft and hard memlock limits in /etc/security/limits.conf:
* softmemlock 262144
* hardmemlock 262144
As these limits *increase* max locked memory from 64 to 262144 kB, it
Sure enough removing the 'hugepages' package has solved the issue.
** Changed in: lightdm
Status: New => Invalid
** Changed in: lightdm-gtk-greeter
Status: New => Invalid
** Changed in: lightdm (Ubuntu)
Status: New => Invalid
** Changed in: unity-greeter (Ubuntu)
Well the ioctl() call isn't really an issue because stderr isn't hooked
to a tty in the way that a greeter is started up so that's normal.
The EAGAIN is interesting because I recently installed a package dealing
with hugepages and it created some rules in /etc/security/limits.d
--
You received
Just prior to the SIGTRAP I see a mmap() fail with EAGAIN and a failing
ioctl() call. This is from the attached strace with the other noise
trimmed out.
4108 mmap(NULL, 8392704, PROT_READ|PROT_WRITE, MAP_PRIVATE|MAP_ANONYMOUS|MAP_ST
ACK, -1, 0
4108 <... mmap resumed> ) = -1 EAGAIN
Unfortunately that didn't work. I went back to the versions that 16.10
originally shipped with and its still broken. I'm guessing some data
file that gets generated got corrupted and its causing this but I'm
unable to find it. I've taken an strace of lightdm-gtk-greeter showing
the failure to help
The lightdm.log is very repetitive so I just snipped out the last run
since they all appear to be identical.
** Attachment added: "snippet from lightdm.log"
https://bugs.launchpad.net/lightdm/+bug/1662244/+attachment/4816174/+files/lightdm.log
--
You received this bug notification because
Thanks for the response Robert. I'll give both a shot.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1662244
Title:
lightdm causes all greeters to fail to start
To manage notifications about this
Does the lightdm.log say anything useful? The stack trace looks like an
out of memory condition, which could be either liblightdm or GTK+
failing to work? I'd suggest trying different versions of those
libraries.
--
You received this bug notification because you are a member of Ubuntu
Bugs,
I've tried lightdm-gtk-greeter and kylin-greeter and the same crash
occurs. So I'm back to thinking this issue is with lightdm. Some data or
configuration its passing to the greeter is causing it to fail.
I've removed all the dot directories (.cache, .config, .dbus, .gconf,
and .local) inside of
17 matches
Mail list logo
