Summary: | kde-base/kdelibs-4.13.1: kio reports disk full when copy to CIFS share (was: kde-base/dolphin-4.13.1 reports disk full when copy to CIFS share) | ||
---|---|---|---|
Product: | Gentoo Linux | Reporter: | barrie backhurst <barrie.backhurst> |
Component: | [OLD] KDE | Assignee: | Gentoo KDE team <kde> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | gentoo, sqn14 |
Priority: | Normal | ||
Version: | unspecified | ||
Hardware: | All | ||
OS: | Linux | ||
URL: | https://bugs.kde.org/show_bug.cgi?id=334776 | ||
Whiteboard: | fixed in 4.13.2 | ||
Package list: | Runtime testing required: | --- | |
Attachments: |
Upstream fix
Ebuild which uses the patch |
Description
barrie backhurst
2014-05-22 09:03:34 UTC
Created attachment 377616 [details, diff] Upstream fix https://bugs.kde.org/show_bug.cgi?id=334776#c15 Created attachment 377618 [details]
Ebuild which uses the patch
same here. This is not a dolphin issue, but a KIO issue, so this affects also krusader and other applications. Please backport the patch from upstream. This is very problematic bug if your home is mounted on a cifs share! (In reply to Till Schäfer from comment #3) > same here. > > This is not a dolphin issue, but a KIO issue, so this affects also krusader > and other applications. > > Please backport the patch from upstream. This is very problematic bug if > your home is mounted on a cifs share! Yes of course, the patch is the same as the backported one. I think in the next days a gentoo release will use the official fix from the kde repository: https://bugs.kde.org/show_bug.cgi?id=334776#c29 Comment on attachment 377616 [details, diff]
Upstream fix
Will use git commit, which contains commit message.
Thanks for reoporting. This is fixed in cvs now. Please sync in some hours to get the changes. + + 25 May 2014; Johannes Huber <johu@gentoo.org> + +files/kdelibs-4.13.1-kio-diskfree.patch, +kdelibs-4.13.1-r1.ebuild, + -kdelibs-4.13.1.ebuild: + Revision bump adds upstream patch which reverts a regression with cifs mounts + introduced in 4.13.1, bug #511012. + |