The currently expected behavior of the GNOME 2.8 desktop on Fedora Core 3 is to pop-up a device when it is plugged in (eg. USB stick). But when the user right-clicks and manually selects unmount, plugs out the device and plugs it back in, it does not pop-up again. Instead, if the user plugs out the device without an unmount notification to the desktop, the desktop icon prevails and when clicked, generates an error.
What is the reason for this? ... and if there is a valid reason, how does the user handle this situation more elegantly? After all, the user might want to plug in the same device twice in a session.
fre, 27.05.2005 kl. 20.42 skrev R.Ramkumar:
The currently expected behavior of the GNOME 2.8 desktop on Fedora Core 3 is to pop-up a device when it is plugged in (eg. USB stick). But when the user right-clicks and manually selects unmount, plugs out the device and plugs it back in, it does not pop-up again. Instead, if the user plugs out the device without an unmount notification to the desktop, the desktop icon prevails and when clicked, generates an error.
What is the reason for this? ... and if there is a valid reason, how does the user handle this situation more elegantly? After all, the user might want to plug in the same device twice in a session.
-- ram_einstein FC3
ram_einstein.blogspot.com
And then there is the "device may popup anywhere at random - including beneath icons". And, on a crowded desktop as mine, it may be impossible to find. Would be kind of cool if it did "glow" as windows do in FC4 when they wants to popup. :P
Kyrre
On Sat, 2005-05-28 at 00:12 +0530, R.Ramkumar wrote:
The currently expected behavior of the GNOME 2.8 desktop on Fedora Core 3 is to pop-up a device when it is plugged in (eg. USB stick). But when the user right-clicks and manually selects unmount, plugs out the device and plugs it back in, it does not pop-up again. Instead, if the user plugs out the device without an unmount notification to the desktop, the desktop icon prevails and when clicked, generates an error.
What is the reason for this? ... and if there is a valid reason, how does the user handle this situation more elegantly? After all, the user might want to plug in the same device twice in a session.
Most likely you have one of the few devices that cause the usb-storage module to hang on a syscall to the kernel when polling the device. This in turn causes HAL to hang. This is "fixed" in the latest HAL on FC4 in which HAL forks for each device it polls so if there is a hang it hangs the forked copy and not all of HAL. Of course this is wasteful of resources and the only real fix would be to fix the usb-storage module or get the newer ub module running better.
-- J5
desktop@lists.stg.fedoraproject.org
-
John (J5) Palmieri -
Kyrre Ness Sjobak -
R.Ramkumar