Bug 605216 - [abrt] crash in gvfs-smb-1.6.2-1.fc13: raise: Process /usr/libexec/gvfsd-smb-browse 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 604631
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:347584be7eddd9970cd8cbe4a50...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2010-06-17 12:57 UTC by Scott M. Sanders
Modified: 2015-03-03 22:49 UTC (History)
5 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2010-11-08 18:54:19 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (10.03 KB, text/plain)
2010-06-17 12:57 UTC, Scott M. Sanders 		no flags Details
View All

Description Scott M. Sanders 2010-06-17 12:57:56 UTC 
abrt 1.1.1 detected a crash.

architecture: i686
Attached file: backtrace
cmdline: /usr/libexec/gvfsd-smb-browse --spawner :1.7 /org/gtk/gvfs/exec_spaw/2
component: gvfs
crash_function: raise
executable: /usr/libexec/gvfsd-smb-browse
global_uuid: 347584be7eddd9970cd8cbe4a508eacd23e4708a
kernel: 2.6.33.5-124.fc13.i686
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)

How to reproduce
-----
1. Click Places > Connect to Server... 
2. Pick service type Windows Share, and type just a local server name in all caps with no extensions. 
3. Enter username and password.
Comment 1 Scott M. Sanders 2010-06-17 12:57:59 UTC 
Created attachment 424802 [details]
File: backtrace
Comment 2 Karel Klíč 2010-11-08 18:54:19 UTC 

*** This bug has been marked as a duplicate of bug 604631 ***
Comment 3 Karel Klíč 2010-11-08 18:54:19 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 #604631.

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