Sidebar Sidebar
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.

System preferences software update badge

camelia said:
Very Good, But I did not understand anything....

Why do I have to run the terminal command?

Code: 
chmod 755 die_catalina_die
Click to expand...

The chmod command tells the OS that you want to give the shell script file permissions so that it can be executed. The below link gives more information on file permissions if you are interested. By the way, if you are not aware of this, macOS is based on UNIX and that is what the link refers to when it explains file permissions.

www.tutorialspoint.com

Unix / Linux - File Permission / Access Modes

Unix / Linux - File Permission / Access Modes - In this chapter, we will discuss in detail about file permission and access modes in Unix. File ownership is an important component of Unix that provides a secure method for storing files. Every file in Unix has the following attributes ?
www.tutorialspoint.com www.tutorialspoint.com

camelia said:
How the terminal command would know the location of the .txt file?
I prefer using the extension ".sh" to make it clear it is a shell script

So the code above will be the same??

Thanks
Camelia
Click to expand...

You can put whatever extension you want on the file, personally I prefer use the .sh extension. Here is how I would suggest the easiest way to do the chmod command:
  1. When you create the die_catalina_die.sh in TextEdit make sure you do TextEdit->Format->Make Plain Text.
  2. Once you have created and saved the die_catalina_die.sh file, open a Finder window to the location where you saved the file.
  3. Open the Terminal app.
  4. in the Terminal window, enter: chmod 755
  5. Put a space after chmod 755.
  6. From the Finder window you opened in step 2, drag from the Finder window die_catalina_die.sh to the Terminal window.
  7. Press the enter key.
When you want to execute the shell script all you have to do is open a Finder window to the location where the shell script file die_catalina_die.sh is stored and double-click on it with the mouse.
 
  • Love
Reactions: camelia
Quick question: does installing this security update from May only affect System Preferences and its notification badges, or do I then start getting the Notification Center notifications that I need to update again? Because those are the worst part, I can live with System Preferences not being in my Dock.
 
The most annoying part is that the badge comes back every other day now, even I did not open the Software Update...
Apple can keep the cancerous Catalina...The more annoying it gets, the less likely I will touch it.
 
  • Like
Reactions: Mr Todhunter
Taz Mangus said:
The chmod command tells the OS that you want to give the shell script file permissions so that it can be executed. The below link gives more information on file permissions if you are interested. By the way, if you are not aware of this, macOS is based on UNIX and that is what the link refers to when it explains file permissions.

www.tutorialspoint.com

Unix / Linux - File Permission / Access Modes

Unix / Linux - File Permission / Access Modes - In this chapter, we will discuss in detail about file permission and access modes in Unix. File ownership is an important component of Unix that provides a secure method for storing files. Every file in Unix has the following attributes ?
www.tutorialspoint.com www.tutorialspoint.com



You can put whatever extension you want on the file, personally I prefer use the .sh extension. Here is how I would suggest the easiest way to do the chmod command:
  1. When you create the die_catalina_die.sh in TextEdit make sure you do TextEdit->Format->Make Plain Text.
  2. Once you have created and saved the die_catalina_die.sh file, open a Finder window to the location where you saved the file.
  3. Open the Terminal app.
  4. in the Terminal window, enter: chmod 755
  5. Put a space after chmod 755.
  6. From the Finder window you opened in step 2, drag from the Finder window die_catalina_die.sh to the Terminal window.
  7. Press the enter key.
When you want to execute the shell script all you have to do is open a Finder window to the location where the shell script file die_catalina_die.sh is stored and double-click on it with the mouse.
Click to expand...

Hello, Something I am doing wrong but I don't know what it is

Taz Mangus said:
  1. When you create the die_catalina_die.sh in TextEdit make sure you do TextEdit->Format->Make Plain Text.
Click to expand...

01Code.jpg


Taz Mangus said:
2. Once you have created and saved the die_catalina_die.sh file, open a Finder window to the location where you saved the file.​
​
3. Open the Terminal app.​
​
4. in the Terminal window, enter: chmod 755​
​
5. Put a space after chmod 755.​
​
6. From the Finder window you opened in step 2, drag from the Finder window die_catalina_die.sh to the Terminal window.​
​
Click to expand...

02Code.png


Taz Mangus said:
7. Press the enter key.​
Click to expand...

Nothing Happens!! 😭😭😭

And If I type in terminal the code, the update badge is there!!!!

03Code.png


Thanks
Came

PS: I would like to know how a shell script works any other easy example?
 
B4U said:
The badge is getting quite aggressive now.
It is showing up every day.
Perhaps it is time to remove system preference from the dock.
Click to expand...

I recently had the exact opposite experience: After I installed Safari 14 through the Software Update on my Late 2008 MacBook, it showed me that there is a Catalina update available as well but then it went away without any interventions on my part. I am assuming that's because Big Sur is on its way already so there is no point to push Catalina.
 
