After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 43902 - Some search results do not have file info displayed
Some search results do not have file info displayed
Status: RESOLVED FIXED
Product: nautilus
Classification: Core
Component: File Search Interface
0.x.x [obsolete]
Other Linux
: Normal normal
: ---
Assigned To: John Sullivan
Nautilus Maintainers
Depends on:
Blocks:
 
 
Reported: 2000-10-19 21:00 UTC by John Sullivan
Modified: 2004-12-22 21:47 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description John Sullivan 2001-09-10 00:46:21 UTC
To reproduce (at least for me):
(1) Launch Nautilus
(2) Click "Find"
(3) Type ".rpm" as the text to search for, hit Enter
(4) Wait for the results to show up. Wait a little longer for the icons to
appear on most rows. No matter how long I wait, the icons do not appear for some
of the rows. (And the size/type/date don't appear for those rows either)

Some interesting facts: All of the .rpm files anywhere inside /home appear
correctly; all of the .rpm files anywhere outside /home do not. Also, clicking
on one of the rows that does not appear correctly causes it to redraw in
selected state with the correct information, and causes all other rows
representing files in that same directory to correctly update (oooh, that's GOT
to be a clue).



------- Additional Comments From sullivan@eazel.com 2000-10-19 17:06:59 ----

I think this bug is fairly recently introduced, and I think it makes search look
pretty bad, so we probably want to consider it for PR2.



------- Additional Comments From sullivan@eazel.com 2000-10-19 17:13:55 ----

Another clue: I've only seen this happen when there are several different
directories in the search results. I'm suspicious of Darin's recent async_job
changes that postpone some directory info fetching. Maybe the postponed jobs
aren't getting started properly when the non-postponed ones finish?



------- Additional Comments From sullivan@eazel.com 2000-10-20 09:17:29 ----

Further evidence that this is caused by ther new limit-async-jobs mechanism -- I
changed MAX_ASYNC_JOBS from 10 to 3 in nautilus-directory-async.c. Afterwards,
even fewer of the search results showed file info. I then changed it from 3 to
1. Afterwards, the sidebar panel did not draw with a background, and the "View
as" option menu never got filled in with contents. This seems like pretty strong
proof that this mechanism is either (1) not executing all the postponed async
jobs, or (2) revealing long-standing race condition bugs elsewhere in the
software. I hope it's (1). Darin, I could definitely use help debugging this.



------- Additional Comments From sullivan@eazel.com 2000-10-20 11:00:56 ----

Milestone is now officially moot, since I fixed the bug.



------- Additional Comments From mjs@noisehavoc.org 2000-11-05 20:46:31 ----

Helping Bud prioritize undecided bugs.



------- Bug moved to this database by unknown@bugzilla.gnome.org 2001-09-09 20:46 -------