duplicate entries for devices in nautilus desktop

I can confirm it on Feisty. Volumes are mounted only once, lshal output is ok but there's two icons.

Thank you for your bug. Are those volumes duplicates to the computer place too? Does "gnomevfs-ls computer:" displays the duplicates too?

> Thank you for your bug. Are those volumes duplicates to the computer
> place too? Does "gnomevfs-ls computer:" displays the duplicates too?
They are duplicated in computer place.

For "gnomevfs-ls computer:" I don't know and I can't try. it's not
every time, maybe every ten first login after booting, and now there's
none.

In my case, I am watching my desktop with two mmc cards right now, they are NOT duplicated in the "computer" location nor in gnomevfs-ls computer:

How can I "gnomevfs-ls" what is shown on the desktop? "gnomevfs-ls Desktop" only shows files therein.

Since this does not happen frequently can you tell me some way to gather debug information regarding the issue? It seems to happen only the first time nautilus is launched after a restart, maybe this can be of help.

I clicked on both the volumes and opened two nautilus windows, then unmounted one of the two, the other remained there on the desktop, then I closed the first window, then the second and I got this crash report - if it can be of help:

Distribution: Ubuntu 6.10 (edgy)
Gnome Release: 2.16.1 2006-10-02 (Ubuntu)
BugBuddy Version: 2.16.0

Memory status: size: 129650688 vsize: 0 resident: 129650688 share: 0 rss: 37924864 rss_rlim: 0
CPU usage: start_time: 1168511884 rtime: 0 utime: 810 stime: 0 cutime:764 cstime: 0 timeout: 46 it_real_value: 0 frequency: 0

Backtrace was generated from '/usr/bin/nautilus'

Using host libthread_db library "/lib/tls/i686/cmov/libthread_db.so.1".
[Thread debugging using libthread_db enabled]
[New Thread -1226701136 (LWP 4737)]
0xffffe410 in __kernel_vsyscall ()
#0 0xffffe410 in __kernel_vsyscall ()
#1 0xb76b634b in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
#2 0xb7e4d1b6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
#3 <signal handler called>
#4 0xb76cc9a1 in IA__g_object_unref (_object=0x8ada328) at gobject.c:1737
#5 0xb76400f1 in IA__g_list_foreach (list=0x897a280,
    func=0x8064d20 <g_object_unref@plt>, user_data=0x0) at glist.c:495
#6 0xb7c953cc in gtk_ui_manager_finalize (object=0x8831190)
    at gtkuimanager.c:392
#7 0xb76ccaec in IA__g_object_unref (_object=0x8831190) at gobject.c:1788
#8 0x0809d28d in nautilus_window_finalize (object=0x86e6c88)
    at nautilus-window.c:635
#9 0xb76ccaec in IA__g_object_unref (_object=0x86e6c88) at gobject.c:1788
#10 0xb7b82f99 in IA__gtk_main_do_event (event=0x8cbfad8) at gtkmain.c:1395
#11 0xb7a0c7ea in gdk_event_dispatch (source=0x81961b8, callback=0,
    user_data=0x0) at gdkevents-x11.c:2320
#12 0xb7642802 in IA__g_main_context_dispatch (context=0x8196200)
    at gmain.c:2045
#13 0xb76457df in g_main_context_iterate (context=0x8196200, block=1,
    dispatch=1, self=0x8177298) at gmain.c:2677
#14 0xb7645b89 in IA__g_main_loop_run (loop=0x81e7bb0) at gmain.c:2881
#15 0xb7b83574 in IA__gtk_main () at gtkmain.c:1024
#16 0x0807bb4a in main (argc=9, argv=0xbfbdd6c4) at nautilus-main.c:372
#17 0xb73ca8cc in __libc_start_main () from /lib/tls/i686/cmov/libc.so.6
#18 0x08067621 in _start ()

Thread 1 (Thread -1226701136 (LWP 4737)):
#0 0xffffe410 in __kernel_vsyscall ()
No symbol table info available.
#1 0xb76b634b in __waitpid_nocancel ()
   from /lib/tls/i686/cmov/libpthread.so.0
No symbol table info available.
#2 0xb7e4d1b6 in gnome_gtk_module_info_get () from /usr/lib/libgnomeui-2.so.0
No symbol table info available.
#3 <signal handler called>
No symbol table info available.
#4 0xb76cc9a1 in IA__g_object_unref (_object=0x8ada328) at gobject.c:1737
 __r = <value optimized out>
 object = (GObject *) 0x8ada328
 __PRETTY_FUNCTION__ = "IA__g_object_unref"
