abrt version: 1.1.14 architecture: x86_64 Attached file: backtrace cmdline: /usr/libexec/gvfsd-smb --spawner :1.10 /org/gtk/gvfs/exec_spaw/9 component: gvfs crash_function: gkr_operation_block_and_unref executable: /usr/libexec/gvfsd-smb kernel: 2.6.35.9-64.fc14.x86_64 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) time: 1291660721 uid: 500 How to reproduce ----- 1. Double-clicking windows network icon 2. 3.
Created attachment 465035 [details] File: backtrace
Package: gvfs-smb-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.attempting to create a shared directory on the system for access from Windows machines on the same network 2. 3. Comment ----- Entered the share parameters, clicked Proceed , boom
Package: gvfs-smb-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Navigated to "Places" on Desktop Selected a previously setup share. 2. Clicked on Share password dialog box gameup, selected rember for this session 3. DBUS dialog box came up Comment ----- This seems to happen after I boot. I will try to mount the windows share again then it starts to work.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Attempted to open existing bookmark to network location [previously accesssed w/o problem] 2. 3.
Package: gvfs-smb-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Navigated to Places 2. Seletcted a samba folder on a remote RH server 3. System crashed. Comment ----- This does not always happens but generally happens after a system restart
Package: gvfs-smb-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. connect to samba share 2. choose to never forget password 3. Comment ----- no
this has worked fine for years, no solution in sight.. now switching distro..
Package: gvfs-smb-1.6.6-1.fc14 Architecture: x86_64 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.In Network, navigate Windows Network/{domain}/Windows machine 2.Login to Windows (7) machine, editing domain 3.Select "User$" folder, login, editing domain {CRASH} Comment ----- Suspicion: I may not have SHARED on the Windows machine.
I also checked Remember Forever - only in step 3, however.
(In reply to comment #1) > func=0x3464016680 "gkr_operation_block_and_unref", message=0x7ff8fc090850 "assertion failed: (op->pending != pending)" Don't see this problem here (F15). Can you check that gnome-keyring-daemon is running at the time of the crash (or before)?
Moreover, have you seen any selinux denials?
Reported upstream: https://bugzilla.gnome.org/show_bug.cgi?id=644407 One last question - is this reproducible always?
Hi Tomas, thanks for looking into this. The problem is always reproducible. No selinux denials, I have also deactivated selinux for testing purposes.. g-k-d is running at the time of the crash. Also happens with clean profile.
i have just tried the upstream patch. fixes the problem. great!
libgnome-keyring-2.32.0-2.fc14 has been submitted as an update for Fedora 14. https://admin.fedoraproject.org/updates/libgnome-keyring-2.32.0-2.fc14
libgnome-keyring-2.32.0-2.fc14 has been pushed to the Fedora 14 stable repository. If problems still persist, please make note of it in this bug report.