Bug#440327: gnome: when the environment can't umount a volume, it should show what locks the volume

[Fernando Cerezal]

Package: gnome
Severity: normal

When a user try to umount a volume that is being used, the environment
shows a message showing it can't, but not why. The solution then is goes to the
terminal, do a "lsof | grep volume" or similar and kill the process.
If the environment can't umount the volume, it should shows a message
showing what is blocking it. Even, if possible, asking user whether
killing the process just before umount the volume.

This is a little problem for advanced users, but a great problem for
non-terminal users.

I dont know what package is responsible of that, please forward this to
the appropriate package.

-- System Information:
Debian Release: lenny/sid
  APT prefers testing
  APT policy: (990, 'testing'), (500, 'stable'), (50, 'unstable'), (20, 'experimental')
Architecture: i386 (i686)

Kernel: Linux 2.6.18-4-686 (SMP w/2 CPU cores)
Locale: LANG=es_ES at euro, LC_CTYPE=es_ES at euro (charmap=ISO-8859-15) (ignored: LC_ALL set to es_ES at euro)
Shell: /bin/sh linked to /bin/bash

Versions of packages gnome depends on:
pn  bluefish                      <none>     (no description available)
pn  evolution | balsa             <none>     (no description available)
pn  gnome-desktop-environment     <none>     (no description available)
pn  gnome-office                  <none>     (no description available)
pn  gnome-themes-extras           <none>     (no description available)
pn  netspeed                      <none>     (no description available)
pn  rhythmbox                     <none>     (no description available)
ii  synaptic                      0.60       Graphical package manager
ii  xscreensaver                  5.03-2     Automatic screensaver for X

gnome recommends no packages.