This is the default Lion shut down (which is auto-resume everything on 
start-up). However the behavior is inconsistent because sometimes it loads 
just fine, other times it doesn't. QS is also the only app that does this 
out of all the apps I've got launching on startup.

I also get a 30 second delay with some apps if they're left to resume. 
Namely, for some reason Firefox causes a "pause" on my system when loading 
apps on startup (it even stops loading of SteerMouse and other stuff). 
However, QS has also never crashed on startup with this "pause"... which 
leads me to think that load order or something is a problem. I've even 
tried the other methods of adding QS to login startup items without using 
the built-in preferences in QS to start up. Didn't make any difference to 
the peculiar behavior.

Also, when I leave the system to resume applications, out of all my apps 
only Firefox causes a "pause". Everything else loads super fast (SSD after 
all) and doesn't seem to have any trouble at all.

Only other thing I can think of is possibly conflict with other startup 
items like... Dropbox maybe? I don't know, something that would cause the 
index load to fail on startup if it's not loaded in some proper order?





> Is this when Quicksilver launches on login, or when Lion auto-resumes 
> everything on login (or both)? There are differences. For instance, on my 
> system, if I login fresh, everything pops right up. If Lion “reopens 
> windows” for me, there’s a long delay (30+ seconds) before certain things 
> (including Quicksilver) launch.
>
> Since you don’t see any crash logs, is it possible that Quicksilver’s just 
> not running yet?
>
> -- 
> Rob McBroom
> <http://www.skurfer.com/>
>  
>

-- You received this message because you are subscribed to the Google Groups 
Quicksilver group. To post to this group, send email to 
[email protected]. To unsubscribe from this group, send 
email to [email protected]. For more options, 
visit this group at 
https://groups.google.com/d/forum/blacktree-quicksilver?hl=en

Reply via email to