GNOME Bugzilla – Bug 585711
nautilus crash when clicking desktop icons for drives
Last modified: 2012-03-28 10:48:23 UTC
Steps to reproduce: 1. clicking any of the fat32, ntfs or dvdrom drive icons on the desktop 2. 3. Stack trace: Distribution: Fedora release 11 (Leonidas) Gnome Release: 2.26.1 2009-04-29 (Red Hat, Inc) BugBuddy Version: 2.26.0 System: Linux 2.6.29.4-167.fc11.x86_64 #1 SMP Wed May 27 17:27:08 EDT 2009 x86_64 X Vendor: The X.Org Foundation X Vendor Release: 10601901 Selinux: Enforcing Accessibility: Disabled GTK+ Theme: Glossy Icon Theme: default.kde GTK+ Modules: canberra-gtk-module, pk-gtk-module, gnomebreakpad Memory status: size: 618852352 vsize: 618852352 resident: 22052864 share: 15228928 rss: 22052864 rss_rlim: 18446744073709551615 CPU usage: start_time: 1244964171 rtime: 177 utime: 147 stime: 30 cutime:0 cstime: 0 timeout: 0 it_real_value: 0 frequency: 100 Backtrace was generated from '/usr/bin/nautilus' [Thread debugging using libthread_db enabled] 0x0000003fa160e9dd in __libc_waitpid (pid=3845, stat_loc=<value optimized out>, options=0) at ../sysdeps/unix/sysv/linux/waitpid.c:41 41 int result = INLINE_SYSCALL (wait4, 4, pid, stat_loc, options, NULL); Current language: auto; currently minimal
+ Trace 215997
Thread 1 (Thread 0x7f240fe1e800 (LWP 3703))
----------- .xsession-errors (20 sec old) --------------------- (nm-connection-editor:3472): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Sp ** libgdu:ERROR:gdu-pool.c:1253:device_recurse: assertion failed: (depth < 100) (nautilus:3703): GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSig Initializing nautilus-gdu extension ** (nautilus:3703): WARNING **: Unable to add monitor: Not supported Window manager warning: Buggy client sent a _NET_ACTIVE_WINDOW message with a timestamp of 0 for 0x4800003 (Archive Ma) Window manager warning: meta_window_activate called by a pager with a 0 timestamp; the pager needs to be fixed. Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1a7 specified for 0x460163e (File Info ). Window manager warning: Invalid WM_TRANSIENT_FOR window 0x1a7 specified for 0x460165f (File Info ). ** libgdu:ERROR:gdu-pool.c:1253:device_recurse: assertion failed: (depth < 100) -------------------------------------------------- Other information: Installed Fedora 11 x86_64 and updated everything to latest version. Fedora automatically created icons for my ntfs, fat32 drives and dvdrom drive on desktop. Clicking any of these icons makes nautilus crash. (PID for nautilus changes after this). I also have crash logs for Xsession and nautilus. (.xsession-errors and nautilus-debug-log.txt) Both say the nearly the same thing: GVFS-RemoteVolumeMonitor-WARNING **: invoking IsSupported() failed for remote volume monitor with dbus name org.gtk.Private.GduVolumeMonitor: org.freedesktop.DBus.Error.Spawn.ChildSignaled: Process /usr/libexec/gvfs-gdu-volume-monitor received signal 6 Initializing nautilus-gdu extension ** (nautilus:3703): WARNING **: Unable to add monitor: Not supported I doubt the bug is related to the automatically created icons, but I don't know a way how to look into their code.
Traveling to these drives via a terminal or file browser is OK, they are correctly mounted and appear in mtab, but I cannot open them from Desktop or from within "Computer" on Desktop, too.
--> gnome-disk-utility (in the plugin for nautilus) Thanks for taking the time to report this bug. Unfortunately, that stack trace is missing some elements that will help a lot to solve the problem, so it will be hard for the developers to fix that crash. Can you get us a stack trace with debugging symbols? Please see http://live.gnome.org/GettingTraces for more information on how to do so and reopen this bug or report a new one. Thanks in advance! Specifically, it's missing symbols for libgdu, and the rest of gnome-disk-utility
installed some more debuginfo packages and here is the current list: [root@fedorastation ~]# rpm -qa|grep debug|sort atk-debuginfo-1.25.2-2.fc11.x86_64 avahi-debuginfo-0.6.25-1.fc11.x86_64 cairo-debuginfo-1.8.6-2.fc11.x86_64 dbus-debuginfo-1.2.12-1.fc11.x86_64 dbus-glib-debuginfo-0.80-2.fc11.x86_64 exempi-debuginfo-2.1.0-3.fc11.x86_64 gamin-debuginfo-0.1.10-4.fc11.x86_64 GConf2-debuginfo-2.26.0-2.fc11.x86_64 glib2-debuginfo-2.20.1-1.fc11.x86_64 glibc-debuginfo-2.10.1-2.x86_64 gnome-desktop-debuginfo-2.26.1-4.fc11.x86_64 gnome-disk-utility-debuginfo-0.3-1.fc11.x86_64 gnome-keyring-debuginfo-2.26.1-1.fc11.x86_64 gtk2-debuginfo-2.16.1-4.fc11.x86_64 gvfs-debuginfo-1.2.3-2.fc11.x86_64 hal-debuginfo-0.5.12-26.20090226git.fc11.x86_64 libcdio-debuginfo-0.81-2.fc11.x86_64 libexif-debuginfo-0.6.16-3.fc11.x86_64 libICE-debuginfo-1.0.4-7.fc11.x86_64 libselinux-debuginfo-2.0.80-1.fc11.x86_64 libSM-debuginfo-1.1.0-4.fc11.x86_64 libsoup-debuginfo-2.26.1-1.fc11.x86_64 libX11-debuginfo-1.2-3.fc11.x86_64 libxml2-debuginfo-2.7.3-2.fc11.x86_64 libXrender-debuginfo-0.9.4-5.fc11.x86_64 nautilus-debuginfo-2.26.3-1.fc11.x86_64 pango-debuginfo-1.24.1-1.fc11.x86_64 PolicyKit-debuginfo-0.9-6.fc11.x86_64 unique-debuginfo-1.0.4-4.fc11.x86_64 [root@fedorastation ~]# attaching a more detailed stack trace right now
Created attachment 137056 [details] a more detailed stack trace I hope. I installed some more debuginfo packages before creating this one. please tell me which debuginfo packages I still need to install if this stack trace is not enough detailed, too.
The stack trace has lots of details now, thanks! I think something's getting confused somewhere between DeviceKit and gnome-disk-utility. Can you attach the output of the command udevinfo -a -p /sys/block/sdb/sdb1/ --attribute-walk (udevinfo should be in the udev package which you should already have installed). Thanks for your time!
[root@fedorastation ~]# udevinfo -a -p /sys/block/sdb/sdb1/ --attribute-walk the program '/bin/bash' called 'udevinfo', it should use 'udevadm info <options>', this will stop working in a future release Udevadm info starts with the device specified by the devpath and then walks up the chain of parent devices. It prints for every device found, all possible attributes in the udev rules key format. A rule to match, can be composed by the attributes of the device and the attributes from one single parent device. looking at device '/devices/pci0000:00/0000:00:0d.0/host2/target2:0:0/2:0:0:0/block/sdb/sdb1': KERNEL=="sdb1" SUBSYSTEM=="block" DRIVER=="" ATTR{partition}=="1" ATTR{start}=="16065" ATTR{size}=="2" ATTR{stat}==" 6 0 10 1 0 0 0 0 0 1 1" looking at parent device '/devices/pci0000:00/0000:00:0d.0/host2/target2:0:0/2:0:0:0/block/sdb': KERNELS=="sdb" SUBSYSTEMS=="block" DRIVERS=="" ATTRS{range}=="16" ATTRS{ext_range}=="256" ATTRS{removable}=="0" ATTRS{ro}=="0" ATTRS{size}=="390721968" ATTRS{capability}=="52" ATTRS{stat}==" 355 6659 17210 3030 1 0 1 3 0 2398 3032" looking at parent device '/devices/pci0000:00/0000:00:0d.0/host2/target2:0:0/2:0:0:0': KERNELS=="2:0:0:0" SUBSYSTEMS=="scsi" DRIVERS=="sd" ATTRS{device_blocked}=="0" ATTRS{type}=="0" ATTRS{scsi_level}=="6" ATTRS{vendor}=="ATA " ATTRS{model}=="ST3200822A " ATTRS{rev}=="3.01" ATTRS{state}=="running" ATTRS{timeout}=="30" ATTRS{iocounterbits}=="32" ATTRS{iorequest_cnt}=="0x174" ATTRS{iodone_cnt}=="0x174" ATTRS{ioerr_cnt}=="0x0" ATTRS{modalias}=="scsi:t-0x00" ATTRS{evt_media_change}=="0" ATTRS{queue_depth}=="1" ATTRS{queue_type}=="none" looking at parent device '/devices/pci0000:00/0000:00:0d.0/host2/target2:0:0': KERNELS=="target2:0:0" SUBSYSTEMS=="scsi" DRIVERS=="" looking at parent device '/devices/pci0000:00/0000:00:0d.0/host2': KERNELS=="host2" SUBSYSTEMS=="scsi" DRIVERS=="" looking at parent device '/devices/pci0000:00/0000:00:0d.0': KERNELS=="0000:00:0d.0" SUBSYSTEMS=="pci" DRIVERS=="pata_amd" ATTRS{vendor}=="0x10de" ATTRS{device}=="0x0265" ATTRS{subsystem_vendor}=="0x105b" ATTRS{subsystem_device}=="0x0d04" ATTRS{class}=="0x01018a" ATTRS{irq}=="0" ATTRS{local_cpus}=="00000000,00000001" ATTRS{local_cpulist}=="0" ATTRS{modalias}=="pci:v000010DEd00000265sv0000105Bsd00000D04bc01sc01i8a" ATTRS{numa_node}=="0" ATTRS{enable}=="1" ATTRS{broken_parity_status}=="0" ATTRS{msi_bus}=="" looking at parent device '/devices/pci0000:00': KERNELS=="pci0000:00" SUBSYSTEMS=="" DRIVERS=="" [root@fedorastation ~]# I must admit that I have a really weird hard disk setup. [root@fedorastation ~]# fdisk -l Disk /dev/sda: 80.0 GB, 80026361856 bytes 255 heads, 63 sectors/track, 9729 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x142b142a Device Boot Start End Blocks Id System /dev/sda1 * 1 3825 30720000 7 HPFS/NTFS /dev/sda2 6375 9730 26949632 7 HPFS/NTFS Partition 2 does not end on cylinder boundary. /dev/sda3 3825 3838 102400 83 Linux /dev/sda4 3839 6374 20370420 5 Extended /dev/sda5 3839 6374 20369408 8e Linux LVM Partition table entries are not in disk order Disk /dev/dm-0: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-0 doesn't contain a valid partition table Disk /dev/dm-1: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-1 doesn't contain a valid partition table Disk /dev/dm-2: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-2 doesn't contain a valid partition table Disk /dev/dm-3: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-3 doesn't contain a valid partition table Disk /dev/dm-4: 1073 MB, 1073741824 bytes 255 heads, 63 sectors/track, 130 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-4 doesn't contain a valid partition table Disk /dev/dm-5: 8589 MB, 8589934592 bytes 255 heads, 63 sectors/track, 1044 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-5 doesn't contain a valid partition table Disk /dev/dm-6: 2147 MB, 2147483648 bytes 255 heads, 63 sectors/track, 261 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x00000000 Disk /dev/dm-6 doesn't contain a valid partition table omitting empty partition (5) Disk /dev/sdb: 200.0 GB, 200049647616 bytes 255 heads, 63 sectors/track, 24321 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0xd3e0d0fd Device Boot Start End Blocks Id System /dev/sdb1 2 24321 195350400 f W95 Ext'd (LBA) /dev/sdb5 2 9200 73890936 b W95 FAT32 /dev/sdb6 9201 19005 78758631 b W95 FAT32 /dev/sdb7 19006 24321 42700738+ 7 HPFS/NTFS Disk /dev/sdc: 750.1 GB, 750156374016 bytes 255 heads, 63 sectors/track, 91201 cylinders Units = cylinders of 16065 * 512 = 8225280 bytes Disk identifier: 0x296e2744 Device Boot Start End Blocks Id System /dev/sdc1 * 1 86010 690875293+ 7 HPFS/NTFS /dev/sdc2 86011 91201 41696707+ f W95 Ext'd (LBA) /dev/sdc5 86011 91201 41696676 b W95 FAT32 You have new mail in /var/spool/mail/root [root@fedorastation ~]# sda is 80GB SATA, including MBR and has 2 ntfs partitions, one at the beginning of the hdd and the other at the end, a linux boot partition in the middle and a linux LVM partition after it. sdb is 200GB IDE. has 2 FAT32 partitions and an NTFS partition. I'm sure it is IDE, not SCSI SATA or USB but I see that it is recognized as sdX instead of hdX. Maybe that convention is deprecated... sdc is 750GB SATA connected via USB, has an NTFS and a FAT32 partition. MBR is running on WinXP NTLDR, grub is booted from NTLDR and then Fedora. By default. WinXP and Fedora try to write MBR to 200GB IDE even if booting is defaulted to 80GB through BIOS, but the only way to let it write to 80GB SATA is disconnecting 200GB IDE.
I figured out that Palimpset Disk Utility (GUI frontend for DeviceKit) is crashing when I try to start it. I doubt that the crash is caused by DeviceKit. I'll try to contact it's developer.
*** This bug has been marked as a duplicate of bug 622066 ***