Bug 553312 - [abrt] crash in gvfs-1.4.3-1.fc12
Summary: [abrt] crash in gvfs-1.4.3-1.fc12
Keywords:
Status: CLOSED DUPLICATE of bug 545788
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 12
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:fd39e4dcd03545b8b504af69372...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-01-07 15:47 UTC by P. A. López-Valencia
Modified: 2015-03-03 22:43 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-02-24 17:24:22 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (14.29 KB, text/plain)
2010-01-07 15:47 UTC, P. A. López-Valencia 		no flags Details
View All

Description P. A. López-Valencia 2010-01-07 15:47:34 UTC 
abrt 1.0.3 detected a crash.

How to reproduce
-----
1. Try to connect to a WebDAV share on the network, created with gnome-user-share
2. A message pops up: "Unable to mount location: DBus error org.freedesktop.DBus.Error.NoReply: Message did not receive a reply (timeout by message bus)"
3. gvfs-dav chrashes and burns.

Comment: See above.
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-dav --spawner :1.7 /org/gtk/gvfs/exec_spaw/12
component: gvfs
executable: /usr/libexec/gvfsd-dav
kernel: 2.6.31.9-174.fc12.i686.PAE
package: gvfs-1.4.3-1.fc12
rating: 4
reason: Process was terminated by signal 11 (Segmentation fault)
Comment 1 P. A. López-Valencia 2010-01-07 15:47:48 UTC 
Created attachment 382269 [details]
File: backtrace
Comment 2 Karel Klíč 2010-02-24 17:24:22 UTC 

*** This bug has been marked as a duplicate of bug 545788 ***
Comment 3 Karel Klíč 2010-02-24 17:24:22 UTC 
This bug appears to have been filled using a buggy version of ABRT, because
it contains a backtrace which is a duplicate of backtrace from bug #545788.

Sorry for the inconvenience.
Comment 4 P. A. López-Valencia 2010-02-24 17:33:30 UTC 
Oh well. They haven't finished inventing ABRT yet.
Note You need to log in before you can comment on or make changes to this bug.