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 529547 - Double clicking on Floppy Drive gives an error (Unable to mount location) despite it's mounted but not opened
Double clicking on Floppy Drive gives an error (Unable to mount location) des...
Status: RESOLVED OBSOLETE
Product: gvfs
Classification: Core
Component: [obsolete] hal volume monitor
0.2.x
Other All
: Normal normal
: ---
Assigned To: gvfs-maint
gvfs-maint
Depends on:
Blocks:
 
 
Reported: 2008-04-23 14:01 UTC by Sergio Zanchetta
Modified: 2016-10-19 13:44 UTC
See Also:
GNOME target: ---
GNOME version: 2.21/2.22

Attachments
Error message (7.93 KB, image/png)
2008-04-23 14:03 UTC, Sergio Zanchetta 		Details

Description Sergio Zanchetta 2008-04-23 14:01:11 UTC 
Please describe the problem:
The bug has been opened on
https://bugs.edge.launchpad.net/ubuntu/+source/gvfs/+bug/203722

The FIRST time I try to mount floppy double clicking its icon I get an error message: See attachment

In English sounds like:
"Unable to mount location"
"Unable to mount file"

but this doesn't prevent mounting itself because floppy is mounted correctly (just wait some seconds) although it doesn't open any folder.
If I unmount and mount it again during the same gnome session no problem at all. (Apart from other bugs filed separately)
The error message come up every FIRST mounting time of every session.


Steps to reproduce:


Actual results:


Expected results:


Does this happen every time?


Other information:
Comment 1 Sergio Zanchetta 2008-04-23 14:03:16 UTC 
Created attachment 109774 [details]
Error message
Comment 2 Alexander Larsson 2009-03-10 14:21:34 UTC 
I don't have a floppy, so i can't test this. But it might be fixed by:

2009-03-05  Alexander Larsson  <alexl@redhat.com>

        * monitor/hal/ghaldrive.c:
        * monitor/hal/ghalmount.c:
        * monitor/hal/ghalvolume.c:
        * monitor/hal/ghalvolumemonitor.c:
	Remove all locking (not needed since we're now
	a single threaded process).
	Don't emit signals in idle, thus risking callback
	reordering. We don't need this anymore as it was
	part of the locking structure.

	This should fix the "No mount object for mounted
	volume" error when mounting.


in gvfs 1.1.8.

Could someone test that?
Comment 3 Sergio Zanchetta 2009-03-12 14:26:09 UTC 
I just tried gvfs 1.1.8 and the bug is not fixed unfortunately.
Comment 4 Ondrej Holy 2016-10-19 13:44:01 UTC 
Hal volume is obsolete currently. If you see this issue also with udisks2 volume monitor, please file a bug for udisks2 volume monitor...