systemd-resolved crashed with SIGSEGV in sd_event_source_unref()

Bug #1625437 reported by Walter Garcia-Fontes
26
This bug affects 4 people
Affects Status Importance Assigned to Milestone
systemd (Ubuntu)
Won't Fix
Medium
Unassigned

Bug Description

I'm getting this crash when starting the computer.

ProblemType: Crash
DistroRelease: Ubuntu 16.10
Package: systemd 231-6
ProcVersionSignature: Ubuntu 4.4.0-9136.55-generic 4.4.16
Uname: Linux 4.4.0-9136-generic x86_64
NonfreeKernelModules: nvidia_uvm nvidia_drm nvidia_modeset nvidia
ApportVersion: 2.20.3-0ubuntu7
Architecture: amd64
Date: Sat Sep 17 20:21:42 2016
ExecutablePath: /lib/systemd/systemd-resolved
InstallationDate: Installed on 2013-11-28 (1026 days ago)
InstallationMedia: Ubuntu 13.10 "Saucy Salamander" - Release amd64 (20131016.1)
MachineType: Dell Inc. Latitude E6530
ProcCmdline: /lib/systemd/systemd-resolved
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-4.4.0-9136-generic root=UUID=409b2104-0062-403c-8b6b-f07948051f69 ro quiet splash vt.handoff=7
Signal: 11
SourcePackage: systemd
StacktraceTop:
 sd_event_source_unref () from /lib/systemd/libsystemd-shared-231.so
 ?? ()
 ?? ()
 ?? ()
 ?? () from /lib/systemd/libsystemd-shared-231.so
Title: systemd-resolved crashed with SIGSEGV in sd_event_source_unref()
UpgradeStatus: Upgraded to yakkety on 2016-08-31 (19 days ago)
UserGroups:

dmi.bios.date: 08/27/2013
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A13
dmi.board.name: 07Y85M
dmi.board.vendor: Dell Inc.
dmi.board.version: A01
dmi.chassis.type: 9
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.:bvrA13:bd08/27/2013:svnDellInc.:pnLatitudeE6530:pvr01:rvnDellInc.:rn07Y85M:rvrA01:cvnDellInc.:ct9:cvr:
dmi.product.name: Latitude E6530
dmi.product.version: 01
dmi.sys.vendor: Dell Inc.

Revision history for this message
Walter Garcia-Fontes (walter-garcia) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 sd_event_source_unref (s=0x55f78f9253b0 <on_query_timeout.lto_priv.104>) at ../src/libsystemd/sd-event/sd-event.c:1385
 dns_query_stop.lto_priv.112 (q=0x55f7915fdc70) at ../src/resolve/resolved-dns-query.c:358
 dns_query_complete.lto_priv.107 (q=0x55f7915fdc70, state=<optimized out>) at ../src/resolve/resolved-dns-query.c:553
 on_query_timeout.lto_priv.104 (s=<optimized out>, usec=<optimized out>, userdata=<optimized out>) at ../src/resolve/resolved-dns-query.c:564
 source_dispatch.lto_priv.92 (s=0x55f791606330) at ../src/libsystemd/sd-event/sd-event.c:2275

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : StacktraceSource.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in systemd (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
information type: Private → Public
Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in systemd (Ubuntu):
status: New → Confirmed
Revision history for this message
Steve Langasek (vorlon) wrote :

Thank you for reporting this issue and helping to improve Ubuntu.

This bug was reported against the version of systemd in Ubuntu 16.10, which has reached End Of Life. As such, we will not be fixing bugs in this version of the package. If this problem is reproducible on later supported versions of Ubuntu, please open a new bug (preferably with a fresh backtrace and crashdump) against that version.

Changed in systemd (Ubuntu):
status: Confirmed → Won't Fix
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.