Comment 11 for bug 118467

Description of problem:

  When trying to unmount a filesystem via the disk mount applet
  while the filesystem is still in use, gnome-mount displays a useful
  error message:

    +---[]-----------------------------+
    | Cannot unmount volume |
    | |
    | An application is preventing the |
    | volume 'foobar' from being |
    | unmounted. |
    | [ OK ] |
    +----------------------------------+

  It comes from gnome-mount and has no window title, but at
  least it shows some kind-of informative text.

  After the user clicks [OK], /usr/libexec/drivemount_applet2
  shows this useless error dialog:

  +-[Unmo]-+
  | |
  | [OK]|
  +--------+

  xwininfo tells that the title should be "Unmount Error".

Version-Release number of selected component (if applicable):

  gnome-applets-2.22.1-1.fc9.i386

How reproducible:

  always

Steps to Reproduce:
1. Insert any hotpluggable device with a filesystem.
2. Wait for hal/gnome-mount to work their magic and mount the FS.
3. Open terminal window and "cd /media/proper-dir" to simulate the app.
4. Click "Unmount foo" in the disk drive mounter applet.

Actual results:

  +-[Unmo]-+
  | |
  | [OK]|
  +--------+

Expected results:

  Either a useful error message or none at all, as gnome-mount has already
  popped up one.

Additional info:

  The useless empty error dialog does NOT pop up when trying to unmount the
  filesystem from the Gnome file manager thingie (is it still called
  nautilus?) or by running "gnome-mount -u -d /dev/sdb1" from a terminal.
  This makes me think the "Disk Mounter" applet is the culprit.

  Oh, and why does the "*Disk* Mounter 2.22.1" (About dialog) correspond to
  the /usr/libexec/*drive*mount_applet2 executable (emphasis mine)? That is
  confusing, to say the least.