Red Hat Bugzilla – Bug 139646
No automatic refresh on documenttree
Last modified: 2007-11-30 17:10:54 EST
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; rv:1.7.3) Gecko/20041001
Description of problem:
I mounted my developmentshare on the local webserver (W2k) through
fstab as smbfs successfully during start. I can cerate, delete, change
documents and folders without any problem.
In the left frame I have the documentlist/foldertree of this webfolder
(/mnt/webdev/testdev/). I create a new file and saves it to a folder.
It appears immediately in the left frame in the folderview.
In Quanta (3.3) the Bug is:
Independend, which view (folder, project) I choose - when I create a
document and saves it to the related folder (e.g.
/mnt/webdev/testdev/), it appears not automatically. With folderview I
have to refresh the tree, in projectview I have to restart Quanta to
see the file.
Chnages in documents are immediately available. It happens when I
create or delete a file.
It happens only on mounted shares! If I do it locally, everything
Version-Release number of selected component (if applicable):
latest version (Date Nov., 17th 2004)
Steps to Reproduce:
1. Open Quanta, select folder
2. Create new document
3. Saving it to the folder
4. Needs a refresh or reload of Quanta to see it.
Sorry, forgot to say: i use Gnome.
Fedora Core 3 is now maintained by the Fedora Legacy project for security
updates only. If this problem is a security issue, please reopen and
reassign to the Fedora Legacy product. If it is not a security issue and
hasn't been resolved in the current FC5 updates or in the FC6 test
release, reopen and change the version to match.
Closing per lack of response to previous request for information.
This bug was originally filed against a much earlier version of Fedora
Core, and significant changes have taken place since the last version
for which this bug is confirmed.
Note that FC3 and FC4 are supported by Fedora Legacy for security
fixes only. Please install a still supported version and retest. If
it still occurs on FC5 or FC6, please reopen and assign to the correct
version. Otherwise, if this a security issue, please change the
product to Fedora Legacy. Thanks, and we are sorry that we did not
get to this bug earlier.