Start at login does nothing in 10.8

[skurfer]

The preferences stays active across logins, but the application is never added to the user’s login items.

[mickeys]

On 10.8b3 (12A193i) QS honors the start-at-login request and does appear in the login items in the Users & Groups prefPane.

[skurfer]

Confirmed. Thanks for pointing this out.

Having looked into it, we still need to update the way we do this, though.

[ant0ineg]

Any updates on this issue?

[iandol]

I also recently have seen this on 3 new 10.8 mountain lion installs with B69 — I just use launchd instead but this is a fairly major issue for general users nevertheless...

[ahmednuaman]

@iandol can you give us some pointers on starting QS with launchd?

[iandol]

I use the following QS.plist saved to my ~/Library/LaunchAgents/

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>QS</string>
    <key>ProgramArguments</key>
    <array>
        <string>/Applications/Quicksilver.app/Contents/MacOS/Quicksilver</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
</dict>
</plist>

[skurfer]

The preference in Quicksilver isn't working, but adding it to Login Items like you would any other app should work fine.

Also, don't use launchd. Bad idea.

[iandol]

@skurfer — curious why you think launchd is a bad idea?

[tiennou]

Same question, especially since I crafted a plist file that's in the repo for this exact purpose ;-).

El 8 août 2012, a las 02:43, Ian notifications@github.com escribió:

@skurfer — curious why you think launchd is a bad idea?

—
Reply to this email directly or view it on GitHub.

[skurfer]

I forget the details. I'm sure I've explained it on another issue here.

One thing I remember is that it just kills Quicksilver, rather than telling it to quit, so any of the stuff it should be doing at shutdown gets skipped. This is probably less of an issue with the way the most recent crash reporter works, but still, are you OK with that? I don't think it was intended for use with GUI applications. Another thing is what if you actually want to quit Quicksilver for some reason? I don't think that was all.

FYI, the "Open at Login" action is also broken. (It uses the same code as the Quicksilver preference.)

[Sesquipedalian]

I don't know anything about Objective-C, but I have learned a fair bit about launchd and its agents, and I'm pretty sure the launch agent plist that landol posted will work just fine. What isn't a good idea is to add the <KeepAlive> key to the plist, because if QS is crashing, the <KeepAlive> key will create an endless loop of crashing and relaunching. Is that what you were thinking of, Rob? Because all landol's plist does is start Quicksilver and then leave it to its own devices.

Alternatively, one could also use this version in order to avoid launchd having anything directly to do with starting QS:

<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE plist PUBLIC "-//Apple//DTD PLIST 1.0//EN" "http://www.apple.com/DTDs/PropertyList-1.0.dtd">
<plist version="1.0">
<dict>
    <key>Label</key>
    <string>QS</string>
    <key>ProgramArguments</key>
    <array>
        <string>open</string>
        <string>-b</string>
        <string>com.blacktree.Quicksilver</string>
    </array>
    <key>RunAtLoad</key>
    <true/>
</dict>
</plist>

[iwhisperer]

I would like to add this observation to the 'modifier-only activation' issue (single command in my case).
I just noticed that after I quit or hide an app, e.g., Safari, 1Password, and then only having the Finder open, that is when the modifier key and command + space both fail to function and only by clicking on the QS dock icon (I don't use the menubar icon) brings up the bezel.