gvfsd-dnssd crashed with signal 7 in avahi_service_resolver_event()

Bug #647236 reported by A. Cooper
154
This bug affects 34 people
Affects Status Importance Assigned to Milestone
gvfs
Fix Released
Critical
gvfs (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: gvfs

Apport keeps reporting major kernel failure???? then crashes when I try to close the report

ProblemType: Crash
DistroRelease: Ubuntu 10.10
Package: gvfs-backends 1.6.3-0ubuntu2
ProcVersionSignature: Ubuntu 2.6.35-22.33-generic 2.6.35.4
Uname: Linux 2.6.35-22-generic x86_64
Architecture: amd64
Date: Fri Sep 24 08:56:11 2010
ExecutablePath: /usr/lib/gvfs/gvfsd-dnssd
InstallationMedia: Ubuntu 10.04 LTS "Lucid Lynx" - Release amd64 (20100429)
ProcCmdline: /usr/lib/gvfs/gvfsd-dnssd --spawner :1.11 /org/gtk/gvfs/exec_spaw/15
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_AU:en_GB:en
 LANG=en_AU.utf8
Signal: 7
SourcePackage: gvfs
StacktraceTop:
 ?? ()
 ?? ()
 avahi_service_resolver_event () from /usr/lib/libavahi-client.so.3
 ?? () from /usr/lib/libavahi-client.so.3
 dbus_connection_dispausernameh () from /lib/libdbus-1.so.3
Title: gvfsd-dnssd crashed with signal 7 in avahi_service_resolver_event()
UserGroups: adm admin cdrom dialout lpadmin mythtv plugdev sambashare

Revision history for this message
A. Cooper (aandacooper) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 lookup_link_file_by_name_and_type (backend=0x13ea820,
 resolve_callback (r=<value optimized out>,
 avahi_service_resolver_event (
 filter_func (bus=<value optimized out>,
 dbus_connection_dispatch (connection=0x13ed170)

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in gvfs (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
Revision history for this message
Pedro Villavicencio (pedro) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at:
 https://bugzilla.gnome.org/show_bug.cgi?id=631023

visibility: private → public
Changed in gvfs (Ubuntu):
status: New → Triaged
Changed in gvfs:
importance: Unknown → Critical
status: Unknown → New
tags: added: precise
Revision history for this message
Vladimir Scherbaev (zemik) wrote :

I have this bug on 12.10

Revision history for this message
Simon Baconnais (smon-deactivatedaccount) wrote :

I have this bug on 13.04

dino99 (9d9)
tags: added: raring
removed: maverick
Revision history for this message
Juan Manuel Pérez Ramos (jmperez1969) wrote :

Hi

Changed in gvfs:
status: New → Confirmed
Changed in gvfs:
status: Confirmed → Fix Released
Changed in gvfs (Ubuntu):
status: Triaged → Fix Committed
Changed in gvfs:
status: Fix Released → Confirmed
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

This bug is also fixed in 1.28.3. An SRU request for Xenial is here Bug #1579505.

Changed in gvfs (Ubuntu):
status: Fix Committed → Fix Released
Revision history for this message
Amr Ibrahim (amribrahim1987) wrote :

Oops, upstream reopened this bug and they attached new patches in the upstream bug report which are waiting for testing.

Changed in gvfs:
status: Confirmed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

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