abrt detected a crash. Attached file: backtrace cmdline: nautilus component: nautilus executable: /usr/bin/nautilus kernel: 2.6.31.5-127.fc12.x86_64 package: nautilus-2.28.1-4.fc12 rating: 4 reason: Process was terminated by signal 6
Created attachment 374044 [details] File: backtrace
Looks like an infinite recursion in device_recurse. David ?
*** Bug 542992 has been marked as a duplicate of this bug. ***
*** Bug 541688 has been marked as a duplicate of this bug. ***
*** Bug 538682 has been marked as a duplicate of this bug. ***
*** Bug 544499 has been marked as a duplicate of this bug. ***
*** Bug 544501 has been marked as a duplicate of this bug. ***
*** Bug 538684 has been marked as a duplicate of this bug. ***
*** Bug 544500 has been marked as a duplicate of this bug. ***
Can you collect the information requested in http://www.freedesktop.org/wiki/Software/DeviceKit-disks when this happens again ?
hi, i have execute command related on site and result is in new attachment.
Created attachment 378086 [details] gvfs-mount -li with root session (su on terminal)
Created attachment 378087 [details] devkit-disks --dump
Created attachment 378088 [details] cat /etc/fstab
Created attachment 378089 [details] cat /proc/self/mountinfo
rpm -q DeviceKit-disks gvfs libatasmart result : DeviceKit-disks-009-3.fc12.x86_64 gvfs-1.4.2-1.fc12.x86_64 libatasmart-0.17-1.fc12.x86_64
Created attachment 378732 [details] gvfs-mount -li with user session
I try to execute gvfs-mount -li on terminal with many options. With connection : - su session => I obtain attachment gvfs-mount -li with root session (su on terminal) - user session => I obtain attachment gvfs-mount -li with user session Message for each test is different and i have more information with user session.
*** Bug 555610 has been marked as a duplicate of this bug. ***
*** Bug 555613 has been marked as a duplicate of this bug. ***
*** Bug 567866 has been marked as a duplicate of this bug. ***
How to reproduce ----- 1. Externel HD mount 2. 3.
How to reproduce ----- 1. no plan 2. 3.
*** Bug 586730 has been marked as a duplicate of this bug. ***
This message is a reminder that Fedora 12 is nearing its end of life. Approximately 30 (thirty) days from now Fedora will stop maintaining and issuing updates for Fedora 12. 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 '12'. 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 12'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 12 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 12 changed to end-of-life (EOL) status on 2010-12-02. Fedora 12 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.