Bug 537213

Summary: [abrt] crash detected in gvfs-1.4.1-3.fc12
Product: [Fedora] Fedora Reporter: Michael Monreal <michael.monreal>
Component: gvfsAssignee: Tomáš Bžatek <tbzatek>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: medium Docs Contact:
Priority: low    
Version: 12CC: alexl, bnocera, lpoetter, mclasen, tbzatek, thomas_sors, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Linux   
Whiteboard: abrt_hash:7e464f1eb0ddb0c39a5a00afc95f47bbc4b8dea8
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2009-11-13 09:30:30 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
File: backtrace none

Description Michael Monreal 2009-11-12 20:11:04 UTC
abrt detected a crash.

How to reproduce
-----
1. try to connect to a gnome-user-share'd share a number of times
2. about every 3rd time, gvfs will crash like this

Comment
-----
The gnome-user-share "server" I want to access is running on Fedora 11 in case it matters.

Is there a way to improve the backtrace? I have installed about every debuginfo package I could think of...

Attached file: backtrace
cmdline: /usr/libexec/gvfsd-dav --spawner :1.7 /org/gtk/gvfs/exec_spaw/14
component: gvfs
executable: /usr/libexec/gvfsd-dav
kernel: 2.6.31.5-127.fc12.i686.PAE
package: gvfs-1.4.1-3.fc12
rating: 4
reason: Process was terminated by signal 11

Comment 1 Michael Monreal 2009-11-12 20:11:08 UTC
Created attachment 369309 [details]
File: backtrace

Comment 2 Matthias Clasen 2009-11-13 01:28:09 UTC
Looks like the segfault is actually in avahi_service_resolver_event

Comment 3 Michael Monreal 2009-11-13 07:34:57 UTC
(In reply to comment #2)
> Looks like the segfault is actually in avahi_service_resolver_event  

Right... offtopic: I have noticed ABRT guessing wrong bug modules a number of times now, is there a way to improve that? Manually changing the module is not supported either...

Comment 4 Tomáš Bžatek 2009-11-13 09:30:30 UTC
No, it's a gvfs bug.

*** This bug has been marked as a duplicate of bug 500655 ***