Fedora Account System
Red Hat Associate
Red Hat Customer
abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: /usr/libexec/gvfsd-smb --spawner :1.9 /org/gtk/gvfs/exec_spaw/2 component: gvfs crash_function: gkr_operation_block_and_unref executable: /usr/libexec/gvfsd-smb kernel: 2.6.35.6-48.fc14.i686 package: gvfs-smb-1.6.6-1.fc14 rating: 4 reason: Process /usr/libexec/gvfsd-smb was killed by signal 6 (SIGABRT) release: Fedora release 14 (Laughlin) How to reproduce: Mount a smb filesystem. time: 1290664533 uid: 500
Created attachment 462826 [details] File: backtrace
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. i only click on a bookmark in nautilus for my SMB share 2. on a second click, my smb was shown/mount in nautilus... 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. i click on my smb-bookmark in nautilus 2. abrt .... 3. on a second click (smb-bookmark) nautilus open my netshare....
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. updated SE policies 2. logout recommended 3. crashed
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. put deja-dup in automatic mode, the backup storage is a samba volume 2. wake up the computer from sleep 3. deja-dup tries to start the backup, it fails because the smb storage is not yet available 4. gvfsd-smb crashes Comment ----- I see two problems here: the first, gvfsd-smb should not crash :). The other, deja-dup should wait for the network to be available, before starting the backup.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Trying to re-open closed nautilus window on Samba file sahre after restart
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.attemped to mount samba share with win 7 2 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Try to open an SMB mount from nautilus using a bookmark Comment ----- Seemed to be working fine until recently.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Opening share through nautilus. Restart fixes the problem temporarily but it comes back again.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Opening file share in Bookmarks folder in nautilus
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Started my laptop 2. Restarted my laptop 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I dont know 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Trying to open a shared folder via openvpn 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Open "Places->Connect to Server" 2.Select "windows share" 3.Fill in server and share and username and click connect
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- Opening SMB bookmark.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. no clue 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Browsed to Netgear Stora and Opened a Public folder 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. initiated update 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Nautilus tried to access a samba share on my local network when it has crashed 2. 3. Comment ----- I know, that the hardware (Western Digital NetCenter 250) which hosts the samba server have a peculiar implementation of samba. However after a few tries, even nautilus is capable for using it, and this reported crash happens at only the first attempt to access the drive. After a few tries, it just starts to work.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Updated 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. Don't have a clue
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. 2. 3. .
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. NS/NC 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. open nautilus 2. click on my bookmark to samba share 3. abrt cames up 4. after a second click on my SMB bookmark in nautilus - the share was shown in nautilus Comment ----- i have a littlel dejavue ?!
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Open Nautilus 2.32.2.1 2. Left Click on Bookmarked SMB share 3. FAIL!
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. dejadup will starts his backupjob 2. no smb 3. Comment ----- its saturday on sunday night in germany. the nazis have time 4 blitzkrieg
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.tried to access my drive through work vpn 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I click on the gnome menu places 2. Select a folder on a windows shared 3. Comment ----- Opening a folder from gnome menu places that was a windows shared folder
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Browsing windows shared directory 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I have a bookmark to a Windows 2003-based share. I clicked on the book mark to mount it. 2. Crash. 3. Comment ----- It wouldn't mount until I opened a new tab in Nautilus.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I tried to mount a share on a Windows XP inside the Virtual machine. 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.no 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. ns/nc 2. 3.
*** Bug 652139 has been marked as a duplicate of this bug. ***
*** Bug 655703 has been marked as a duplicate of this bug. ***
*** Bug 655586 has been marked as a duplicate of this bug. ***
*** Bug 649350 has been marked as a duplicate of this bug. ***
*** Bug 655115 has been marked as a duplicate of this bug. ***
*** Bug 640849 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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, you are encouraged to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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