gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()

Bug #1548970 reported by Randy
154
This bug affects 30 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
High
Unassigned

Bug Description

Running:

Description: Ubuntu Xenial Xerus (development branch)
Release: 16.04

gvfs:
  Installed: 1.27.90-1ubuntu1
  Candidate: 1.27.90-1ubuntu1
  Version table:
 *** 1.27.90-1ubuntu1 500
        500 http://us.archive.ubuntu.com/ubuntu xenial/main amd64 Packages
        100 /var/lib/dpkg/status

Didn't expect anything happened shortly after booting & logging in.

I got this pop-up.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gvfs-backends 1.27.90-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-6.21-generic 4.4.1
Uname: Linux 4.4.0-6-generic x86_64
ApportVersion: 2.20-0ubuntu3
Architecture: amd64
CurrentDesktop: GNOME
Date: Tue Feb 23 14:48:35 2016
ExecutablePath: /usr/lib/gvfs/gvfsd-dnssd
InstallationDate: Installed on 2014-10-30 (481 days ago)
InstallationMedia: Ubuntu-GNOME 14.10 "Utopic Unicorn" - Release amd64 (20141022.1)
ProcCmdline: /usr/lib/gvfs/gvfsd-dnssd --spawner :1.14 /org/gtk/gvfs/exec_spaw/10
ProcEnviron:
 SHELL=/bin/bash
 XDG_RUNTIME_DIR=<set>
 PATH=(custom, user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f8712280d9a <__strcmp_sse2_unaligned+26>: movdqu (%rdi),%xmm1
 PC (0x7f8712280d9a) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%xmm1" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? ()
 avahi_service_resolver_event () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 ?? () from /usr/lib/x86_64-linux-gnu/libavahi-client.so.3
 dbus_connection_dispatch () from /lib/x86_64-linux-gnu/libdbus-1.so.3
Title: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()
UpgradeStatus: Upgraded to xenial on 2016-02-15 (8 days ago)
UserGroups: adm cdrom dip libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Randy (randy-duran) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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 #927340, 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.

information type: Private → Public
tags: removed: need-amd64-retrace
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in gvfs (Ubuntu):
status: New → Confirmed
Revision history for this message
phoenix (shamilek) wrote :

ubuntu:~$ lsb_release -a
No LSB modules are available.
Distributor ID: Ubuntu
Description: Ubuntu 16.04.1 LTS
Release: 16.04
Codename: xenial

Changed in gvfs (Ubuntu):
importance: Undecided → High
Revision history for this message
Kathryn Morgan (katamo) wrote :

Bug #927340 is either private or non-existant. The link is broken and so this is not a duplicate bug. I have recreated the symptom on 3 different Dell Precision Mobile Workstation 5510's & a 5520 running 16.04.1 with all updates.

Revision history for this message
libcha (libcha) wrote :

Same message appeared in yakkety.

Revision history for this message
Leon Rozanov (schekn) wrote :

Suddenly happened after an update and reboot.
Ubuntu 16.04.3 LTS

Revision history for this message
David Farrell (dfarrell16) wrote :

On 16.04.5 Dell Inspiron, seems to be related to Wifi on boot. If I disable Wifi and reboot, does not seem to happen. If I enable WiFi after boot, still does not happen. WiFi is Intel 3165.

Revision history for this message
Rakshit Kothari (rakshit-kothari) wrote :

Hello! My first comment here on this forum. This bug consistently occurs everytime my system is rebooted. Since I have absolutely no idea what goes on behind the scenes, I'd like to mention that I use NVIDIA drivers. Hoping to find a solution.

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.