Hide Forgot
Description of problem: when searching / or just /home/user/ for test nautilus is unusable, I have i7 processor so other cores or threads can be used no need for such behaviour. matches found 3.500 from search over / nautilus was unresponsive for a few minutes, this is odd Version-Release number of selected component (if applicable): nautilus-2.28.4-18.el6.x86_64 How reproducible: 100% Steps to Reproduce: 1.place some file on your desktop (e.g. testfile.txt) 2.go into search dialog (ctrl+f) 3.search file in / Actual results: have to wait for search end to continue work Expected results: can work during nautilus search Additional info:
I would guess it's cycling inside of symlink loop. Anyway, do you have Tracker installed and running? Is there a heavy disk activity or just CPU load?
it's not cycling .. it will finish .. the thing is it's not running in separate thread. I can work in other programs but when moving search dialog around my desktop is blurred it possibly redraws but after 30 seconds or so .. It should be possible to work without noticing something is working in background. no I do not have tracker installed.. what is it? is it available in RHEL6?
Tracker is semantical indexer, working in background, making a database of your documents, pictures, etc. Nautilus can use tracker to quickly find what you need.
(In reply to comment #2) is it available in RHEL6? how can i check it's on?
(In reply to comment #4) > (In reply to comment #2) > is it available in RHEL6? how can i check it's on? Ha, it's not... I thought we pushed full set of basic gnome desktop components there. Ok then. Not sure if this is easily fixable as we probably need to make sync operations async.
Okay, this looks like a candidate for fixing. But first, could you please attach debugger to a running process and grab a backtrace at the point nautilus is unresponsive? It would give me an idea what's going on... Btw. the search is actually running in a thread, might be a synchronize issue or your system just can't hold that much I/O load.
Since RHEL 6.3 External Beta has begun, and this bug remains unresolved, it has been rejected as it is not proposed as exception or blocker. Red Hat invites you to ask your support representative to propose this request, if appropriate and relevant, in the next release of Red Hat Enterprise Linux.