Back to bug 713179
| Who | When | What | Removed | Added |
|---|---|---|---|---|
| Ales Zelinka | 2011-06-14 15:10:03 UTC | Priority | unspecified | medium |
| Severity | unspecified | medium | ||
| Cameron Meadors | 2011-10-03 23:27:46 UTC | QA Contact | desktop-bugs | desktop-qa-list |
| prashant ingale | 2012-11-01 10:01:46 UTC | CC | pingale | |
| Tomáš Bžatek | 2012-11-02 14:33:35 UTC | Status | NEW | ASSIGNED |
| Simon Green | 2013-03-01 05:09:28 UTC | CC | pingale | vgaikwad |
| Tomas Kopecek | 2013-05-09 09:17:19 UTC | Assignee | tbzatek | oholy |
| Ondrej Holy | 2015-02-24 10:04:23 UTC | Status | ASSIGNED | POST |
| Matthias Clasen | 2015-10-23 14:45:42 UTC | CC | mclasen | |
| Blocks | 1271696 | |||
| Jiri Koten | 2015-10-23 15:03:40 UTC | CC | jkoten | |
| Ondrej Holy | 2015-11-10 14:41:42 UTC | Status | POST | MODIFIED |
| Link ID | GNOME Desktop 729463 | |||
| Fixed In Version | gvfs-1.4.3-23.el6 | |||
| errata-xmlrpc | 2015-11-11 10:23:36 UTC | Status | MODIFIED | ON_QA |
| Ondrej Holy | 2015-11-11 11:49:46 UTC | Doc Text | Cause: File paths in archives with components consisting of single dot (i.e. ./foo/bar, foo/./bar) weren't handled by gvfsd-archive backend properly. Consequence: Archive backend crashed with some specific archives during mount operation. Fix: File path components consisting of single dot are skipped currently. Result: Archive backend is mounted properly with mentioned specific archives. |
|
| Chris Williams | 2015-11-16 19:18:58 UTC | Blocks | 1172231 | |
| Bohdan Milar | 2016-01-12 11:35:56 UTC | CC | bmilar | |
| Bohdan Milar | 2016-03-07 15:28:20 UTC | Status | ON_QA | VERIFIED |
| Jiri Herrmann | 2016-04-06 19:17:10 UTC | CC | jherrman | |
| Docs Contact | jherrman | |||
| Doc Text | Cause: File paths in archives with components consisting of single dot (i.e. ./foo/bar, foo/./bar) weren't handled by gvfsd-archive backend properly. Consequence: Archive backend crashed with some specific archives during mount operation. Fix: File path components consisting of single dot are skipped currently. Result: Archive backend is mounted properly with mentioned specific archives. | gvfs correctly checks if the metadata database has been loaded Prior to this update, the gvfs metadata daemon and client applications such as Nautilus terminated unexpectedly when unitialized internal structures were used for corrupted or unreadable metadata databases. The missing check has been added that verifies that the metadata database has been loaded properly. As a result, in the described circumstances, an error is returned instead of a crash occurring. | ||
| Doc Type | Bug Fix | Release Note | ||
| Jiri Herrmann | 2016-04-06 19:29:20 UTC | Doc Text | gvfs correctly checks if the metadata database has been loaded Prior to this update, the gvfs metadata daemon and client applications such as Nautilus terminated unexpectedly when unitialized internal structures were used for corrupted or unreadable metadata databases. The missing check has been added that verifies that the metadata database has been loaded properly. As a result, in the described circumstances, an error is returned instead of a crash occurring. | The gvfs-archive backend no longer crashes due to certain archive file paths Mounting gvfs-archive backend previously terminated unexpectedly when used with archives that had a single dot (".") character as a component of their file path. With this update, these file path components are skipped, and in the mentioned situation, the archive backend mounts correctly. |
| Jiri Herrmann | 2016-04-07 11:36:39 UTC | Doc Text | The gvfs-archive backend no longer crashes due to certain archive file paths Mounting gvfs-archive backend previously terminated unexpectedly when used with archives that had a single dot (".") character as a component of their file path. With this update, these file path components are skipped, and in the mentioned situation, the archive backend mounts correctly. | The gvfs-archive backend no longer crashes due to certain archive file paths Mounting the gvfs archive backend previously terminated unexpectedly when used with archives that had a single dot (".") character as a component of their file path. With this update, these file path components are skipped, and in the mentioned situation, the archive backend mounts correctly. |
| Jiri Herrmann | 2016-04-19 17:50:04 UTC | Doc Text | The gvfs-archive backend no longer crashes due to certain archive file paths Mounting the gvfs archive backend previously terminated unexpectedly when used with archives that had a single dot (".") character as a component of their file path. With this update, these file path components are skipped, and in the mentioned situation, the archive backend mounts correctly. | The *gvfs* archive backend no longer crashes due to certain archive file paths Mounting the *gvfs* archive backend previously terminated unexpectedly when used with archives that had a single dot (".") character as a component of their file path. With this update, these file path components are skipped, and in the mentioned situation, the archive backend mounts correctly. |
| Jiri Herrmann | 2016-04-22 13:49:10 UTC | Doc Text | The *gvfs* archive backend no longer crashes due to certain archive file paths Mounting the *gvfs* archive backend previously terminated unexpectedly when used with archives that had a single dot (".") character as a component of their file path. With this update, these file path components are skipped, and in the mentioned situation, the archive backend mounts correctly. | The *gvfs* archive back end no longer crashes due to certain archive file paths Mounting the *gvfs* archive back end previously terminated unexpectedly when used with archives that had a single dot (".") character as a component of their file path. With this update, these file path components are skipped, and in the mentioned situation, the archive back end mounts correctly. |
| Jiri Herrmann | 2016-04-28 10:45:33 UTC | Doc Text | The *gvfs* archive back end no longer crashes due to certain archive file paths Mounting the *gvfs* archive back end previously terminated unexpectedly when used with archives that had a single dot (".") character as a component of their file path. With this update, these file path components are skipped, and in the mentioned situation, the archive back end mounts correctly. | The *gvfs* archive backend no longer crashes due to certain archive file paths Mounting the *gvfs* archive backend previously terminated unexpectedly when used with archives that had a single dot (".") character as a component of their file path. With this update, these file path components are skipped, and in the mentioned situation, the archive backend mounts correctly. |
| errata-xmlrpc | 2016-05-09 16:12:32 UTC | Status | VERIFIED | RELEASE_PENDING |
| errata-xmlrpc | 2016-05-10 19:43:39 UTC | Status | RELEASE_PENDING | CLOSED |
| Resolution | --- | ERRATA | ||
| Last Closed | 2016-05-10 15:43:39 UTC |
Back to bug 713179