abrt 1.0.8 detected a crash. architecture: x86_64 Attached file: backtrace cmdline: nautilus comment: was copying ~20 gb to a usb drive (from ext3 to ext2) and ~10gb from one partition to another on the same physical disk (ext3 to ntfs) component: nautilus executable: /usr/bin/nautilus kernel: 2.6.32.9-70.fc12.x86_64 package: nautilus-2.28.4-2.fc12 rating: 4 reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) release: Fedora release 12 (Constantine)
Created attachment 399465 [details] File: backtrace
How to reproduce ----- 1. Open Nautilus 2. Delete some files 3. Try to open others
How to reproduce ----- 1. Set nautilus behavior to always open in browser windows 2. open multiple tabs in browser windows of diffrent file systems / directories (e.g /media/STORAGE etc) 3. perform multiple file operations (copying/moving/pasting) from different source locations to different target locations. Comment ----- Moving some audio files from an external storage as well as a fixed storage to a different target storage. The move uses multiple directories that are put together in the target location.
How to reproduce ----- 1. Use bulk renamer to rename many files at once 2. Crash. 3.
How to reproduce ----- 1. closing nautilus 2. 3.
Comment ----- delete large number of file with sftp connection protocol
How to reproduce ----- 1. Copying jpg files from digital camera to new folder on machine 2. 3.
Comment ----- The last thing I did in nautilus was to start copying a directory from a FUSE NTFS filesystem to another XFS filesystem. I think that copy operation was successful because my Bittorrent client didn't complain about the integrity of the moved directory.
I'm sorry for the duplicate comments, but abrt complained about some connectivity issues, so I had to report the bug a couple of times.
How to reproduce ----- I don't know.
Comment ----- Select a file at the same time as it's deleted (by some other process) such that the file is deleted between you selecting it and Nautilus getting the file's display name.
How to reproduce ----- 1. copyed files from usb camera to usb external hdd using two instances of Nautilus 2. 3.
How to reproduce ----- 1.Create a mapping to a server using ssh 2.Move a list of file to another folder. Both locations on the mapped drive 3.While moving file acccess another folder on the mapped drive
How to reproduce ----- 1.Open /tmp/ 2.Sort files by size by clicking button on the tab. 3.start pressing del button continuously and using arrow keysgo to the next file if the file is not deleted. Comment ----- I was basically trying to delete files from /tmp, instead of selecting all files and deleting it. I deleted one file at a time.
Comment ----- Happened when I said to "Extract Here" of a zip file
How to reproduce ----- 1. I tried to open a folder that was renamed after nautilus showed it in his window. 2. 3.
Comment ----- I was trying to select some files and folders
*** Bug 583035 has been marked as a duplicate of this bug. ***
*** Bug 583515 has been marked as a duplicate of this bug. ***
*** Bug 585971 has been marked as a duplicate of this bug. ***
*** Bug 587912 has been marked as a duplicate of this bug. ***
*** Bug 589111 has been marked as a duplicate of this bug. ***
*** Bug 589116 has been marked as a duplicate of this bug. ***
*** Bug 590622 has been marked as a duplicate of this bug. ***
*** Bug 590803 has been marked as a duplicate of this bug. ***
*** Bug 591326 has been marked as a duplicate of this bug. ***
*** Bug 591474 has been marked as a duplicate of this bug. ***
*** Bug 593248 has been marked as a duplicate of this bug. ***
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- I was rapidly deleting a load of photos (one by one, but quickly) in eog.
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Unknown, just happened. 2. 3.
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. 2. 3.I have no idea what I was doing when this happened. :-( sorry!
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Deleted multiple files independently using shift+delete in the Downloads folder
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Open nautilus --no-desktop --browser %U 2. Selected redundant files 3. Move to Trash
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Select more than 20 movie files on a cifs share mounted on gnome 2.Delete it by shift+del keys 3.
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- Nautilus crashed while I emptied the trash.
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Transfer files to external hard drive. 2. Check properties on hard drive with right click.
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Open a folder that have been extracted 2. 3.
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. tried to eject my camera in USB memory mode. 2. 3.
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. Attempted to open a folder located in /home/username/Downloads 2. Crash 3.
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) Comment ----- no idea how to reproduce
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- Don't really know. Abbrt sayd that nautilus were broken. I just were rellocating my files in transmission to another directory.
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.closed nautilus 2. 3.
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1. click on an unmounted usb drive before it disappears from the list on "computer" 2. 3.
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- (deleted a jpg file during thumbnail generation)
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
Package: nautilus-2.30.1-3.fc13 Architecture: x86_64 OS Release: Fedora release 13 (Goddard) How to reproduce ----- 1.Delete many files. I was deleting 135 (all in the directory) and it died with 9 to go, said the status window. 2. 3. Comment ----- Delete many files (135).
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.
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.