GNOME Bugzilla – Bug 99383
mount generates desktop icon on all desktop instances
Last modified: 2004-12-22 21:47:04 UTC
Package: nautilus Severity: minor Version: 2.0.6-6 Synopsis: mount generates desktop icon on all desktop instances Bugzilla-Product: nautilus Bugzilla-Component: Desktop Description: Description of Problem: When multiple X sessions are running with multiple nautilus desktops, multiple new icons appear when a new mount is attached. E.g., if one console session is active and two Xvnc sessions are active, then user mounts a smb share or a CD, three icons will appear on all X terminals. Steps to reproduce the problem: 1. Launch X console, launch VNC Server (either manual or -inet) 2. Launch appropriate VNC Viewer on remote console 3. Mount a share or CD 4. Note there will be two desktop icons created for the new resource Actual Results: N mount icons on each desktop, where N is the number of instances of the nautilus desktop. Expected Results: One mount icon on each desktop, regardless of nautilus desktop instances. How often does this happen? Very repeatable. Attempted with 2, 3, and 4 desktop instances. Additional Information: Redhat 8.0 kernel-2.4.18-18.8.0 gnome-desktop-2.0.6-4 gnome-session-2.0.5-7 nautilus-2.0.6-6 vnc-server-3.3.3r2-39 vnc-3.3.3r2-29 XFree86-4.2.0-72 ------- Bug moved to this database by unknown@bugzilla.gnome.org 2002-11-23 16:28 ------- The original reporter (rawilt@msn.com) of this bug does not have an account here. Reassigning to the exporter, unknown@bugzilla.gnome.org. Reassigning to the default owner of the component, nautilus-maint@bugzilla.gnome.org.
This could be related to bug 99502
I can see how this would happen, each nautilus sees the new media and creates a launcher for it in the desktop directory. Nautilus would need to be made check if an icon has already been created.
Does this happen in the latest release?
Yes, with Redhat 9 the problem is still present. Current versions are listed below: kernel-2.4.20-9 gnome-desktop-2.2.0.1-4 gnome-session-2.2.0.2-4 nautilus-2.2.1-5 vnc-server-3.3.3r2-47 vnc-3.3.3r2-47 XFree86-4.3.0-2
This is fixed in 2.3.x.