abrt version: 1.1.14 architecture: i686 Attached file: backtrace cmdline: nautilus --sm-client-id 1010eaf64f6a8dd0f9128356862072663400000265000049 --sm-client-state-file /home/wbaker/.config/session-state/nautilus-1288011599.state component: nautilus crash_function: nautilus_window_report_load_underway executable: /usr/bin/nautilus kernel: 2.6.34.7-56.fc13.i686.PAE package: nautilus-2.30.1-6.fc13 rating: 4 reason: Process /usr/bin/nautilus was killed by signal 6 (SIGABRT) release: Fedora release 13 (Goddard) time: 1294108438 uid: 500 comment ----- My goal was to accomplish some maintenance on my rpms landfill $ ls rpms | wc -l 8524 From nautilus wished to do the moral equivalent of cd rpms mkdir foo mv *.rpms foo/. The rpms directory is a landfill of all the rpms from past Fedora builds installations ... back through FC4 ... created with hard links to the original locations. At the failuire ~/.xsession-errors contains ERROR:nautilus-window-slot-info.c:93:nautilus_window_slot_info_set_status: assertion failed: (NAUTILUS_IS_WINDOW_SLOT_INFO (slot)) Upon nautilus restart, to replay the failure we see in ~/.xsession-errors Intializing nautilus-pastebin extension... Initializing nautilus-search-tool extension Initializing nautilus-open-terminal extension Nautilus module initialize nautilus_module_list_types() Initializing nautilus-image-converter extension Initializing nautilus-gdu extension Initializing nautilus-sound-converter extension sys:1: GtkWarning: gdk_pixbuf_format_get_name: assertion `format != NULL' failed F3 seems to not function on this large directory. The menu will show the checkbox that the Extra Pane is enabled, but there are not two panes. One can go back and forth in this manner enabling and disabling the extra pane (but no extra pane showsup). When one displays a smaller directory, e.g. the directory immediately above, then the F3 function "works" again to display two panes. With the Extra Pane enabled, one can double-click on the rpms directory ... and force an an abort in the repeatable fashion, seeing ERROR:nautilus-window-manage-views.c:1339:nautilus_window_report_load_underway: assertion failed: (slot != NULL) Upon first contact, it takes 12 seconds to load the rpms directory with 8524 items. It's big but doable... How to reproduce ----- 1. nautilus 2. brows a directory of *.rpm files (~8000 files big over nfs) 3. ...wait... see it come up in icons 4. F3 (enable extra pane)
Created attachment 471580 [details] File: backtrace
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.