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 312171 - hal/non-hal incoherence: gnome_vfs_drive_get_activation_uri ()
hal/non-hal incoherence: gnome_vfs_drive_get_activation_uri ()
Status: RESOLVED WONTFIX
Product: gnome-vfs
Classification: Deprecated
Component: URI handling
2.11.x
Other All
: High normal
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on:
Blocks:
 
 
Reported: 2005-07-31 22:26 UTC by Sebastien Bacher
Modified: 2008-09-06 19:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12


Description Sebastien Bacher 2005-07-31 22:26:57 UTC 
gnome_vfs_drive_get_activation_uri () returns "" or the fstab path (ie:
"file:///media/floppy0") 
for a non-mounted volume, depending of how it's build. That's not coherent and
creates issues like bug #310270.

The API has no description for this function. A convention should be picked here
and one of the functions changed to match it.
Comment 1 Christian Neumair 2005-07-31 22:54:09 UTC 
Good catch! This has to be sorted out since it can be a nasty source of
confusion and crashers.
Comment 2 David Zeuthen (not reading bugmail) 2005-08-01 01:03:59 UTC 
This is pretty intentional - in the general case we simply don't know a'priori
where a GnomeVFSDrive will be mounted - this is especially true if you use a
mount program like pmount where the mount point in /media is not created until
you actually mount the device. I submit it's a bug we need to fix if
applications / libraries depend on the activation_uri GnomeVFSDrive at all. Does
this make sense?

See bug 308475 for an example of one bug fixed.
Comment 3 Sebastien Bacher 2005-08-01 07:41:30 UTC 
That seems to be right, so the non-hal code should be changed to return "" too
Comment 4 Luis Villa 2005-08-24 21:45:43 UTC 
Will this be fixed for 2.12? Does it need to be? What is the user impact?
Comment 5 Alexander Larsson 2005-09-01 12:15:00 UTC 
davidz: The problem seems to be that you get NULL from gnome_vfs_uri_new(""),
which can cause crashes like in bug 310270.
Comment 6 Elijah Newren 2006-01-11 05:43:33 UTC 
I'm going to drop this from the release blocker list (gnome-target); if you feel it should still be on the list, feel free to re-add and answer Luis' questions for us bugsquadders.  :)
Comment 7 André Klapper 2008-09-06 19:05:52 UTC 
gnome-vfs has been deprecated and superseded by gio/gvfs since GNOME 2.22, hence mass-closing many of the gnome-vfs requests/bug reports. This means that gnome-vfs is NOT actively maintained anymore, however patches are still welcome.

If your reported issue is still valid for gio/gvfs, please feel free to file a bug report against glib/gio or gvfs.

@Bugzilla mail recipients: query for gnome-vfs-mass-close to get rid of these notification emails all together.


General further information: http://en.wikipedia.org/wiki/GVFS 
Reasons behind this decision are listed at http://www.mail-archive.com/gnome-vfs-list@gnome.org/msg00899.html