Bug 144626

Summary: nautilus/gnome-vfs2 slow startup without hald
Product: [Fedora] Fedora Reporter: Sean Middleditch <sean>
Component: gnome-vfs2Assignee: Tomáš Bžatek <tbzatek>
Status: CLOSED INSUFFICIENT_DATA QA Contact:
Severity: medium Docs Contact:
Priority: medium    
Version: rawhideCC: jonstanley, tsmetana
Target Milestone: ---   
Target Release: ---   
Hardware: i386   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2008-05-10 05:28:46 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Sean Middleditch 2005-01-09 23:51:27 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5)
Gecko/20041220 Epiphany/1.4.7

Description of problem:
If hald cannot startup (or is locked up during startup) then Nautilus
takes a *very* long time to start (several minutes at least).  I'm
ASSuming it's trying to talk to HAL and has a long timeout.  Once it
does come up, it performs at normal speeds.

Version-Release number of selected component (if applicable):
nautilus-2.8.1-5 gnome-vfs2-2.8.2-10  hal-0.4.2.cvs20041210-1

How reproducible:
Always

Steps to Reproduce:
1. log into gnome with hald not running; nautilus takes a long time to
come up
    

Additional info:

Comment 1 Alexander Larsson 2006-09-01 15:00:43 UTC
Do you still see this? 
How come your hald didn't start?


Comment 2 Jon Stanley 2008-05-10 05:28:46 UTC
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received feedback to the
information we have requested above, we will assume the problem was not
reproducible, or has been fixed in one of the updates we have released for the
reporter's distribution.

Users who have experienced this problem are encouraged to upgrade to the latest
update of their distribution, and if this issue turns out to still be
reproducible in the latest update, please reopen this bug with additional
information.

Closing as INSUFFICIENT_DATA.