#5 0xb76400f1 in IA__g_list_foreach (list=0x897a280,
    func=0x8064d20 <g_object_unref@plt>, user_data=0x0) at glist.c:495
 next = (GList *) 0x0
#6 0xb7c953cc in gtk_ui_manager_finalize (object=0x8831190)
    at gtkuimanager.c:392
No locals.
#7 0xb76ccaec in IA__g_object_unref (_object=0x8831190) at gobject.c:1788
 object = (GObject *) 0x8831190
 __PRETTY_FUNCTION__ =...

Nautilus and the Gnome desktop display two memory card icons if Ubuntu is booted with memory card inserted. This only happens when the memory card is inserted before Ubuntu is booted. If I insert the memory card into my USB reader after Ubuntu boots, I will only see one icon, as expected, in Nautilus and on the desktop.

This issue does not affect Ubuntu 6.06 (Dapper Drake). I first noticed it appear in Ubuntu 6.10 (Edgy Eft). The problem persists with Ubuntu 7.04 (Feisty Fawn).

There does not seem to be any difference between the behavior of the two icons. While the memory card is mounted, it is possible to access the contents of the volume by opening either icon (by double-clicking).

It is possible to unmount the volume by right-clicking on one of the 2 icons and selecting, "Unmount". The memory card will un-mount, however, one of the icons will remain on the Desktop and one will remain in the Nautilus "Places' menu--although in Nautilus the icon will change locations.

I have the same problem with an external hard drive. It began in Edgy and has persisted into Feisty.

Restarting DBUS fixes the problem for me.

restarting dbus doesn't fix anything, gnomevfs is just doing fallback on fstab parsing when you do that which might workaround the duplicate entry but creates other breakages most likely

Is somebody seeing this on gutsy? I guess this bug could be closed, since I never saw that again. Anyway, I will never have an mmc icon again it seems due to bug #137686 so it could be as well only "fixed" for me :)

I have seen it in Gutsy (tribe 5) a couple of times. But the last two week or so it hasn't happened again. I guess it was just temporarily broken and fixed again.

It happens in Gutsy too, with all patches applied on 20071011. I guess it was just temporarily fixed and broken again ;-) ;-) ;-)

I've got two iPod icons (the iPod was sitting in its dock at boot time), and two disk icons for a flash card that was inserted in the card reader at boot time.

Unmounting one of the icons makes it disappear and the media be unmounted, but the twin icon is left on the desktop. Nothing remains in the /media directory when the media has been unmounted, even though one icon is still visible, but a single entry appears when the media is mounted -- a "disk" entry for the flash card, or an "Ipod" entry for the ipod.

I'm still having this problem with gutsy too.
It got worse now, because a logout/login would fix it; unfortunately there's another bug which prevents a proper login after a logout, so only a restart fixes it for me now.

I get this bug in Gutsy too but only about a third of the times I login.

I confirmed this bug on Gutsy release too. gnomevfs-ls shows no duplication in device entries but not with Nautilus.
Upgraded from Feisty does not produce this bug. I encountered this bug only with fresh install of Gutsy.

I have upgraded from Gutsy and have this bug. I don't notice it that much, but maybe 10% of the time I have duplicate icons for removable media.

That should be 'upgraded from Feisty' in my last comment -- obviously :)

Still no workarounds?

I just ran into the same feature. I decided to play around a little. In case my observation can help shed some light on the issue, here they are:

Background:
I am running Feisty Workstation, with few customization, VMWare server the only non Ubuntu add-on (observations below were made on the host, not a VM). I have an external USB disk with two partitions on it. As it is pretty much plugged in permanently they would ideally result in two additional device icons once the desktop is fully started up. Here is what I actually saw:

[1] The first time ever I connected the USB drive I got the expected two icons.

[2] The next time I rebooted the system I got four icons, two for each partition, both actually connecting to the appropriate file system.

[3] On consecutive reboots, I get two, three, or four icons, most commonly four, three is the second most often.

[4] When consulting .nautilus/metafiles/x-nautilus-desktop:%2F%2F%2F.xml (the only file that seems to reference those partitions), I find two entries for each of the two partitions in question.

[5] Removing the duplicate entries and restarting gdm will "fix" the problem for the time being for the next restart of gdm or the next system reboot, but the "fix" does not persist across the next reboot after. Rather, .nautilus/metafiles/x-nautilus-desktop:%2F%2F%2F.xml regains the duplicate entries.

