systemd-logind crashed at shutdown segment of reboot process with signal 11/segv
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Sometimes when I reboot systemd-
{lsb_release -rd}
Description: Ubuntu Wily Werewolf (development branch)
Release: 15.10
{apt-cache policy systemd}
systemd:
Installed: 225-1ubuntu4
Candidate: 225-1ubuntu4
Version table:
*** 225-1ubuntu4 0
500 http://
100 /var/lib/
ProblemType: Crash
DistroRelease: Ubuntu 15.10
Package: systemd 225-1ubuntu4
ProcVersionSign
Uname: Linux 3.19.0-28-generic i686
NonfreeKernelMo
ApportVersion: 2.19-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Tue Sep 29 12:13:23 2015
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2015-09-16 (13 days ago)
InstallationMedia: Lubuntu 15.04 "Vivid Vervet" - Release i386 (20150422)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 046d:c51b Logitech, Inc. V220 Cordless Optical Mouse for Notebooks
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Hewlett-Packard Presario V6000 (RG298UA#ABA)
ProcCmdline: /lib/systemd/
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis: Skipped: missing required field "Disassembly"
Signal: 11
SourcePackage: systemd
UdevLog: Error: [Errno 2] No such file or directory: '/var/log/udev'
UpgradeStatus: Upgraded to wily on 2015-09-16 (13 days ago)
UserGroups:
dmi.bios.date: 10/25/2006
dmi.bios.vendor: Hewlett-Packard
dmi.bios.version: F.1A
dmi.board.name: 30B7
dmi.board.vendor: Quanta
dmi.board.version: 65.21
dmi.chassis.type: 10
dmi.chassis.vendor: Quanta
dmi.chassis.
dmi.modalias: dmi:bvnHewlett-
dmi.product.name: Presario V6000 (RG298UA#ABA)
dmi.product.
dmi.sys.vendor: Hewlett-Packard
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 #1499863, 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.