abrt version: 1.1.13 architecture: i686 Attached file: backtrace cmdline: nautilus component: nautilus crash_function: g_type_check_instance_cast executable: /usr/bin/nautilus kernel: 2.6.35.4-28.fc14.i686.PAE package: nautilus-2.32.0-1.fc14 rating: 4 reason: Process /usr/bin/nautilus was killed by signal 11 (SIGSEGV) release: Fedora release 14 (Laughlin) time: 1287421456 uid: 500 comment ----- I had a usb flash drive with a iso9660 filesystem (! - very convenient!). It mounted fine and was read-only ... mostly. No copy/paste in context menu and ctrl-c ctrl-v didn't work. But I could drag'n'drop from another windows. That opened a hanging progress bar. Cancel didn't work. Ejecting the flash made nautilus crash.
Created attachment 454170 [details] File: backtrace
Hmm... probably just a duplicate of bug 640258?
Program received signal SIGSEGV, Segmentation fault. nautilus_path_bar_size_allocate (widget=0x936f3f0 [NautilusPathBar], allocation=0xbffe7340) at nautilus-pathbar.c:669 669 child = BUTTON_DATA (list->data)->button; (gdb) l 664 child_allocation.x += (path_bar->spacing + path_bar->slider_width); 665 } 666 } 667 668 for (list = first_button; list; list = list->prev) { 669 child = BUTTON_DATA (list->data)->button; 670 gtk_widget_get_child_requisition (child, &child_requisition); 671 672 gtk_widget_get_allocation (widget, &widget_allocation); 673 (gdb) p list $8 = 0x10 = {Cannot access memory at address 0x10 (gdb) info locals child = <value optimized out> path_bar = <value optimized out> direction = GTK_TEXT_DIR_LTR child_allocation = {x = 43046415, y = 72, width = 0, height = 29} list = 0x10 = {<error reading variable list (Cannot access memory at address 0x10)> first_button = 0x95f7ea0 = {0x90d6f10, <error reading variable first_button (Cannot access memory at address 0xace)> width = <value optimized out> allocation_width = 638 border_width = 0 need_sliders = 0 up_slider_offset = 0 down_slider_offset = <value optimized out> child_requisition = {width = 0, height = 0} widget_allocation = {x = 158, y = 72, width = 638, height = 29} (gdb)
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. inserted an USB memory stick 2. cancelled the offered app to open it 3. opened device's folder manually via desktop icon double-click 4. transferred files to new folder on desktop 5. in Nautilus, selected "Safely Remove Drive" 6. crash of Nautilus
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- I just click on the unmount icon of my usb key /dev/sdb1 in nautilus and nautilus crashed
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I ejected a thumbdrive and this crash message appeared 2. 3. Comment ----- Not sure how to reproduce.
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Plugged my computer to TV 2.Wih PC cable 3. and then crash happend Comment ----- Not sure what happened, but just plugged PC into computer
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. unmount an usb stick 2. 3.
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1 2. 3.
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. Plug in an usb-stick (auto mounted) 2. open some text files on the usb-stick an save some text-files to the usb-stick 3. On the gnome desktop right-click on the icon for the mounted usb-stick 4. Choose in the context menu "Safely remove drive" /!\ The icon was removed from the gnome desktop and nautilus crashed
Created attachment 459853 [details] Backtrace for nautilus crashed while unmount usb-stick
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. The kernel parameter usbcore. was set to 999999, since the setting of -1 had not worked (unlike in F13) and usb deviced had been not recognized properly 2. I put a pendrive (TwinMos) into an usb port, a file browser window appeared 3. I issued "eject" ("Wysuń" in Polish ) from the filebrowser window. The pendrive seems to have been unmounted but an alert about a package crash (segmentation violation on nautilus) appeared. Comment ----- The error appears regulary. I have the asus A7N8Xe-deluxe motherboard. I also stress another error I noticed, perhaps connected. In F13 I had to set the kernel parameter usbcore.autosuspend to -1, otherwise most usb devices was not seen. Now in F14 it does not help. I temporarily use the gratest positive timeout for the suspension I was able to set, e.g. 999999 sec., but clearly this is not a safe solution (I am not sure whether somewhere in the system/equipment this number is not truncated to something smaller, so I can get my devices disconnected after a certain time).
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.Plug in an usb-stick 2.Click "Safely remove device" in the windows nautilus just opened 3.nautilus crashes
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- After selecting "eject" at usb flash stick (w two ext3 partititions, device was automounted), nautilus crashed.
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1. I tried to Safely Remove USB drive 2. 3.
Package: nautilus-2.32.0-1.fc14 Architecture: i686 OS Release: Fedora release 14 (Laughlin) How to reproduce ----- 1.I ejected the USB drive and then it reported that an application from package nautilus crashed. 2. 3.
*** Bug 674734 has been marked as a duplicate of this bug. ***
This message is a notice that Fedora 14 is now at end of life. Fedora has stopped maintaining and issuing updates for Fedora 14. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At this time, all open bugs with a Fedora 'version' of '14' have been closed as WONTFIX. (Please note: Our normal process is to give advanced warning of this occurring, but we forgot to do that. A thousand apologies.) Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, feel free to reopen this bug and simply change the 'version' to a later Fedora version. Bug Reporter: Thank you for reporting this issue and we are sorry that we were unable to fix it before Fedora 14 reached 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 to click on "Clone This Bug" (top right of this page) and open it against that version of Fedora. 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