GNOME Bugzilla – Bug 687023
Nautilus Jumps to Home on the Other Tab
Last modified: 2012-10-29 20:25:00 UTC
Dear developer(s), This is how you could see an interrupting behavior in Nautilus 3.6: Open Nautilus with two tabs. Under the left tab, for example, open any folder other that the home folder. Under the right tab, search a word but don't close the search entry afterward. Now, if you go back to the left tab, it'll jump to the home folder. You could go to the previously opened folder with "back" button but this behavior gets really annoying after a while. I tried Nautilus 3.7.1 and saw the same thing.
Thanks for taking the time to report this bug. This particular bug has already been reported into our bug tracking system, but we are happy to tell you that the problem has already been fixed. It should be solved in the next software version. You may want to check for a software upgrade. *** This bug has been marked as a duplicate of bug 686893 ***
Hi, I'm afraid that your patch for fixing this bug has a side effect: After a search, clicking on the search button doesn't show the searched location anymore but just leaves the results to be shown. I tested your patch for Nautilus-3.6.1 but I think the same issue should exist in v3.7. Why not just using if (location != NULL) { nautilus_window_go_to (window, location); g_object_unref (location); } in the original function nautilus_window_set_search_visible() from v3.6.1?
Indeed, I just pushed additional fixes for this bug you're mentioning to both git master and gnome-3-6.
Thanks a lot for your quick replies. I really appreciate your efforts and just want to be helpful. This time, clicking on the search button makes the tab always load the Home directory after a search, in spite of its previous location. By my previous comment I meant why making Home as a fallback directory at all? Am I wrong in supposing that "location" is NULL only when the searched folder is somehow removed? In that case, Nautilus would show a warning dialog after clicking on the button and there would be no need to a fallback location.
Thank you for testing - as we can see there's never enough of it! The fallback return to Home was another oversight not covered by the previous fix. It should all work fine now, I pushed another patch to git.
Everything seems to be OK now :) Thanks again for your efforts.