abrt 1.1.1 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/gvfsd-smb --spawner :1.7 /org/gtk/gvfs/exec_spaw/2 component: gvfs crash_function: raise executable: /usr/libexec/gvfsd-smb global_uuid: 352385538467978becb42dfdad00e283603f8f79 kernel: 2.6.33.5-112.fc13.x86_64 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)
Created attachment 418206 [details] File: backtrace
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Launch an already opened file in gnome-shell's "recent documents", after having logged in "automatically" (meaning that the login keyring isn't unlocked, as I did not type in a password). The share was not already mounted.
gnome-keyring-2.30.1-2.fc13.x86_64 libgnome-keyring-2.30.0-2.fc13.x86_64 gvfs-smb-1.6.2-1.fc13.x86_64
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Attempt to browse to a windows share. 2. 3. Comment ----- This happens with all windows shares (e.g. doesn't matter what domain/server/share user etc). I can reach the shares through dolphin, just not nautilus.
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- not sure what this error is about, found it in the list
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Accessed an SMB share with GVFS. Comment ----- I simply tried to mount an SMB drive over GVFS. I typed in my keyring password and got this crash. One thing to note is that I didn't need to remove my password from the backtrace as it appears the password field returned in the auth call was null.
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Just tried to connect to a network share. Works the second time I try.
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Tried to mount Via Nautilus smb-resource 2. 3.
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. It happens all the time when I open Rhythmbox 0.12.8 which has some music track links with urls smb://10.0.0.1/d$/xxx/ 2. After the error everything seems to work as it should and tracks a accessible 3.
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. connected to smb-server (ubuntu 10.04 LTS) 2. 3.
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce > ----- 1. Crash happened when Deja Dup attempted to automatically mount an smb share. 2. 3.
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. mount smb via nautilus 2. 3.
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.trying to access share on windows network. 2. not in domain, computer name in windows directory, permissions by network user and pass, diferent from computer user and pass. 3.after suspend in one networking and waking up in another one. Comment ----- after restarting, nautilus - it worked. no need to restart os.
Package: gvfs-smb-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Places->network->Windows Network->Windows Machine 2.Enter Username & Password 3.Connect Comment ----- Attempting to connect to SMB Share hosted on Ubuntu server 10.04.
*** Bug 603323 has been marked as a duplicate of this bug. ***
*** Bug 645809 has been marked as a duplicate of this bug. ***
*** Bug 646800 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 13 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 13. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as WONTFIX if it remains open with a Fedora 'version' of '13'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version prior to Fedora 13's end of life. Bug Reporter: Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 13 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora please change the 'version' of this bug to the applicable version. If you are unable to change the version, please add a comment here and someone will do it for you. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete. The process we are following is described here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping
Fedora 13 changed to end-of-life (EOL) status on 2011-06-25. Fedora 13 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. Thank you for reporting this bug and we are sorry it could not be fixed.