[systemd 230-2] systemd-resolved crashed with SIGSEGV
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned |
Bug Description
After upgrading systemd to 230-2, and done a cold reboot, i've tested that command:
systemd-resolve www.facebook.com
www.facebook.com: resolve call failed: DNSSEC validation failed: failed-auxiliary
and got that crash.
(Previous related issue: lp:1586991 )
ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 230-2
ProcVersionSign
Uname: Linux 4.4.0-23-generic x86_64
NonfreeKernelMo
ApportVersion: 2.20.1-0ubuntu4
Architecture: amd64
Date: Wed Jun 1 08:52:01 2016
ExecutablePath: /lib/systemd/
Lsusb:
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
Bus 003 Device 002: ID 046d:c062 Logitech, Inc. M-UAS144 [LS1 Laser Mouse]
Bus 003 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
Bus 002 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: ASUSTEK COMPUTER INC P5W DH Deluxe
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] /etc/systemd/
[EXTENDED] /lib/systemd/
3 overridden configuration files found.
Title: systemd-resolved crashed with SIGSEGV
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 07/22/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3002
dmi.board.
dmi.board.name: P5W DH Deluxe
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P5W DH Deluxe
dmi.product.
dmi.sys.vendor: ASUSTEK COMPUTER INC
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.