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
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)
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
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
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
Touch seeded packages, which is subscribed to lightdm in Ubuntu.
https://bugs.launchpad.net/bugs/1662244
Title:
lightdm causes all greeters to fail to start
Status
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
** Also affects: lightdm
Importance: Undecided
Status: New
** Also affects: unity-greeter (Ubuntu)
Importance: Undecided
Status: New
** No longer affects: lightdm
** No longer affects: lightdm (Ubuntu)
** Summary changed:
- lightdm fails to start
+ unity-greeter crashes
Realized that it's likely unity-greeter because I'm seeing a lot of...
[25886.110278] traps: unity-greeter[820] trap int3 ip:7fb856a35241
sp:7fff145ad0f0 error:0 in libglib-2.0.so.0.5000.0[7fb8569e5000+11]
I've got libglib2.0 2.50.2-2ubuntu1 so I tried to roll back to 2.50.0-1
but that
So this issue bit me in a weird way. I had my bridge called "xenbr0" and
the result of these two interacting gives me absolutely no DNS
resolution since the /etc/resolv.conf just pointed to 127.0.0.53 and
didn't include the DNS server from my "xenbr0". Renaming the bridge to
"renbr0" caused it to
Public bug reported:
lightdm is failing to start. Best guess is because of unity-session-
manager. This is from .xsession-errors.
dbus-update-activation-environment: setting
_=/usr/bin/dbus-update-activation-environment
upstart: click-user-hooks main process (4028) terminated with status 1
11 matches
Mail list logo
