Este conteúdo não está disponível no idioma selecionado.
1.65. gnome-vfs2
1.65.1. RHBA-2010:0317: bug fix update
An updated gnome-vfs2 package that fixes a bug is now available.
GNOME VFS is the GNOME virtual file system. It is the foundation of the Nautilus file manager. It provides a modular architecture and ships with several modules that implement support for file systems, http, ftp, and others. It provides a URI-based API, backend supporting asynchronous file operations, a MIME type manipulation library, and other features.
* the gnome-vfs2 package would only work correctly on a system running Samba 3.0 packages, and could not be installed on a system running Samba 3.3 packages. The version of gnome-vfs provided with this advisory depends only on a small Samba subpackage, which is independent from other Samba packages. The gnome-vfs2 package can now be installed on a system running Samba 3.3 packages. (BZ#555642)
Users are advised to check the parallel Samba advisory RHBA-2009:9287.
Users are advised to upgrade to this updated gnome-vfs2 package, which resolves this issue.
1.65.2. RHBA-2010:0032: bug fix update
Note
This update has already been released (prior to the GA of this release) as FASTRACK errata RHBA-2010:0032
GNOME VFS is the GNOME virtual file system. It is the foundation of the Nautilus file manager. It provides a modular architecture, and ships with several modules that implement support for file systems and protocols such as HTTP and FTP, among others.
These updated gnome-vfs2 packages provide fixes for the following bugs:
* an unresolved symbol in the gnome-vfs2 library caused the system-config-network GUI application to be unable to start. (BZ#247522)
* client applications which used the gnome-vfs2 library were unable to search for certain paths because the search process ended as soon as it encountered a file or directory which it was unable to read. This update fixes this bug in gnome-vfs2 so that searches skip over unreadable files or directories and continue as expected.
Note: a future nautilus update will be released that properly fixes this bug in the Nautilus file manager. (BZ#432764)
* when attempting to move one or more files between two NFS mounts, the Nautilus file manager displayed a dialog box that stated: Error: "Not on the same file system." This error was caused by an EXDEV error in the gnome-vfs2 file module due to rename semantics. With this update, moving a file from one NFS mount to another succeeds as expected due to the implementation of a proper copy-and-delete fallback routine. (BZ#438116)
* attempting to open a supported document type represented by a symbolic link on an NFS share with the Evince document viewer failed with the following error message:
Unable to open document Unhandled MIME type: “application/octet-stream”
This update improves this behavior with a symbolic link check so that Evince is now able to successfully open a link to a supported document type when both the link and actual file are located on an NFS share. (BZ#481593)
* the gnome-vfs-daemon service reads the list of mounted devices at /proc/mounts upon startup. If one of the device paths was not valid UTF-8, gnome-vfs-daemon was disconnected by D-Bus when it attempted to communicate the path over the system message bus, at which time it exited. However, other GNOME applications would then attempt to restart gnome-vfs-daemon, at which time the same sequence of events reoccurred, leading to a potentially infinite loop and much extraneous CPU usage. With this update, gnome-vfs-daemon correctly converts the information provided by /proc/mounts into valid UTF-8 before communicating it via D-Bus, which prevents the possibility of gnome-vfs-daemon being disconnected, exiting, and being restarted in a continuous fashion. (BZ#486286)
* accessing a WebDAV share which contained a comma in its path name with the Nautilus file manager resulted in a "File not found" error. This update ensures that reserved characters in path names are properly escaped, and thus Nautilus is able to access such paths as expected. (BZ#503112)
All GNOME users are advised to upgrade to these updated packages, which resolve these issues. Running GNOME sessions must be restarted for the update to take effect.