Bug 613226 - [abrt] crash in gvfs-smb-1.6.2-1.fc13: raise: Process /usr/libexec/gvfsd-smb was killed by signal 6 (SIGABRT)
Summary: [abrt] crash in gvfs-smb-1.6.2-1.fc13: raise: Process /usr/libexec/gvfsd-smb ...
Keywords:
Status: CLOSED DUPLICATE of bug 600929
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 13
Hardware: i686
OS: Linux
low
medium
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:001192745795dcb76e12e4a0071...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-07-10 05:44 UTC by Arnaud Bergmann
Modified: 2015-03-03 22:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2010-11-09 13:45:38 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (12.85 KB, text/plain)
2010-07-10 05:44 UTC, Arnaud Bergmann
no flags Details

Description Arnaud Bergmann 2010-07-10 05:44:25 UTC
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-smb --spawner :1.7 /org/gtk/gvfs/exec_spaw/4
comment: I tried to connect to a folder on a windows server and it crashes.
component: gvfs
crash_function: raise
executable: /usr/libexec/gvfsd-smb
global_uuid: 001192745795dcb76e12e4a0071bd232f5bbe3b6
kernel: 2.6.33.5-124.fc13.i686
package: gvfs-smb-1.6.2-1.fc13
rating: 4
reason: Process /usr/libexec/gvfsd-smb was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)

How to reproduce
-----
1.Connect to a server
2.choosing "windows share"
3.putting date

Comment 1 Arnaud Bergmann 2010-07-10 05:44:28 UTC
Created attachment 430828 [details]
File: backtrace

Comment 2 Karel Klíč 2010-11-09 13:45:38 UTC

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

Comment 3 Karel Klíč 2010-11-09 13:45:38 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 #600929.

Sorry for the inconvenience.


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