Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Start at login does nothing in 10.8 #831

Closed
skurfer opened this issue Apr 19, 2012 · 12 comments
Closed

Start at login does nothing in 10.8 #831

skurfer opened this issue Apr 19, 2012 · 12 comments
Assignees
Milestone

Comments

@skurfer
Copy link
Member

@skurfer skurfer commented Apr 19, 2012

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

@ghost ghost assigned skurfer May 4, 2012
@mickeys
Copy link

@mickeys mickeys commented May 19, 2012

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

@skurfer
Copy link
Member Author

@skurfer skurfer commented May 21, 2012

Confirmed. Thanks for pointing this out.

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

@skurfer skurfer closed this as completed May 21, 2012
@skurfer skurfer reopened this Jun 14, 2012
@ant0ineg
Copy link

@ant0ineg ant0ineg commented Aug 3, 2012

Any updates on this issue?

@iandol
Copy link

@iandol iandol commented Aug 7, 2012

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
Copy link

@ahmednuaman ahmednuaman commented Aug 7, 2012

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

@iandol
Copy link

@iandol iandol commented Aug 7, 2012

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
Copy link
Member Author

@skurfer skurfer commented Aug 8, 2012

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
Copy link

@iandol iandol commented Aug 8, 2012

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

@tiennou
Copy link
Member

@tiennou tiennou commented Aug 9, 2012

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
Copy link
Member Author

@skurfer skurfer commented Aug 12, 2012

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
Copy link

@Sesquipedalian Sesquipedalian commented Aug 16, 2012

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
Copy link

@iwhisperer iwhisperer commented Aug 18, 2012

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

8 participants