B4U said:
The badge is getting quite aggressive now.
It is showing up every day.
Perhaps it is time to remove system preference from the dock.
Click to expand...
Keep the dock small so you will almost not see the badge
tinybadge.jpg
I do not mind having it because this way I know if I have other updates
But if I open Software update I get a clean window 😊
NoCatalina.jpg
 
  • Like
Reactions: B4U
avz said:
I recently had the exact opposite experience: After I installed Safari 14 through the Software Update on my Late 2008 MacBook, it showed me that there is a Catalina update available as well but then it went away without any interventions on my part. I am assuming that's because Big Sur is on its way already so there is no point to push Catalina.
Click to expand...
Or maybe they realized Catalina was a big mistake?! LOL
 
  • Haha
Reactions: B4U
I have done it again since a few days ago and it works (I have macOS Mojave though).

1) QUIT System Preferences

2) in terminal run:
sudo softwareupdate --ignore "macOS Catalina"

3) in terminal run:
defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier

4) in terminal run:
softwareupdate --list
 
  • Like
  • Love
Reactions: camelia and B4U
nkarafo said:
I have done it again since a few days ago and it works (I have macOS Mojave though).

1) QUIT System Preferences

2) in terminal run:
sudo softwareupdate --ignore "macOS Catalina"

3) in terminal run:
defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier

4) in terminal run:
softwareupdate --list
Click to expand...

I believe you actually don't need step 2), it will work without it.
 
avz said:
I believe you actually don't need step 2), it will work without it.
Click to expand...
I agree, because step 2 in terminal gives you
"Ignoring software updates is deprecated.
The ability to ignore individual updates will be removed in a future release of macOS."
 
nkarafo said:
I have done it again since a few days ago and it works (I have macOS Mojave though).

1) QUIT System Preferences

2) in terminal run:
sudo softwareupdate --ignore "macOS Catalina"

3) in terminal run:
defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier

4) in terminal run:
softwareupdate --list
Click to expand...

Didn't try this yet because I'm using another way to stop it and still it works I'm good with it
but I will keep this in mind. Thanks
 
nkarafo said:
I have done it again since a few days ago and it works (I have macOS Mojave though).

1) QUIT System Preferences

2) in terminal run:
sudo softwareupdate --ignore "macOS Catalina"

3) in terminal run:
defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier

4) in terminal run:
softwareupdate --list
Click to expand...
This method worked like magic.
The badge has not shown up again until yesterday for Security Update 2020-005 10.14.6, which is expected.
Thank you for sharing.
 
Last edited:
B4U said:
This method worked like magic.
The badge has not shown up again until yesterday for Security Update 2020-005 10.14.6
Thank you!
Click to expand...
Good! Have you tried after the Security Update 2020-005 , if you updated of course,
to see if it didn’t break software update showing Catalina again when you check?
 
B4U said:
The red badge for Cancerlina came right back if I check.
Click to expand...
😟 Just the annoying badge or Cancerlina notification as well?
In case it’s because we need to substitute the Software update framework again
 
katbel said:
😟 Just the annoying badge or Cancerlina notification as well?
In case it’s because we need to substitute the Software update framework again
Click to expand...
So far, only when I go to System Preference to check Software Updates, Cancerlina is back along with the red badge.
It has only been 1 day, so I am not sure what will happen if I don't disturb the hornets' nest.
 
  • Wow
Reactions: katbel
B4U said:
So far, only when I go to System Preference to check Software Updates, Cancerlina is back along with the red badge.
It has only been 1 day, so I am not sure what will happen if I don't disturb the hornets' nest.
Click to expand...
Thanks for reporting it
We need to remove and go back to the safer framework, lot of work too :rolleyes:
 
  • Like
Reactions: B4U
  • Wow
Reactions: camelia
Hello, this walk-through works before the Security supplemental update, So I have to repeat it?

Or is not working anymore?
nkarafo said:
I have done it again since a few days ago and it works (I have macOS Mojave though).


1) QUIT System Preferences


2) in terminal run:

sudo softwareupdate --ignore "macOS Catalina"


3) in terminal run:

defaults delete com.apple.preferences.softwareupdate LatestMajorOSSeenByUserBundleIdentifier


4) in terminal run:

softwareupdate --list
Click to expand...
katbel said:
Thanks for reporting it
We need to remove and go back to the safer framework, lot of work too :rolleyes:
Click to expand...

What do you mean with "We need to remove and go back to the safer framework, lot of work too"?

Thanks
Camelia
 
camelia said:
Or is not working anymore?
What do you mean with "We need to remove and go back to the safer framework, lot of work too"?
Click to expand...

If you have done only the supplemental update you are good to go.
I was referring when you apply the Security Update 2020-005, then you need to substitute the new Software update framework with the old one that you kept from Security Update 2020-002 as suggested here #18,496
 
Last edited:
  • Love
Reactions: camelia
katbel said:
If you have done only the supplemental update you are good to go.
I was referring when you apply the Security Update 2020-005, then you need to substitute the new Software update framework with the old one that you kept from Security Update 2020-002 as suggested here #18,496
Click to expand...

Thank you :)
 
You must log in or register to reply here.
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.
Top Bottom
Back