I'm having problems finding were can I disable Skype auto-start

Discussion in 'Mac Apps and Mac App Store' started by vodkaPT, Apr 13, 2013.

  1. vodkaPT macrumors member

    Joined:
    Jun 10, 2012
    Location:
    Lisbon, Portugal
    #1
    Hi all,

    This may be a silly question, but I'm feeling impotent to stop skype from auto start in my mac pc.

    I even google it and I followed the skype help:

    https://support.skype.com/en/faq/FA...or-mac-from-starting-when-i-start-my-computer

    But skype is not listed on my pc auto start applications.

    I don't know what to do to prevent skype from auto start every time I turn on my PC. I'm even thinking in remove skype because this is being a very annoying problem.

    Any help?

    thanks
     
  2. gj.george macrumors newbie

    Joined:
    Sep 25, 2012
    #2
    Hello!

    It's quite easy to do actually.
    Go to the skype icon sitting on your dock, and right click on it.
    From there go to Options, and simply deselect Open at Login.
    That's it!

    Hope this helps.
     

    Attached Files:

  3. bdrake47 macrumors regular

    Joined:
    Jul 28, 2012
    #3
    That is what the Skype Help link the OP posted said to do also, which the OP said he followed. That was the first method listed.

    The second was to remove from Login Items in Sys. Prefs | Users.

    Surely it has to be one of those two solutions, where else could Skype bury a startup command?
     
  4. patte, Jul 23, 2014
    Last edited: Jul 23, 2014

    patte macrumors newbie

    patte

    Joined:
    Sep 22, 2009
    #4
    I'm having this problem, too lately.

    Of course the former two things where the first ones I checked for. In addition I checked everything in these two locations:
    Code:
    ~/Library/LaunchAgents/
    /Library/LaunchAgents/
    Still nothing, next I deactivated my usual suspects from starting up at the login (Hazel, Keyboard Maestro). Nothing.

    The console gave me little clues: http://cl.ly/Wilf/skype.log

    Code:
    2014-07-23 8:36:42.595 AM gkbisd[204]: Unable to collect cdhash for /Applications/Skype.app (error code 100024)
    2014-07-23 8:36:42.734 AM Skype[15399]: BUG in libdispatch: 14A298i - 993 - 0xe
    2014-07-23 8:36:42.915 AM Skype[15399]: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.0 instead of 10.10.0. Use NSProcessInfo's operatingSystemVersion property to get correct system version number.
    Call location:
    2014-07-23 8:36:42.915 AM Skype[15399]: 0   CarbonCore                          0x9bbafbbf ___Gestalt_SystemVersion_block_invoke + 135
    2014-07-23 8:36:42.916 AM Skype[15399]: 1   libdispatch.dylib                   0x924736d0 _dispatch_client_callout + 50
    2014-07-23 8:36:42.916 AM Skype[15399]: 2   libdispatch.dylib                   0x9247365e dispatch_once_f + 148
    2014-07-23 8:36:42.916 AM Skype[15399]: 3   libdispatch.dylib                   0x924745b5 dispatch_once + 31
    2014-07-23 8:36:42.916 AM Skype[15399]: 4   CarbonCore                          0x9bb4209c _Gestalt_SystemVersion + 1050
    2014-07-23 8:36:42.916 AM Skype[15399]: 5   CarbonCore                          0x9bb41c4d Gestalt + 150
    2014-07-23 8:36:42.916 AM Skype[15399]: 6   Skype                               0x00ed020c Skype + 15528460
    2014-07-23 8:36:43.946 AM Skype[15399]: Failed to create AccessSession
    2014-07-23 8:36:45.041 AM Skype[15399]: Failed to create AccessSession
    2014-07-23 8:38:18.112 AM Skype[15399]: Failed to get contents of directory "/Users/patte/Library/Logs/Skype". The file “Skype” couldn’t be opened because there is no such file.
    I managed to get this via Console.app, but don't know if it's useful:

    [​IMG]

    … and this via another app:

    [​IMG]

    … and even after completely uninstalling Skype (with Hazel) and digging for relicts with EasyFind I still got this lovely screen after booting up:

    [​IMG]

    Anyone have an idea on how to track something like this? When I have some more time I'll probably going to remove every launch agent and login item in the user preferences to see if this still occurs.

    PS: This also happened on OS X 10.9.
     

Share This Page