Description of problem: k3b recognizes new nfs mount only after resart of k3b if you entered the directory before. Version-Release number of selected component (if applicable): k3b-0.12.15-3.1.1 How reproducible: always Steps to Reproduce: 1. Start k3b, go to mount point in dirview 2. Mount nfs filessytem onto this directory. 3. Try to get into the newly mounted filesystem. Actual results: The directory is still empty. Expected results: Mounted filesystem is there. Additional info:
this should be a general kde problem
Or more specifically, lack of dbus-qt bindings.
re-assigning (back) to k3b, see if we can get dbus-qt support working.
should be better with any recent release -> closing.
No, it is not better - it is stillthe same. But the bug affects all kde applications, therefore assigning to kdelibs.
rpm -q k3b kdelibs please.
kdelibs-3.5.7-13.fc8 k3b-1.0.2-1.fc8 It is not bound to k3b. This problem occurs where ever the kde fileselectionbox is used. The qt fileselectionbox is working as expected.
confirmed, using konq... needed a manual refresh to see new directory contents. This may well be one of those things like when going to the doctor: "Dr., my arm hurts when I move it like this..." "Then don't do that!" When I find time, I'll see about reporting this upstream, unless someone beats me to it. :)
Any special preferenced on the thing to beat you? ;-)
Based on the date this bug was created, it appears to have been reported against rawhide during the development of a Fedora release that is no longer maintained. In order to refocus our efforts as a project we are flagging all of the open bugs for releases which are no longer maintained. If this bug remains in NEEDINFO thirty (30) days from now, we will automatically close it. If you can reproduce this bug in a maintained Fedora version (7, 8, or rawhide), please change this bug to the respective version and change the status to ASSIGNED. (If you're unable to change the bug's version or status, add a comment to the bug and someone will change it for you.) Thanks for your help, and we apologize again that we haven't handled these issues to this point. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp We will be following the process here: http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this doesn't happen again.
This bug has been in NEEDINFO for more than 30 days since feedback was first requested. As a result we are closing it. If you can reproduce this bug in the future against a maintained Fedora version please feel free to reopen it against that version. The process we're following is outlined here: http://fedoraproject.org/wiki/BugZappers/F9CleanUp