[Bug 1560072] Re: systemd-logind crashed with SIGSEGV

Mon Mar 21 15:09:42 UTC 2016

*** This bug is a duplicate of bug 1553040 ***
    https://bugs.launchpad.net/bugs/1553040

Thank you for taking the time to report this crash and helping to make
this software better.  This particular crash has already been reported
and is a duplicate of bug #1553040, so is being marked as such.  Please
look at the other bug report to see if there is any missing information
that you can provide, or to see if there is a workaround for the bug.
Additionally, any further discussion regarding the bug should occur in
the other report.  Please continue to report any other bugs you may
find.

** Attachment removed: "CoreDump.gz"
   https://bugs.launchpad.net/bugs/1560072/+attachment/4606472/+files/CoreDump.gz

** Attachment removed: "Disassembly.txt"
   https://bugs.launchpad.net/bugs/1560072/+attachment/4606475/+files/Disassembly.txt

** Attachment removed: "ProcMaps.txt"
   https://bugs.launchpad.net/bugs/1560072/+attachment/4606481/+files/ProcMaps.txt

** Attachment removed: "ProcStatus.txt"
   https://bugs.launchpad.net/bugs/1560072/+attachment/4606483/+files/ProcStatus.txt

** Attachment removed: "Registers.txt"
   https://bugs.launchpad.net/bugs/1560072/+attachment/4606484/+files/Registers.txt

** Attachment removed: "Stacktrace.txt"
   https://bugs.launchpad.net/bugs/1560072/+attachment/4606486/+files/Stacktrace.txt

** Attachment removed: "ThreadStacktrace.txt"
   https://bugs.launchpad.net/bugs/1560072/+attachment/4606489/+files/ThreadStacktrace.txt

** This bug has been marked a duplicate of bug 1553040
   systemd-logind crashed with SIGSEGV

** Information type changed from Private to Public

** Tags removed: need-amd64-retrace

-- 
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to systemd in Ubuntu.
https://bugs.launchpad.net/bugs/1560072

Title:
  systemd-logind crashed with SIGSEGV

Status in systemd package in Ubuntu:
  New

Bug description:
  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.

  ProblemType: Crash
  DistroRelease: Ubuntu 16.04
  Package: systemd 229-2ubuntu1 [modified: usr/share/dbus-1/system-services/org.freedesktop.systemd1.service]
  ProcVersionSignature: Ubuntu 4.4.0-13.29-generic 4.4.5
  Uname: Linux 4.4.0-13-generic x86_64
  ApportVersion: 2.20-0ubuntu3
  Architecture: amd64
  Date: Mon Mar 21 10:01:03 2016
  ExecutablePath: /lib/systemd/systemd-logind
  InstallationDate: Installed on 2015-06-13 (281 days ago)
  InstallationMedia: Ubuntu 15.04 "Vivid Vervet" - Release amd64 (20150422)
  MachineType: Dell Inc. XPS 13 9343
  ProcCmdline: /lib/systemd/systemd-logind
  ProcEnviron:
   LANG=en_US.UTF-8
   PATH=(custom, no user)
  ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-13-generic root=UUID=7bc4dcd2-0bd8-4e42-b8b7-9f1ed6b8a3e9 ro libata.force=noncq kaslr quiet splash vt.handoff=7
  Signal: 11
  SourcePackage: systemd
  StacktraceTop:
   ?? ()
   ?? ()
   ?? ()
   ?? ()
   ?? ()
  Title: systemd-logind crashed with SIGSEGV
  UpgradeStatus: Upgraded to xenial on 2016-01-12 (69 days ago)
  UserGroups:

  dmi.bios.date: 11/11/2015
  dmi.bios.vendor: Dell Inc.
  dmi.bios.version: A07
  dmi.board.name: 0310JH
  dmi.board.vendor: Dell Inc.
  dmi.board.version: A00
  dmi.chassis.type: 9
  dmi.chassis.vendor: Dell Inc.
  dmi.modalias: dmi:bvnDellInc.:bvrA07:bd11/11/2015:svnDellInc.:pnXPS139343:pvr:rvnDellInc.:rn0310JH:rvrA00:cvnDellInc.:ct9:cvr:
  dmi.product.name: XPS 13 9343
  dmi.sys.vendor: Dell Inc.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/systemd/+bug/1560072/+subscriptions