systemd-resolved crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Probably a duplicate of another bug I filed (#1587766), but filing it anyway because I thought there might be a reason why Apport loaded twice instead of once (please tell me why Apport does this, if this is a duplicate!)
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 230-1git1
ProcVersionSign
Uname: Linux 4.4.0-23-generic x86_64
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
CrashCounter: 1
Date: Wed Jun 1 09:47:53 2016
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2016-04-26 (35 days ago)
InstallationMedia: Ubuntu 16.10 "Yakkety Yak" - Alpha amd64 (20160426)
Lsusb:
Bus 001 Device 004: ID 058f:6362 Alcor Micro Corp. Flash Card Reader/Writer
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 002 Device 003: ID 17ef:604d Lenovo
Bus 002 Device 002: ID 04d9:1603 Holtek Semiconductor, Inc. Keyboard
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: Packard Bell imedia S1710
ProcCmdline: /lib/systemd/
ProcEnviron:
LANG=en_GB.UTF-8
LANGUAGE=en_GB:en
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 11
SourcePackage: systemd
StacktraceTop:
?? ()
?? ()
?? ()
?? ()
?? ()
SystemdDelta:
[EXTENDED] /lib/systemd/
[EXTENDED] /lib/systemd/
[EXTENDED] /etc/systemd/
3 overridden configuration files found.
Title: systemd-resolved crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 06/06/2009
dmi.bios.vendor: AMI
dmi.bios.version: P01-A3
dmi.board.
dmi.board.name: MCP73T-AD
dmi.board.vendor: Packard Bell
dmi.chassis.type: 3
dmi.chassis.vendor: Packard Bell
dmi.modalias: dmi:bvnAMI:
dmi.product.name: imedia S1710
dmi.sys.vendor: Packard Bell
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 #1586991, 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.