[6] If I remove the original entries and keep the duplicates--- ditto.

[7] If I remove all four partition entries--- ditto.

[8] The number of icons shown will vary across restarting gdm; so a full reboot is _not_ necessary to trigger the problem. If anything restarting gdm tends to fix the problem (got two icons twice in a row). However, I haven't tried often enough to consider my sample size valid.

Hope that this is enough of a pattern to get to narrow it down. Let me know if I can be of help---

FL

I never saw this again. Is this still a problem in hardy?

Haven't noticed it since alpha5 (where I boarded the Heron-train). But I have to admit I have all desktop icons disabled, use no gnome-panels and instead use avant-window-navigator. So this isn't a real comparison (to my previous Gutsy/Feisty installations).

closing the bug since nobody seem to have it on hardy, there is no recent duplicate and nautilus changed a lot this cycle, feel free to reopen if you still get the issue using the new version though

I am now seeing this bug again in intrepid. Attaching a screenshot and the output from lshal. In the screenshot you can view the two SD card reader icons, however in lshal there is only one icon.

Now I tried to unmount one of the "two" volumes, and then opened the other one. This results in the device being read very badly: I only have three items in it (DCIM folder, 100NIKON folder and a .DSC file), while you can view in the second screenshot the mess that results in nautilus (random files and unicode characters being presented). I tried to umount the second device from nautilus, but it stays there.

Then, I removed the card manually. The SD icon turned into a normal "unmounted volume" icon. I reinserted the card and a new SD icon appeared. From there I view my files correctly, however the old "unmounted volume" icon is still there. You can view this in the third screenshot I attach. Opening the unmounted volume does not make it change into a mounted volume, and it still shows garbled content. Killing nautilus with nautilus -q and restarting it does not change things, however this does not always happen, I just noticed it right now.

These two lines in the output of "mount" are probably the culprit

/dev/mmcblk1p1 on /media/disk type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)
/dev/mmcblk0p1 on /media/disk-1 type vfat (rw,nosuid,nodev,uhelper=hal,shortname=mixed,uid=1000,utf8,umask=077,flush)

If I run "sudo umount /media/disk" the "wrong" icon of course disappears. Now we have to understand where is the bug actually.

the current comment suggests that's not a nautilus bug, it's just listing things which are mounted correctly

I agree. Do you think this may be a bug in hal?

could you run lshal --monitor, plug your device and copy the log to the bug?

Here it is, however the bug appears randomly and is not appearing right now, so I guess this is not the debug output that would be required to understand what's happening.

Start monitoring devicelist:
-------------------------------------------------
14:59:56.682: pci_104c_803c_mmc_host_mmc_card_rca53244 added
14:59:56.865: storage_serial_0x509da3f3 added
14:59:56.975: volume_part1_size_507258368 added
14:59:57.169: volume_part1_size_507258368 property volume.mount_point = '/media/disk'
14:59:57.176: volume_part1_size_507258368 property volume.is_mounted = true

Notice that the above is the log when I remove and insert the SD card, since the device is internal I can't "unplug" it.

Here is the log when the two devices are present.

20:19:28.641: volume_part1_size_507258368 property volume.mount_point = '(null)'
Unknown type 0=''
20:19:28.655: volume_part1_size_507258368 property volume.is_mounted =
20:19:28.658: volume_part1_size_507258368 removed
20:19:28.665: storage_serial_0x509da3f3 removed
20:19:28.673: pci_104c_803c_mmc_host_mmc_card_rca53244 removed
20:19:33.636: pci_104c_803c_mmc_host_mmc_card_rca53244 added
20:19:33.787: storage_serial_0x509da3f3 added
20:19:33.890: volume_part1_size_507258368 added
20:19:34.081: volume_part1_size_507258368 property volume.mount_point = '/media/disk-1'
20:19:34.088: volume_part1_size_507258368 property volume.is_mounted = true

This definitely is a consequence of at least suspend-to-ram (not always of suspend-to-disk).

Linking upstream

Raising priority. This is not just a cosmetical issue, it also breaks gphoto camera access, and spams the user with lots of "cannot lock device"/"cannot mount bla" error messages.

whoops, sorry; I meant bug 332875 which is the master bug for jaunty.

could you try if that's still an issue in current jaunty?

Defect does not seem to be present in Ubuntu 9.04. I cannot reproduce on 9.04, although with the same hardware, I was able to see this defect on 6.10 and 7.04.

closing since tht works now