Bug 718482 - [abrt] gvfs-smb-1.6.4-2.fc14: g_assertion_message: Process /usr/libexec/gvfsd-smb was killed by signal 6 (SIGABRT)
Summary: [abrt] gvfs-smb-1.6.4-2.fc14: g_assertion_message: Process /usr/libexec/gvfsd...
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:d221aa001a94b2205c0af60329e...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-07-03 11:36 UTC by hosso_hn097
Modified: 2015-03-03 23:01 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-03-30 12:08:37 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
File: backtrace (16.86 KB, text/plain)
2011-07-03 11:36 UTC, hosso_hn097
no flags Details

Description hosso_hn097 2011-07-03 11:36:38 UTC
abrt version: 1.1.13
architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-smb --spawner :1.10 /org/gtk/gvfs/exec_spaw/2
component: gvfs
crash_function: g_assertion_message
executable: /usr/libexec/gvfsd-smb
kernel: 2.6.35.6-45.fc14.i686
package: gvfs-smb-1.6.4-2.fc14
rating: 4
reason: Process /usr/libexec/gvfsd-smb was killed by signal 6 (SIGABRT)
release: Fedora release 14 (Laughlin)
time: 1309683106
uid: 500

How to reproduce
-----
1.Launch nautilus.
2.Choose Samba server location from Bookmark menu (URL like smb://uuuuuuuu@ssssss/uuuuuu)
3.ABRT crash dialog is displayed.

Comment 1 hosso_hn097 2011-07-03 11:36:41 UTC
Created attachment 511045 [details]
File: backtrace

Comment 2 abrt-bot 2012-03-30 12:08:37 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 #679940, bug #689254, 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.