Newly assigned objects.nosync folder on desktop after updating to 11.3

[chris4565]

Hi everyone,

I just updated to 11.3 and now I have a folder called "Newly assigned objects.nosync" (translated from German) on my desktop. Here's what's in it (the desktop folder is a link to the one shown below and apparently the actual folder doesn't have the ".nosync" part in its name):

So apparently the content is a file called "group.system_default".

What does this mean? Can I just ignore this folder?

Thanks and best wishes
Chris

 

[metabotschafter]

Same here, also with a german system. If you compare the group file with the file currently in use, can you spot the difference? On my mac, the trustd group seems to be missing.
Regards Christian

 

[KALLT]

It says so in the accompanying PDF file:

Configuration files with the suffix “system_default” were edited or customised but the changes were allowed to remain installed. The system_default version of the file is provided to demonstrate what the Apple-supplied version of this file would look like. It is recommended you compare the two and evaluate whether you wish to integrate any changes Apple may have made to the default version.

There is a file called /private/etc/group that deviates from Apple’s default. Apple chose to keep that file there and put the default file in “Relocated Items” and added “system_default” to the name.

Given that Apple leaves you a choice, it is probably fine to just ignore or delete the Relocated Items folder. Otherwise, you’d have to compare the two files:

diff /etc/group /Users/Shared/Relocated\ Items/Configuration/private/etc/group.system_default

and merge the changes manually. In my case, I only have to add this line to /etc/group:

_trustd:*:282:_trustd

 

[metabotschafter]

That´s the line which is missing on my mac as well. If this is a "standard" issue, I am just wondering if it is needed. Especially if it is a default issue. Given the fact that I reinstalled my mac two weeks ago, I am also quit sure the file was not altered.

 

[KALLT]

It might be an oversight on Apple’s part. In my experience, they wouldn’t expose users to such details and instead either update the file or place the default file alongside the modified file (albeit by adding a suffix to the default file, such as “~orig”).

 

[metabotschafter]

I checked the file on my wifes Mac, she did not update yet. Her group does not include trustd as well, beside that her md5 sum is the same as the "modified" one on my Mac. As she uses her computer in a very different fashion, I am also sure that this is a mistake on Apples side.

 

[chris4565]

Ok, thanks for your input. Then I'm glad I'm not alone with this

 

[VineRider]

Exact same issue - US version and I have this file in my relocated items folder on the desktop. Updated a MacBook and a Mac mini and both had the issue.



edit-I just installed an 11.3 VM via parallels as a new install and the group file does have the trustd entry.

 

[metabotschafter]

Exact same issue - US version and I have this file in my relocated items folder on the desktop. Updated a MacBook and a Mac mini and both had the issue.



edit-I just installed an 11.3 VM via parallels as a new install and the group file does have the trustd entry.

Thats interesting, out of curiosity can you provide the md5 sum of the group file in the vm?

 

[neokrish]

Can confirm the same issue (+1 German user), I have a "Relocated Items" folder on the desktop with the group file and doing a diff gives the same result - _trustd:*:282:_trustd

 

[KALLT]

If you are certain that only that line (_trustd:*:282:_trustd) is different, you can simply swap the files:

sudo cp /etc/group /etc/group~previous
sudo mv /Users/Shared/Relocated\ Items/Configuration/private/etc/group.system_default /etc/group

 

[metabotschafter]

If you are certain that only that line (_trustd:*:282:_trustd) is different, you can simply swap the files:

sudo cp /etc/group /etc/group~previous
sudo mv /Users/Shared/Relocated\ Items/Configuration/private/etc/group.system_default /etc/group

I agree , but Bit of an academic question, but why should you of the fresh installed 11.3 os from VineRider does not include trustd as well. I am undecided so far.

 

[mirksde]

Hi everyone,

I just updated to 11.3 and now I have a folder called "Newly assigned objects.nosync" (translated from German) on my desktop. Here's what's in it (the desktop folder is a link to the one shown below and apparently the actual folder doesn't have the ".nosync" part in its name):

View attachment 1764413

So apparently the content is a file called "group.system_default".

What does this mean? Can I just ignore this folder?

Thanks and best wishes
Chris

Same issue in Germany, MacBook Pro with M1 Chip. In my experience as a developer, I would not screw on the system myself at this point. Wait for a fix from Apple.

 

[KALLT]

I agree , but Bit of an academic question, but why should you of the fresh installed 11.3 os from VineRider does not include trustd as well. I am undecided so far.

VineReader said that on a new installation of macOS 11.3 /etc/group does contain that line. So it appears to be true what Apple states in the PDF file that I quoted above, that updating macOS to 11.3 does not overwrite the existing file, even though the default changed.

If you check the Directory Service, you will also see that the _trustd group exists and is correctly configured regardless whether it is mentioned in /etc/group:

% dscl . -read /Groups/_trustd
AppleMetaNodeLocation: /Local/Default
GeneratedUID: ABCDEFAB-CDEF-ABCD-EFAB-CDEF0000011A
GroupMembers: FFFFEEEE-DDDD-CCCC-BBBB-AAAA0000011A
GroupMembership: _trustd
Password: *
PrimaryGroupID: 282
RealName: trustd
RecordName: _trustd
RecordType: dsRecTypeStandard:Groups

In other words, it is likely fine to do nothing (and hope that Apple resolved it somehow) or update /etc/group manually.

 

[metabotschafter]

VineReader said that on a new installation of macOS 11.3 /etc/group does contain that line. So it appears to be true what Apple states in the PDF file that I quoted above, that updating macOS to 11.3 does not overwrite the existing file, even though the default changed.

I am sorry, you are right

 

[Adydog]

Non-developer here...

I ran the 'diff' on 'group.system_default' and got _trustd:*:282:_trustd

So, what should I do now?

Thanks

 

[chris4565]

So I'm a real noob when it comes to system files apparently because I can't even find the "original" file. Can someone tell me where it is so that I can compare it?

 

[VineRider]

I reinstalled macOS on both my MacBook Pro and Mac mini by going into recovery mode and reinstalling from the recovery partition. This reinstall updated the group file to include the trustd entry in the group file at private/etc. It also put the old group file without the trustd entry in the recovered items folder on the desktop.

No settings were lost so this seems like a fairly easy way to solve the problem. I am not a expert in command line work on the Mac, so this worked for me. I would expect that just adding the entry to the existing group file and rebooting would work, but I was not sure how to do that via command line so the reinstall fixed the issue for me.

Cheers,
VineRider

 

[KALLT]

So I'm a real noob when it comes to system files apparently because I can't even find the "original" file. Can someone tell me where it is so that I can compare it?

Don’t worry about it. According to the header of /etc/group, that file is only needed in single-user mode, not in normal operation of macOS. In all other cases, the Directory Service is used (as I mentioned above), which seems to be correct as of macOS 11.3 as well.

If it were crucial, Apple would have updated the file during the upgrade process, rather than let the user deal with it.

 

[metabotschafter]

Based on KALLT‘s feedback I will leave it as it is for now, given the fact that trustd process seems to be fine.

 

[Bogdan Bink]

That´s the line which is missing on my mac as well. If this is a "standard" issue, I am just wondering if it is needed. Especially if it is a default issue. Given the fact that I reinstalled my mac two weeks ago, I am also quit sure the file was not altered.

Hi, same here. Only line missing is
_trustd:*:282:_trustd.

Apple could give us more insight on what to do as I have no idea why this line is there (my guess is that it appears because I once used the single mode boot.)

But how do I know, Apple, whether this line is needed or not? As I did not add it myself, I have no clue.

 

[VineRider]

Don’t worry about it. According to the header of /etc/group, that file is only needed in single-user mode, not in normal operation of macOS. In all other cases, the Directory Service is used (as I mentioned above), which seems to be correct as of macOS 11.3 as well.

If it were crucial, Apple would have updated the file during the upgrade process, rather than let the user deal with it.

What is single user mode? I only have one user account on my MacBook, is this what you are referring to?

 

[metabotschafter]

What is single user mode? I only have one user account on my MacBook, is this what you are referring

This is „reduced“ mode where non critical parts of the OS stay unlaunched. It is not related to the number of user accounts.

 

[VineRider]

This is „reduced“ mode were non critical parts of the OS stay unlaunched. It is not related to the number of user accounts.

Thanks for the explanation!

Cheers,
VineRider

 

[ralphthemagi]

I suspect this is related to the issue on Nov 12, 2020 where trustd was trying to connect to oscp.apple.com to validate security certificates, but that server was effectively DDoS'd and crashed. The result was that every internet connected Mac basically ground to a halt when trying to do even simple things like open an app, since trustd was timing out while trying to validate a certificate.

Single user mode is more than just a reduced mode. It's literally just boots you to the command line.

My best guess is that this is included as part of a new default, which is then later removed through some other process.