systemd-logind crash at login or on sudo su (not sure which)
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
What I expected to happen. No crashing process when I log in.
I had previously shut down the virtual machine just fine so this was from a fresh power on. I logged into the system and got the attached crash.
This is likely unrelated, but I had just logged in, opened a terminal (control-alt-t) and typed "sudo su" and had not entered my password yet, when the crash screen showed up.
I hope this can help you trouble shoot the problem as I have seen similar crash-after login problems with Lubuntu before. In all cases everything seems to run fine after the task crashed.
lsb_release -rd
Ubuntu Wily Werewolf (development branch)
Release: 15.10
Note: 2015-09-19 version
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 4.2.0-10-generic x86_64
ApportVersion: 2.18.1-0ubuntu1
Architecture: amd64
Date: Sat Sep 19 14:56:41 2015
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2015-09-19 (0 days ago)
InstallationMedia: Lubuntu 15.10 "Wily Werewolf" - Alpha amd64 (20150919)
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 002: ID 80ee:0021 VirtualBox USB Tablet
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcCmdline: /lib/systemd/
ProcEnviron:
LANG=en_CA.UTF-8
LANGUAGE=en_CA:en
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: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.board.name: VirtualBox
dmi.board.vendor: Oracle Corporation
dmi.board.version: 1.2
dmi.chassis.type: 1
dmi.chassis.vendor: Oracle Corporation
dmi.modalias: dmi:bvninnotekG
dmi.product.name: VirtualBox
dmi.product.
dmi.sys.vendor: innotek GmbH
This crash has the same stack trace characteristics as bug #1495178. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.