![]() ![]() ![]() Installed package that Composer saved to the desktop. Packaged this with composer and deployed to the same test Mac. ![]() Signed in as a different user, still no alert. No notification for Slack to make changes. Simple drag and drop to Applications folder after mounting the dmg. I tried churcht's script and it didn't work so I tried this:ĭownloaded Slack from their website. To see if the environment variable is actually there Then try opening Slack and see if it gets rid of that annoying admin prompt. # Create PLIST file that sets an environment variableįile="/Library/LaunchDaemons/"Ĭom.COMPANYNAME.disable-slack-auto-updatesĪfter you create the plist file on a test machine, you should log out and back in. Here is a script I'm working on this morning for this in my environment. The best way to do this is to implement this environment variable SLACK_NO_AUTO_UPDATES No system.log output when i press cancel, neither when i enter the admin credentials. May 10 11:58:31 SecurityAgent: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set set a breakpoint on _dispatch_bug_deprecated to debug May 10 11:58:30 SecurityAgent: objc: Class TKTokenRefCtkd is implemented in both /System/Library/Frameworks/amework/Versions/A/Security (0x7fff9712afd0) and /System/Library/Frameworks/amework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10522fd10). May 10 11:58:30 SecurityAgent: objc: Class TKTokenRefImpl is implemented in both /System/Library/Frameworks/amework/Versions/A/Security (0x7fff9712afa8) and /System/Library/Frameworks/amework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10522fce8). I do get an output from terminal saying: May 10 11:58:30 Slack: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set set a breakpoint on _dispatch_bug_deprecated to debug But the pop-up on every start is still anoying. If you click on cancel, the app still starts. When they update Slack (which is simply a new installation of the most recent client), it always shows the dialogue mentioned in the subject or attached screenshot on every app start, until someone types in admin creds. When the problem occurs again, follow the steps above to remove only the last login item you added.We're currently running our mac's with automatic install scripts via jamf. If this solves the problem, open Login Items settings again, add the login items one at a time, and restart your Mac after adding each one. Select all of the login items, then click the Remove button. Make a list of the login items in the Open at Login list-you’ll need to remember them later. On your Mac, choose Apple menu > System Settings, click General in the sidebar, then click Login Items on the right. If the issue continues, a login item may be the issue: If the issue doesn't continue in safe mode, restart your Mac as you normally would and check for the issue again. Follow the steps here: Start up your Mac in safe mode - Apple Support Starting up your Mac in safe mode can help you identify whether the issues you’re experiencing are caused by software that loads as your Mac starts up. If that doesn't resolve the issue, try booting into safe mode. Shut down or restart your Mac - Apple Support To get started, we recommend trying to restart your Mac. There are some basic troubleshooting steps that may resolve the issue. ![]()
0 Comments
Leave a Reply. |