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 300597 - files from cdda:///dev/cdrom violates gnome-vfs MIME type rules
files from cdda:///dev/cdrom violates gnome-vfs MIME type rules
Product: gnome-vfs
Classification: Deprecated
Component: Module: (other)
Other Linux
: Normal normal
: ---
Assigned To: gnome-vfs maintainers
gnome-vfs maintainers
Depends on: 310656
Reported: 2005-04-14 11:25 UTC by Stanislav Brabec
Modified: 2008-09-06 19:05 UTC
See Also:
GNOME target: ---
GNOME version: 2.11/2.12

Description Stanislav Brabec 2005-04-14 11:25:05 UTC
Version details: gnome-vfs-2.10.0
Distribution/Version: SuSE Linux 9.3

Open cdda:///dev/cdrom in Nautilus and click to any file there. You will only
see warning about security risk opening this file.

Fix: Add .waw to file names.

Related: bug 138033, bug 171595
Comment 1 Sebastien Bacher 2005-07-17 15:53:46 UTC
Thanks for your bug.

The cdda method uses that:

"		dirname = gnome_vfs_uri_extract_dirname (uri);			
		schemedir = g_strdup_printf ("cdda://%s", dirname);
		/* Remove trailing '/' if there is one */
		sep = strrchr (schemedir, '/');
		if (sep != NULL) {
			schemedir [strlen (schemedir) - 1] = '\0';

The issue is than gnome_vfs_uri_extract_dirname returns name without as "/" so
the code drops a char of the path. I've opened #310656 about this
Comment 2 André Klapper 2008-09-06 19:05:51 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: 
Reasons behind this decision are listed at