Hide Forgot
abrt version: 1.1.18 architecture: i686 Attached file: backtrace, 8536 bytes cmdline: /usr/libexec/gvfsd-trash --spawner :1.10 /org/gtk/gvfs/exec_spaw/0 component: gvfs Attached file: coredump, 9654272 bytes crash_function: g_vfs_job_emit_finished executable: /usr/libexec/gvfsd-trash kernel: 2.6.35.12-90.fc14.i686.PAE package: gvfs-1.6.6-1.fc14 rating: 4 reason: Process /usr/libexec/gvfsd-trash was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) How to reproduce: Viewing the Trash bin in gnome with files from a mounted samba network share in it. time: 1303724186 uid: 500
Created attachment 494632 [details] File: backtrace
Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Opened Facebook chat windows in Firefox 2. 3.
Package: gvfs-1.8.1-2.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- no idea
Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Empty thrash 2.Crash 3.
Package: gvfs-1.8.2-1.fc15 Architecture: i686 OS Release: Fedora release 15 (Lovelock) Comment ----- I have no idea.
Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. open natulis 2. search for "iso" in the trash 3. click through some folders and gvfs crashes Comment ----- would search for any deleted iso files in my trash
Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. just openning the trash directory 2. 3.
Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.open the recycle bin 2. 3.
Package: gvfs-1.10.0-1.fc16 Architecture: i686 OS Release: Fedora release 16 (Verne) Comment ----- Playing youtube movie by using Chromium Browswer. Suddenly browser flash player down and receive this error messsage.
Package: gvfs-1.6.6-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Примонтировал устройство (Nokia XPressMusic) 2. Открыл карту памяти 3. Вылетела ошибка
Package: gvfs-1.10.1-2.fc16 Architecture: x86_64 OS Release: Fedora release 16 (Verne) Comment ----- dont know any more
Could someone please explain the status? Why is this closed as NOTABUG? This still triggers abrt in the current fedora 16 version.
This is likely NOTABUG because the original report seems to be against Samba. So when using Samba software, the original bug happens. Samba software is technically not supported by Fedora / Red Hat. If you can reproduce this issue with current Fedora version, then re-create the issue with a default Fedora install. You may need to create a new bug for this, or just search for a similar bug that doesn't involve Samba. I get this issue with my Recycle Bin everyday in Fedora 14. But I'm doing my best to ignore it until I upgrade.
Got the same crash with trash bin, without samba share or something on F18 (whatever it's status is now).
I was trying to mount and access files onn a remote ftp or smb host. When asking for a password, I refused three times in a row, then the modal window stayed grey, and I couldnt use the File application anymore. backtrace_rating: 4 Package: gvfs-1.14.2-2.fc18 OS Release: Fedora release 18 (Spherical Cow)
I get this crash on login in F18. No Samba or trash in sight.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
This message is a reminder that Fedora 18 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 18. 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 '18'. 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 18's end of life. Thank you for reporting this issue and we are sorry that we may not be able to fix it before Fedora 18 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, you are encouraged change the 'version' to a later Fedora version prior to Fedora 18's end of life. 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.
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.