abrt 1.0.9 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/gvfsd-smb --spawner :1.1 /org/gtk/gvfs/exec_spaw/3 component: gvfs executable: /usr/libexec/gvfsd-smb global_uuid: 811b01fcf27ae371174961ee70333c667566178a kernel: 2.6.33.1-24.fc13.x86_64 package: gvfs-smb-1.6.0-1.fc13 rating: 4 reason: Process /usr/libexec/gvfsd-smb was killed by signal 11 (SIGSEGV) release: Fedora release 13 (Goddard) How to reproduce ----- 1. Push files to Samba server 2. This crash occours 3.
Created attachment 406943 [details] File: backtrace
Package: gvfs-smb-1.6.0-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.connect to samba share 2. 3. Comment ----- Just try to connect to a samba share.
Package: gvfs-smb-1.6.0-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Just try to navigate samba share 2. 3.
Looks like a duplicate of 573438 (and happens here too).
Package: gvfs-smb-1.6.0-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- open samba resource
Package: gvfs-smb-1.6.0-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open nautilus 2. Ctrl + L 3. Type a smb:// address, I tried with a local samba server named ferenginar: smb://ferenginar 4. It shows shared folders in 'ferenginar' server and I double click in one of the folders ('public') to mount it Comment ----- I tried to mount a samba folder from a local server from nautilus by double clicking on it. The folder doesn't need password, it's public. This used to work with Fedora 12 and the same samba server.
*** Bug 573093 has been marked as a duplicate of this bug. ***
*** Bug 586626 has been marked as a duplicate of this bug. ***
Works here with F15, is this still an issue for anyone?
(In reply to comment #9) > Works here with F15, is this still an issue for anyone? Works here F14 and gvfs-smb-1.6.6-1.fc14.x86_64
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.