systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
systemd (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I ran the Software Center, and this bug came up.
Ubuntu GNOME 17.04 beta 2
GNOME 3.24.0
ProblemType: Crash
DistroRelease: Ubuntu 17.04
Package: systemd 232-19
ProcVersionSign
Uname: Linux 4.10.0-15-generic x86_64
ApportVersion: 2.20.4-0ubuntu3
Architecture: amd64
CrashCounter: 1
Date: Fri Apr 7 19:39:42 2017
ExecutablePath: /lib/systemd/
InstallationDate: Installed on 2017-04-07 (0 days ago)
InstallationMedia: Ubuntu-GNOME 17.04 "Zesty Zapus" - Beta amd64 (20170321)
Lsusb:
Bus 002 Device 001: ID 1d6b:0003 Linux Foundation 3.0 root hub
Bus 001 Device 004: ID 8087:0a2b Intel Corp.
Bus 001 Device 003: ID 04f2:b57e Chicony Electronics Co., Ltd
Bus 001 Device 002: ID 046d:c52b Logitech, Inc. Unifying Receiver
Bus 001 Device 001: ID 1d6b:0002 Linux Foundation 2.0 root hub
MachineType: LENOVO 80SA
ProcCmdline: /lib/systemd/
ProcEnviron:
LANG=en_US.UTF-8
PATH=(custom, no user)
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 11
SourcePackage: systemd
StacktraceTop:
?? ()
?? ()
?? () from /lib/systemd/
sd_event_dispatch () from /lib/systemd/
sd_event_run () from /lib/systemd/
Title: systemd-resolved crashed with SIGSEGV in sd_event_dispatch()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups:
dmi.bios.date: 05/17/2016
dmi.bios.vendor: LENOVO
dmi.bios.version: 0VCN18WW(V1.03)
dmi.board.
dmi.board.name: Lenovo ideapad F
dmi.board.vendor: LENOVO
dmi.board.version: SDK0J40700 WIN
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 80SA
dmi.product.
dmi.sys.vendor: LENOVO
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 #1621396, 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.