Bug 679940 - [abrt] gvfs-smb-1.6.6-1.fc14: on_pending_call_notify: Process /usr/libexec/gvfsd-smb-browse was killed by signal 6 (SIGABRT)
Summary: [abrt] gvfs-smb-1.6.6-1.fc14: on_pending_call_notify: Process /usr/libexec/gv...
Keywords:
Status: CLOSED DUPLICATE of bug 743874
Alias: None
Product: Fedora
Classification: Fedora
Component: gvfs
Version: 14
Hardware: i686
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tomáš Bžatek
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:af4b881abe2e3a2bc409f661438...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-02-23 21:54 UTC by antonio montagnani
Modified: 2015-03-03 22:58 UTC (History)
4 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-03-30 12:08:49 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (21.44 KB, text/plain)
2011-02-23 21:54 UTC, antonio montagnani 		no flags Details
View All

Description antonio montagnani 2011-02-23 21:54:18 UTC 
abrt version: 1.1.17
architecture: i686
Attached file: backtrace, 21954 bytes
cmdline: /usr/libexec/gvfsd-smb-browse --spawner :1.10 /org/gtk/gvfs/exec_spaw/3
component: gvfs
Attached file: coredump, 19132416 bytes
crash_function: on_pending_call_notify
executable: /usr/libexec/gvfsd-smb-browse
kernel: 2.6.35.11-83.fc14.i686.PAE
package: gvfs-smb-1.6.6-1.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-smb-browse was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1298497182
uid: 500

How to reproduce
-----
1.surfing a samba share
2.
3.
Comment 1 antonio montagnani 2011-02-23 21:54:22 UTC 
Created attachment 480585 [details]
File: backtrace
Comment 2 abrt-bot 2012-03-30 12:08:49 UTC 
Backtrace analysis found this bug to be similar to bug #743874, closing as duplicate.

Bugs which were found to be similar to this bug: bug #663255, bug #668753, bug #689254, bug #718482, bug #743874

This comment is automatically generated.

*** This bug has been marked as a duplicate of bug 743874 ***
Note You need to log in before you can comment on or make changes to this bug.