Bug 620999 - [abrt] crash in gvfs-smb-1.6.2-1.fc13: raise: Process /usr/libexec/gvfsd-smb-browse was killed by signal 6 (SIGABRT)
[abrt] crash in gvfs-smb-1.6.2-1.fc13: raise: Process /usr/libexec/gvfsd-smb-...
Status: CLOSED DUPLICATE of bug 607713
Product: Fedora
Classification: Fedora
Component: gvfs (Show other bugs)
13
x86_64 Linux
low Severity medium
: ---
: ---
Assigned To: Tomáš Bžatek
Fedora Extras Quality Assurance
abrt_hash:8d6d319a0dae2c6a2a332aa7934...
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2010-08-03 18:39 EDT by Gianluca Varisco
Modified: 2015-03-03 17:51 EST (History)
4 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2010-11-09 11:56:24 EST
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
File: backtrace (12.11 KB, text/plain)
2010-08-03 18:39 EDT, Gianluca Varisco
no flags Details

  None (edit)
Description Gianluca Varisco 2010-08-03 18:39:55 EDT
abrt 1.1.1 detected a crash.

architecture: x86_64
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-smb-browse --spawner :1.6 /org/gtk/gvfs/exec_spaw/7
component: gvfs
crash_function: raise
executable: /usr/libexec/gvfsd-smb-browse
global_uuid: 8d6d319a0dae2c6a2a332aa793405cc26681187b
kernel: 2.6.33.6-147.fc13.x86_64
package: gvfs-smb-1.6.2-1.fc13
rating: 4
reason: Process /usr/libexec/gvfsd-smb-browse was killed by signal 6 (SIGABRT)
release: Fedora release 13 (Goddard)
Comment 1 Gianluca Varisco 2010-08-03 18:39:58 EDT
Created attachment 436399 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-09 11:56:24 EST

*** This bug has been marked as a duplicate of bug 607713 ***
Comment 3 Karel Klíč 2010-11-09 11:56:24 EST
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 #607713.

Sorry for the inconvenience.

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