quicksilver & lion problems - typing stops working

[t]

i have been having quicksilver issues ever since upgrading to os
10.7 / lion. i've tried reinstalling several times, and have also
replicated this on another machine. googling has thrown up no
solutions, so i'm presuming i've just go wrong settings somewhere.
here's what's going on:

1. first time i setup and use quicksilver all works fine.
2. if i quit qs or restart my computer then when i start it up again,
call up qs by control-space, then when i start typing *no text appears
in qs* but it does appear to be receiving input because if i hit enter
then it opens something up.
3. however, since i don't see what i'm typing, and it doesn't trigger
the list of things it might open, i have no idea what it's going to
open. it also behaves differently from normal, i.e. typing "post" does
not get "postbox" as the first item, it gets itunes!

i've tried resetting preferences, uninstalling, reinstalling, deleting
caches in ~/library/caches, deleting shelves in /application support,
etc. etc. etc. also tried this on another computer and it's the same
behaviour.
i've tried not changing any of the default preferences.
i've checked and i'm not running any of the known problematic
applications.
the only way to reset it to proper behaviour is to quit quicksilver,
start it up again manually, choose "reset preferences" and go through
the whole thing again.

anyone have any ideas what's going on here?

[Patrick Robertson]

My only suggestion is to check the interface you are using, and that you are using the latest version.

Are you using the built in Bezel interface, or a different one?

[t]

definitely using the latest version. i've tried using both bezel and
primer interface (favouring the latter). does that make a difference?

i've been using QS for years... i'd hate to have to give it up just
because of this....





On Jan 4, 12:45 pm, Patrick Robertson <robertson.patr...@gmail.com>
wrote:

> My only suggestion is to check the interface you are using, and that you
> are using the latest version.
>
> Are you using the built in Bezel interface, or a different one?
>

[Rob McBroom]

On Jan 4, 2012, at 9:54 AM, t wrote:

> 1. first time i setup and use quicksilver all works fine.
> 2. if i quit qs or restart my computer then when i start it up again,
> call up qs by control-space, then when i start typing *no text appears
> in qs* but it does appear to be receiving input because if i hit enter
> then it opens something up.
> 3. however, since i don't see what i'm typing, and it doesn't trigger
> the list of things it might open, i have no idea what it's going to
> open. it also behaves differently from normal, i.e. typing "post" does
> not get "postbox" as the first item, it gets itunes!

This sounds a bit like issue 580.

https://github.com/quicksilver/Quicksilver/issues/580

Though those users say they just can’t use Quicksilver if it runs on login. If they shut it down and/or start it up manually later, everything seems fine (without having to do anything with preferences). If you find that doesn’t work, I would try just deleting the caches and nothing else.

Hopefully we can find a fix, but since none of the regular developers can reproduce it, we can’t track it down. I’ve tried to provide instructions for anyone who *can* reproduce it and wants to help out.

https://github.com/quicksilver/Quicksilver/issues/580#issuecomment-3198986

--
Rob McBroom
<http://www.skurfer.com/>

[t]

that's interesting: i'm also using a Macbook Air (and the other
computer I tried also has an SSD drive) -- seems to be a common
theme...
thanks for the info.

> This sounds a bit like issue 580.
>
> https://github.com/quicksilver/Quicksilver/issues/580
>
> Though those users say they just can’t use Quicksilver if it runs on login. If they shut it down and/or start it up manually later, everything seems fine (without having to do anything with preferences). If you find that doesn’t work, I would try just deleting the caches and nothing else.
>
> Hopefully we can find a fix, but since none of the regular developers can reproduce it, we can’t track it down. I’ve tried to provide instructions for anyone who *can* reproduce it and wants to help out.
>

> https://github.com/quicksilver/Quicksilver/issues/580#issuecomment-31...

[rufwork]

I don't have Xcode installed on this machine, but did want to add that
I have a 13" MacBook (not Air) with SSD and it has the same issue.
Can we all have the same wack software installed that's causing a
conflict, or is Occum suggesting SSD (giving me a Classic extension
flashback)? Anybody *not* have SSD and have this issue?

[Ken Caron]

Glad to see I'm not the only one with this issue.
I'm not on an Air, I'm on a MBP with an aftermarket SSD, running Lion.
Seems to be the same behavior though. It resolves itself when I restart Quicksilver.  It's just a pain as I completely disabled spotlight.

[Jeff Vautin]

I'm having the same problem, with a 15" MBP 8,2, running 10.7.3,
aftermarket SSD from OWC, running the latest version of QS (B65).

Restarting QS resolves the issue. The .plist fix did not work for me,
though.

[Rob McBroom]

On Feb 25, 2012, at 4:07 PM, Jeff Vautin wrote:

> I'm having the same problem, with a 15" MBP 8,2, running 10.7.3,
> aftermarket SSD from OWC, running the latest version of QS (B65).

We still need a volunteer to try the steps outlined here:

https://github.com/quicksilver/Quicksilver/issues/580#issuecomment-3198986

[Rob McBroom]

I think I may have figured this out. Can everyone affected please run this in a Terminal and post the output here?

defaults read com.blacktree.Quicksilver "Last Update Check"

Thanks.

[David Nicholls]

This is what I see:

2012-03-02 07:52:14.269 defaults[524:207]
The domain/default pair of (/Users/<username>/Library/Preferences/com.blacktree.Quicksilver.plist, Last Update Check) does not exist

(where I have changed my user name to <username>).

DN

[David Nicholls]

Looks like the change fixed it. I have removed the plist fix and everything appears to be working properly now. I'm running b65 (3920).

DN

On 02/03/2012, at 1:28 AM, Rob McBroom wrote: