Solved

Prevent "Slack wants to make changes"

Forum|Forum|6 years ago
May 10, 2019
28 replies
291 views

+3

lxfl
New Contributor

Hi,

we're currently running our mac's with automatic install scripts via jamf.
Our users don't have admin privilegues.

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.
If you click on cancel, the app still starts. But the pop-up on every start is still anoying.

I do get an output from terminal saying:

May 10 11:58:30 Slack[21065]: 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[21094]: objc[21094]: Class TKTokenRefImpl is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fff9712afa8) and /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10522fce8). One of the two will be used. Which one is undefined.
May 10 11:58:30 SecurityAgent[21094]: objc[21094]: Class TKTokenRefCtkd is implemented in both /System/Library/Frameworks/Security.framework/Versions/A/Security (0x7fff9712afd0) and /System/Library/Frameworks/Security.framework/Versions/A/MachServices/SecurityAgent.bundle/Contents/MacOS/SecurityAgent (0x10522fd10). One of the two will be used. Which one is undefined.
May 10 11:58:31 SecurityAgent[21094]: DEPRECATED USE in libdispatch client: dispatch source activated with no event handler set; set a breakpoint on _dispatch_bug_deprecated to debug

No system.log output when i press cancel, neither when i enter the admin credentials.

Any ideas how i can fix that?

Best answer by anverhousseini

I think the issue with this dialogue is the ownership of the Slack.app bundle. Just change the ownership to the current logged in user:

chown -R $(scutil <<< "show State:/Users/ConsoleUser" | awk -F': ' '/[[:space:]]+Name[[:space:]]:/ { if ( $2 != "loginwindow" ) { print $2 }}'):staff "/Applications/Slack.app"

You could add this snippet to your install script or as a postinstall script in a package.

Show first post

1
2

Forum|pagination.label 2 / 2

S

+2

Siggloo
New Contributor
Forum|Forum|2 years ago
May 21, 2023

Hi,

I have one question. This script is running great on Intel chips, but on M1 it will upgrade (if you check about, it will show the latest version) but helper will still continue to prompt and once you enter the admin credentials it will restart and upgrade again, and then it will stop. Does anyone else experience this problem?

Did you get this sorted out? Just found this tread and is about to test the script :)

Like

D

+2

david_maestre
New Contributor
Forum|Forum|2 years ago
May 21, 2023

I personally use "installomator.sh" to install slack. It installs the web version. I have a configuration profile setup for auto-updates too and it suppresses the need for admin credentials on every update. Just restart Slack and done.

Like

masyed
New Contributor
Forum|Forum|2 years ago
July 11, 2023

I think the issue with this dialogue is the ownership of the Slack.app bundle. Just change the ownership to the current logged in user:

chown -R $(scutil <<< "show State:/Users/ConsoleUser" | awk -F': ' '/[[:space:]]+Name[[:space:]]:/ { if ( $2 != "loginwindow" ) { print $2 }}'):staff "/Applications/Slack.app"

You could add this snippet to your install script or as a postinstall script in a package.

Still its asking for admin creds , Not accepting user login details. Staff group has been updated with read and write permission

Like

1
2

Forum|pagination.label 2 / 2

Sign up

Login with SSO

Login to the community

Login with SSO

Scanning file for viruses.

This file cannot be downloaded