Version: 3.5.9 (using KDE 3.5.9) OS: Linux Installed from: Debian testing/unstable Packages BUG: when the permissions of a file or folder displayed currently in Konqueror is changed outside of Konqueror (e.g. command line or a different file manager), then Konqueror shows in context menu permissions (right-mouse-click) stale (the pre-change acquired) permission-information. REPRODUCE: change a file or folders permissions while displaying it in Konqueror in the command line. Then open the permissions in Konqueror with right-mouse-click and see the old, previous permissions. So it seems those information get taken out of cache, despite the file-size gets re-read again. Example: display a folder with rwx for UserA with Konqueror started by user UserA. Change the ownership so that UserA can't read that folder anymore with sudo on command line. Right-click as UserA on that folder in Konqueror. The size of that folder will be displayed as "can't enter folder ...", which is correct, but the permissions will still be displayed from before. And you can change the permissions, which then, on write-attemt leads to an error-msg with insufficient rights. Resolvment: e.g. re-read the permission information on opening the context menu, so all is up to date. RESOLVE: e.g. re-read the file-information on right-click
KDE 3 is no longer maintained. However, this issue also affects KDE 4 from git master and is fault of KDirListerCache not sending update notifications when the permissions of directories and files is changed externally.
*** Bug 118136 has been marked as a duplicate of this bug. ***
Git commit 9c1e5d56cdfb844f49a41010d307882939971da1 by Dawit Alemayehu. Committed on 19/05/2013 at 01:05. Pushed by adawit into branch 'KDE/4.10'. Update permissions shown in the properties dialog when it is changed externally. FIXED-IN: 4.10.4 REVIEW: 103555 M +7 -1 kio/kio/kdirlister.cpp M +36 -10 kio/tests/kdirlistertest.cpp M +1 -0 kio/tests/kdirlistertest.h http://commits.kde.org/kdelibs/9c1e5d56cdfb844f49a41010d307882939971da1
*** Bug 154205 has been marked as a duplicate of this bug. ***