Bug 594952 - [abrt] crash in gvfs-1.6.1-3.fc13: __strcmp_ssse3: Process /usr/libexec/gvfsd-dav was killed by signal 11 (SIGSEGV)
Summary: [abrt] crash in gvfs-1.6.1-3.fc13: __strcmp_ssse3: Process /usr/libexec/gvfsd...
Status: CLOSED DUPLICATE of bug 531973
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 13
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:0a3b7a5839ca6e8499b24b8836b...
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-05-22 07:39 UTC by Marek Paśnikowski
Modified: 2015-03-03 22:48 UTC (History)
4 users (show)

(edit)
Clone Of:
(edit)
Last Closed: 2010-05-25 10:15:22 UTC


Attachments (Terms of Use)
File: backtrace (69.77 KB, text/plain)
2010-05-22 07:39 UTC, Marek Paśnikowski
no flags Details

Description Marek Paśnikowski 2010-05-22 07:39:49 UTC
abrt 1.1.0 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-dav --spawner :1.7 /org/gtk/gvfs/exec_spaw/5
comment: Tried to enter 'magister-laptop-0' network directory from 'magister-laptop-0'.
component: gvfs
crash_function: __strcmp_ssse3
executable: /usr/libexec/gvfsd-dav
global_uuid: 0a3b7a5839ca6e8499b24b8836b99bfb07a5d551
kernel: 2.6.33.4-95.fc13.x86_64
package: gvfs-1.6.1-3.fc13
rating: 4
reason: Process /usr/libexec/gvfsd-dav was killed by signal 11 (SIGSEGV)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1. Enter network directory
2. Enter the directory of computer you are working on.
3.

Comment 1 Marek Paśnikowski 2010-05-22 07:39:52 UTC
Created attachment 415833 [details]
File: backtrace

Comment 2 Karel Klíč 2010-05-25 10:15:22 UTC

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

Comment 3 Karel Klíč 2010-05-25 10:15: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 #531973.

Sorry for the inconvenience.


Note You need to log in before you can comment on or make changes to this bug.