Bug 154205

Version:            (using KDE KDE 3.97.0)
Installed from:    Ubuntu Packages
OS:                Linux

Steps to reproduce:

1. In Konsole do: mkdir /tmp/foo
2. Open Konqueror
3. Go to /tmp or to /tmp/foo
4. In Konsole do: chmod -x /tmp/foo
5. Try navigating into /tmp/foo from elsewhere in Konqueror.

Expected result:

I should not be allowed into the /tmp/foo folder.

Actual result:

I am allowed.

Notes:

1) Problem persistent till closing all Konqueror windows:

I have to entirely close all existing windows of Konqueror and then restart Konqueror to make it recognize the no-entry permission on the directory. Simply navigating elsewhere in the same tab, opening a new tab, or trying a new Konqueror window without closing the old one are all ineffective in making Konqueror recognize the new permissions.

2) Problem does not arise until first stat of directory by Konqueror

Also, unless Konqueror at least once reads the permission of the folder, this behaviour is not seen. That is, if I skip step 3 or go anywhere other than /tmp or /tmp/foo in step 3, then after step 4 and step 5 I am denied access, which is the accepted behaviour.

3) Konqueror recognises +x change, only not -x change

That is, if before step 2 I add a chmod -x /tmp/foo and then at step 4 I do chmod +x /tmp/foo and try step 5, then Konqueror sees the new permissions of the folder and allows me inside, where it did not allow me before.