Error was made in a background: gvfsd-dnssd crashed with SIGSEGV in avahi_service_resolver_event()

Bug #1569200 reported by ws
This bug report is a duplicate of:  Edit Remove
50
This bug affects 10 people
Affects Status Importance Assigned to Milestone
gvfs (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

-

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: gvfs-backends 1.27.92-1ubuntu1
ProcVersionSignature: Ubuntu 4.4.0-18.34-generic 4.4.6
Uname: Linux 4.4.0-18-generic x86_64
ApportVersion: 2.20.1-0ubuntu1
Architecture: amd64
CrashCounter: 1
CurrentDesktop: Unity
Date: Tue Apr 12 09:15:44 2016
ExecutablePath: /usr/lib/gvfs/gvfsd-dnssd
InstallationDate: Installed on 2016-04-02 (9 days ago)
InstallationMedia: Ubuntu 16.04 LTS "Xenial Xerus" - Beta amd64 (20160323)
ProcCmdline: /usr/lib/gvfs/gvfsd-dnssd --spawner :1.4 /org/gtk/gvfs/exec_spaw/5
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=pl
 PATH=(custom, no user)
 LANG=pl_PL.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f0e6b0e929a <__strcmp_sse2_unaligned+26>: movdqu (%rdi),%xmm1
 PC (0x7f0e6b0e929a) 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: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
ws (szczypka-wojciech) 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
astromo (slyryder) wrote :

https://bugs.launchpad.net/ubuntu/+source/gvfs/+bug/1569200/comments/2
advises that this bug is a duplicate of this bug report:
   https://bugs.launchpad.net/bugs/927340

However, the link to bug #927340 is dead, so it's not really a duplicate is it?

The bug is affecting my installation as well. Any update on a fix. The bug post dates to back 4 months, so I would have thought that there was something further to report by now.

Revision history for this message
Leu (leuofiridia) wrote :

Bug affecting my installation after upgrading from 14.04. I've noticed that before the SIGSEGV, the process tops at 100% of one of my core's usage.

Revision history for this message
Dfarce (i8b4u) wrote :

I only got this bug after upgrading from 15.10 to 16.04.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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