DoubleCommand needs to be reinstalled after each reboot on Yosemite

[Thomas-Z]

Everything seems to be working fine on Yosemite but it stops to work after each reboot.

A reinstall fixes everything until the next reboot.

[tigredanky]

Yeah, just started experiencing this with the update. Pucha.

[tsiger]

Pucha indeed.

[zbyna]

Same problem :(

[zbyna]

There is a very good alternative which works even after restart:
https://pqrs.org/osx/karabiner/

[tigredanky]

Thanks zbyna, I've got a post on settings for it, too. It still gets wiped after some restarts, though.

http://foxytigre.com/geekout/pc-keyboard-logitech-mk700-mac-using-karabiner/

[andkrup]

Got the same problem here as well

You don't need to reinstall DoubleCommand, just run it manually..

sudo /Library/StartupItems/DoubleCommand/DoubleCommand

[kleuter]

Same issue, workaround by fuzzyflop works

[mbaltaks]

I'm not 100% sure why it won't load automatically, but it could be that recent versions of Mac OS X don't use the /Library/StartupItems folder anymore.

There is a login.command file in /Library/StartupItems/DoubleCommand which was designed to be run as a login item to allow multi-user preferences for DoubleCommand. If you were to add:

sudo /Library/StartupItems/DoubleCommand/DoubleCommand start

after the sysctl=/usr/sbin/sysctl line, then that might ease the pain, but you'd still need to enter your password each login.

[mbaltaks]

Actually, has anyone tried sudo rsync -av /Library/StartupItems/DoubleCommandDoubleCommand.kext /System/Library/Extensions?

[enjay314]

I think I got it working under Yosemite after #mbaltaks mentioned that it might not use StartupItems.

I made a LaunchDaemon by making a new com.doublecommand.plist (contents below) and putting it in /Library/LaunchDaemons.

In Terminal I used sudo nano /Library/LaunchDaemons/com.doublecommand.plist to make my new document and didn't have to mess with permissions later.

I suppose if you make a plain text file elsewhere and drag it to LaunchDaemons, you have to make sure the owner is root:wheel (sudo chown root:wheel /Library/LaunchDaemons/com.doublecommand.plist) and permissions are 755 (sudo chmod 755 /Library/LaunchDaemons/com.doublecommand.plist).

After things were in place, I ran this command:
sudo launchctl load -w /Library/LaunchDaemons/com.doublecommand.plist
then restarted and everything seemed to work.

This is my com.doublecommand.plist file:

<?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>com.doublecommand.plist</string>
<key>ProgramArguments</key>
<array>
  <string>/Library/StartupItems/DoubleCommand/DoubleCommand</string>
<string>start</string>
</array>
    <key>RunAtLoad</key>
    <true/>
    <key>KeepAlive</key>
    <true/>
</dict>
</plist>

[kleuter]

enjay314, anyway to have it directly in the setup ?

[richard-griffiths]

mbaltaks comment from May 18 works to fix this in El Capitan 11.11. you will need to insert a forward slash in the path between the two doublecommands, like this:
sudo rsync -av /Library/StartupItems/DoubleCommand/DoubleCommand.kext /System/Library/Extensions

[tobsn]

fyi, all those fixes don't work on the new magic keyboard. the only way to make it work for me is to remove the prefpane and then install the pkg again.

same applies to karabiner app btw. it can't handle fn remapping on the new keyboard.

[tobsn]

Created a separate issue with a bounty attached to it:
#25