I'm on a xenial ubuntu-desktop and have snappy dimension on classic installed. I was working on other things and apport popped up. The trigger seems to be the background snappy update task for ubuntu-core that triggers a reboot of ubuntu-core. Looking at my logs I see:
Mar 21 10:00:30 <hostname> systemd[1]: Started Ubuntu Core Snappy AutoUpdate. Mar 21 10:01:02 <hostname> systemd[1]: Mounting Squashfs mount unit for ubuntu-core... Mar 21 10:01:02 <hostname> systemd[1]: Mounted Squashfs mount unit for ubuntu-core. Mar 21 10:01:03 <hostname> snappy[25381]: Name Date Version Developer Mar 21 10:01:03 <hostname> snappy[25381]: ubuntu-core 2016-03-21 16.04-20160321-05-01 canonical! Mar 21 10:01:03 <hostname> snappy[25381]: Reboot to use ubuntu-core version 16.04-20160321-05-01. Mar 21 10:01:03 <hostname> snappy[25381]: Rebooting to satisfy updates for ubuntu-core Mar 21 10:01:03 <hostname> kernel: [85783.825747] systemd-logind[1101]: segfault at 0 ip 00007fc5cafcfd9e sp 00007ffc1cf 580b8 error 4 in libc-2.21.so[7fc5caf30000+1c0000] Mar 21 10:01:03 <hostname> systemd[1]: systemd-logind.service: Main process exited, code=dumped, status=11/SEGV Mar 21 10:01:03 <hostname> systemd[1]: systemd-logind.service: Unit entered failed state. Mar 21 10:01:03 <hostname> /usr/bin/snappy[25381]: main.go:50: DEBUG: [/usr/bin/snappy update --automatic-reboot] failed : failed to auto reboot: Failed to call ScheduleShutdown in logind, proceeding with immediate shutdown: Message re cipient disconnected from message bus without replying Mar 21 10:01:03 <hostname> snappy[25381]: failed to auto reboot: Failed to call ScheduleShutdown in logind, proceeding w ith immediate shutdown: Message recipient disconnected from message bus without replying Mar 21 10:01:03 <hostname> systemd[1]: systemd-logind.service: Failed with result 'core-dump'. Mar 21 10:01:03 <hostname> systemd[1]: snappy-autopilot.service: Main process exited, code=exited, status=1/FAILURE Mar 21 10:01:03 <hostname> systemd[1]: snappy-autopilot.service: Unit entered failed state. Mar 21 10:01:03 <hostname> systemd[1]: snappy-autopilot.service: Failed with result 'exit-code'. Mar 21 10:01:03 <hostname> systemd[1]: systemd-logind.service: Service has no hold-off time, scheduling restart. Mar 21 10:01:03 <hostname> systemd[1]: Stopped Login Service. Mar 21 10:01:03 <hostname> dbus[1163]: [system] Activating via systemd: service name='org.freedesktop.login1' unit='dbus -org.freedesktop.login1.service' Mar 21 10:01:03 <hostname> systemd[1]: Starting Login Service... Mar 21 10:01:03 <hostname> dbus[1163]: [system] Successfully activated service 'org.freedesktop.login1' Mar 21 10:01:03 <hostname> systemd[1]: Started Login Service. Mar 21 10:01:03 <hostname> systemd[1]: Started User Manager for UID 1000. Mar 21 10:01:03 <hostname> systemd[1]: Started User Manager for UID 119. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553040 Title: systemd-logind crashed with SIGSEGV To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1553040/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
