abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: /usr/libexec/gvfs-gdu-volume-monitor component: gvfs crash_function: gdu_pool_get_presentables executable: /usr/libexec/gvfs-gdu-volume-monitor kernel: 2.6.34.7-61.fc13.i686 package: gvfs-1.6.2-1.fc13 rating: 4 reason: Process /usr/libexec/gvfs-gdu-volume-monitor was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) time: 1291223684 uid: 500 How to reproduce ----- 1. Bug au démarrage 2. 3.
Created attachment 464060 [details] File: backtrace
Package: gvfs-1.6.2-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. booted my pc and logged in 2. it stayed quite a time with just showing the background image (~2min) 3. gnome started
Package: gvfs-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. open a sandbox: sandbox -X -t sandbox_web_t firefox -> crash
Package: gvfs-1.6.2-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.general power failure 2.boot 3.
Package: gvfs-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Reboot system after latest update. 2. 3. Comment ----- After installing the latest update to FC13 I re-booted the system.
Package: gvfs-1.6.2-1.fc13 Architecture: i686 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.opened the gdu gui 2.tried to start some undefined/unamed "set" marked as down because of missing member 3. Comment ----- I recentry l added a driver which was belonging to dissolved (I think I did though I have a doubt now) fakeraid stripped set on another computer
Package: gvfs-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. opened a firefox within a SELinux sandbox 2. 3.
Package: gvfs-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. log-in 2. 3.
Package: gvfs-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.all'avvio 2. 3.
Package: gvfs-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. It happens everytime I boot the system 2. 3.
Package: gvfs-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. I installed rhythmbox 2. plugged in a brand new ipod touch 3g to charge 3. started rhythmbox
Package: gvfs-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. It happens everytime I run evolution from KDE 2. 3.
my crash in comment 12 came when running rhythmbox under KDE
Package: gvfs-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Happens on reboot from Windows 7 (dual boot system) 2. Can also happen on reboot from FC13 3. Always followed by gdu-notification-daemon crash Comment ----- Am running F13 on an HP nc6320 with a dual boot Windows 7 x86_64 configuration on the same drive using GRUB. This crash seems to happen in conjunction with my system running very slowly. That is to say, when my system boots normally, I don't get this bug. When it boots and runs very slowly, these crashes happen
Package: gvfs-1.6.2-1.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- I opened Galeon's file chooser dialog to attach a file to an email message in gmail and got an abrt notification of the crash
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.