After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 511139 - Applet Displays Empty Dialog Boxes on Unmount Failure
Applet Displays Empty Dialog Boxes on Unmount Failure
Status: RESOLVED OBSOLETE
Product: gnome-applets
Classification: Other
Component: Disk Mounter (drivemount)
2.20.x
Other All
: Normal minor
: ---
Assigned To: gnome-applets Maintainers
gnome-applets Maintainers
Depends on:
Blocks:
 
 
Reported: 2008-01-21 21:54 UTC by David Tomaschik
Modified: 2011-03-01 22:13 UTC
See Also:
GNOME target: ---
GNOME version: 2.19/2.20



Description David Tomaschik 2008-01-21 21:54:01 UTC
Please describe the problem:
If a drive cannot be unmounted from the drive mounter applet, two dialog boxes are  displayed.  The first dialog box (presented by gnome-mount) states that "An application is preventing..." and correctly presents the unmounting error.  Immediately afterward, a second dialog (part of the drivemount applet) appears with no text in it.  This second dialog is unnecessary and confusing.

Steps to reproduce:
1. Mount a drive with the Gnome mount applet.
2. Open a terminal and "cd" into the mountpoint for the drive.
3. Attempt to unmount the drive from the Gnome mount applet.



Actual results:
A second, useless, error dialog appears.

Expected results:
Only one dialog (probably from gnome-mount) should appear.

Does this happen every time?
Yes, confirmed on multiple systems.

Other information:
Originally reported in Ubuntu: https://bugs.launchpad.net/ubuntu/+source/gnome-applets/+bug/118467

A little more information: it seems that mount_result in drive-button.c of gnome-applets produces its own error dialog in addition to that produced by gnome-umount in gnome-mount. Is this dialog necessary at all? It seems that char *error is empty anyway.

This should be a relatively simple fix, I'm just not sure of the exact codepaths leading to mount_result.
Comment 1 Matthias Clasen 2008-04-21 17:46:48 UTC
Fedora bug for this issue: https://bugzilla.redhat.com/show_bug.cgi?id=443396
Comment 2 Hew McLachlan 2009-05-30 13:11:09 UTC
I cannot reproduce the issue with 2.26.1.
Comment 3 Phillip Susi 2011-03-01 21:19:15 UTC
Multiple people have now said they can not reproduce this, and the original report was for obsolete releases.  I suggest this report be closed now.
Comment 4 André Klapper 2011-03-01 22:13:51 UTC
Closing, thanks for the notice.