Version: 3.5.0-1.0.fc3.kde (using KDE 3.5.0-1.0.fc3.kde, Fedora Core release 3 (Heidelberg)) Compiler: gcc version 3.4.4 20050721 (Red Hat 3.4.4-2) OS: Linux (i686) release 2.6.10-1.766_FC3 The bug can be reproduced simply: root creates a file in an user's Desktop folder or in a directory which is opened in konqueror. Then konqueror's property dialog shows root ownership. Now the user closes the property dialog, but not the konqueror window. Then root does a chmod on the file, but opening the properties dialog again shows old (cached?) ownership. This is not just a matter of noticing when permissions are changed, because I would expect konqueror to update this information at least when left-clicking and opening the properties dialog.
My KDE install has my own patch for http://bugs.kde.org/show_bug.cgi?id=106394 and, with this patch, I cannot reproduce your bug. Can someone using a "stock" KDE install try to reproduce?
worksforme, svn r620k on freebsd with no patches
I can reproduce using KDE and Konqueror 3.5.5 on Gentoo. Tried with both chmod, chgrp and chown. Same behaviour. Looks like the property dialog i s using cached information. I need to hit F5 to get thecorrect information in the property window. Cheers Jo
I can confirm that this happens in 3.5.5 TO reproduce: 1. Create a file as root. e.g. do 'sudo touch file' 2. View its properties in Konqueror (Right click on file -> Properties menu entry) 3. Change perms. e.g. 'sudo chown _username_ file' 4. Without refreshing the konqueror window view the properties of 'file' again 5. They will still be listed as belonging to root.
*** Bug 148651 has been marked as a duplicate of this bug. ***
I can confirm that this bug is present in KDE 3.5.9. with Debian testing and Debian unstable. Also, related to this, Konqueror does not update the list of files for VFAT and NTFS filesystems when files are created or deleted from a console.
Message from the Bugsquad and Konqueror teams: This bug is closed as outdated, as we do not have the manpower to maintain the KDE3 version anymore. If you still can reproduce this issue with Konqueror 4.8.4 or later, please open a new report. Thank you for your understanding.
FYI. There is an equivalent bug report against KDE 4.9 for this very same issue. See bug# 173733 ; so this issue has not been resolved at all.
*** This bug has been marked as a duplicate of bug 173733 ***