<< Solved >> Process "com.apple.parsec-fbf.flush" on Catalina 10.15.2 prevents system from sleeping automatically.

[pastrychef]

Your screenshots are irrelevant. It's more important that Apple itself has to say about his inventions:

CoreParsec.framework

/System/Library/PrivateFrameworks/CoreParsec.framework/Versions/Current/Resources/Info.plist

Bundle identifier: com.apple.siri.parsec.CoreParsec
Privacy - Location Usage Description: Spotlight, Messages, Lookup & Safari Suggestions use your location to provide more accurate local results.

From BSD System Manager's Manual: parsec-fbf is responsible for periodic flush and upload of Siri Search analytics data.

Do you have something really valuable to provide?

You asked about the tasks and I showed you they are running. If it's irrelevant, it's because you asked for irrelevant info.

If you ask irrelevant questions, you get irrelevant answers.

You are a waste of time.

 

[iLikeHackintosh]

You are a waste of time.

Thank you for your opinion. But this far you haven't provided any valuable information. You are telling over and over, that you don't have this issue on your comp. Thats cool and even great. parsec-fbf agent s part of Siri and handles very specific background tasks - sends autonomously data of your searches to to Apple for analytical purposes. Issue with Idle Sleep due the parsec-fbf is specific to 10.15.2, this is not only the Hacks issue but even genuine Macs are affected. I suppose that most Mac users haven't noticed the issue as parsec-fbf agent is disabled when comp runs on battery and it doesn't disable display's sleep. Displays are going black and users might thing that their comps sleep. Issue is easy to figure out on Hacks, as on regular PC there is huge difference when comp is on proper sleep or just the display sleeps.

parsec-fbf runs even when Siri is disabled. Probably Apple uses it for other kind spoofing too now, but that's just the guess. Fact is, that since 10.15.2 parsec-fbf agent has lot of changes.

Would be really great and appreciated if you could provide some really valuable information, rather than telling about your computer and guesses based on that.

I think you should be worried and check why parsec-fbf agent doesn't work on your computer as this is normal part of macOS Catalina. If you get this running on your comp, then we probably have something more to discuss, especially how it affects sleep of your system. But there is nothing new about that if to disable parsec-fbf agent, then Idle Sleep works again.

My concerns is why it prevents especially Idle Sleep since 10.15.2.

 

[pastrychef]

Thank you for your opinion.

Make no mistake. It is not an opinion. It is a fact.

But this far you haven't provided any valuable information. You are telling over and over, that you don't have this issue on your comp. Thats cool and even great. parsec-fbf agent s part of Siri and handles very specific background tasks - sends autonomously data of your searches to to Apple for analytical purposes. Issue with Idle Sleep due the parsec-fbf is specific to 10.15.2, this is not only the Hacks issue but even genuine Macs are affected. I suppose that most Mac users haven't noticed the issue as parsec-fbf agent is disabled when comp runs on battery and it doesn't disable display's sleep. Displays are going black and users might thing that their comps sleep. Issue is easy to figure out on Hacks, as on regular PC there is huge difference when comp is on proper sleep or just the display sleeps.

parsec-fbf runs even when Siri is disabled. Probably Apple uses it for other kind spoofing too now, but that's just the guess. Fact is, that since 10.15.2 parsec-fbf agent has lot of changes.

Would be really great and appreciated if you could provide some really valuable information, rather than telling about your computer and guesses based on that.

I think you should be worried and check why parsec-fbf agent doesn't work on your computer as this is normal part of macOS Catalina. If you get this running on your comp, then we probably have something more to discuss, especially how it affects sleep of your system. But there is nothing new about that if to disable parsec-fbf agent, then Idle Sleep works again.

My concerns is why it prevents especially Idle Sleep since 10.15.2.

If this were a wide spread problem, why is there only a handful of people complaining about it?

I have everything working beautifully. You are the one who has a build with problems. I have nothing to check.

 

[Henties]

It's not a 10.15.2 issue since not everyone is affected by it. So, it has to be some other software and/or hackintosh configuration issue.

Hi I am affected on both of my "oldish" builds. Just reverted back to Mojave and everything is home and dry again.
The problem seem quite widespread, at least that is my opinion.
Greets
Henties

 

[Henties]

@pastrychef Further to my posting under #44 above I just wander what differs between your basic Catalina setup on which autosleep works and those of us on which autosleep does not work ? Could it perhaps be that your use of a different bootloader than Clover, could be the key to the solution ? Presently I am readying a spare SSD with a vanilla installation of
Catalina to see if that makes a difference. Will report back once done and results are known. In my environment I really have no need for Catalina and its quirks however I also do not want to get too far behind with what Apple pushes down our "throats" My adage has always been "if it ain't broken don't fix it". By the same token I also agree that if a problem
does not manifest itself in your environment then your hands are tied as you cannot troubleshoot and offer a solution for something that is not faulty. Now that the path has been paved for a more amicable "tone" in this thread a viable solution may perhaps still be stumbled upon to solve this nagging autosleep irritation with Catalina 10.15.2.
Greets Henties

 

[xavierniu]

@pastrychef Further to my posting under #44 above I just wander what differs between your basic Catalina setup on which autosleep works and those of us on which autosleep does not work ? Could it perhaps be that your use of a different bootloader than Clover, could be the key to the solution ? Presently I am readying a spare SSD with a vanilla installation of
Catalina to see if that makes a difference. Will report back once done and results are known. In my environment I really have no need for Catalina and its quirks however I also do not want to get too far behind with what Apple pushes down our "throats" My adage has always been "if it ain't broken don't fix it". By the same token I also agree that if a problem
does not manifest itself in your environment then your hands are tied as you cannot troubleshoot and offer a solution for something that is not faulty. Now that the path has been paved for a more amicable "tone" in this thread a viable solution may perhaps still be stumbled upon to solve this nagging autosleep irritation with Catalina 10.15.2.
Greets Henties

People who have been affected by its quirk will appreciate your efforts! Looking forward to seeing the result of that!

 

[pastrychef]

@pastrychef Further to my posting under #44 above I just wander what differs between your basic Catalina setup on which autosleep works and those of us on which autosleep does not work ? Could it perhaps be that your use of a different bootloader than Clover, could be the key to the solution ? Presently I am readying a spare SSD with a vanilla installation of
Catalina to see if that makes a difference. Will report back once done and results are known. In my environment I really have no need for Catalina and its quirks however I also do not want to get too far behind with what Apple pushes down our "throats" My adage has always been "if it ain't broken don't fix it". By the same token I also agree that if a problem
does not manifest itself in your environment then your hands are tied as you cannot troubleshoot and offer a solution for something that is not faulty. Now that the path has been paved for a more amicable "tone" in this thread a viable solution may perhaps still be stumbled upon to solve this nagging autosleep irritation with Catalina 10.15.2.
Greets Henties

Not sure if it makes any difference, but I've primarily been using OpenCore on my main system for the last few months.

Do you have Siri enabled?
Does the issue manifest if Siri is disabled?
Does the issue manifest if everything is disabled in System Preferences > Security & Privacy > Analytics & Improvements?
Have you tested on a completely clean install of of 10.15.2?

 

[Henties]

Not sure if it makes any difference, but I've primarily been using OpenCore on my main system for the last few months.

Do you have Siri enabled?
Does the issue manifest if Siri is disabled?
Does the issue manifest if everything is disabled in System Preferences > Security & Privacy > Analytics & Improvements?
Have you tested on a completely clean install of of 10.15.2?

Trying to do a new clean install, it failed by telling me that my image is corrupt. Presently downloading again directly from Appstore, it will take a while, the internet seems overloaded. Will let you know once I managed to complete this task. My mind is presently not too clear, buried my wife on 23 December, finding it still difficult to concentrate for longer periods on end. Will eventually get there.
Greetings Henties

 

[mango1122]

Hi there,

Recently I replaced a network card from BCM94352Z to BCM94360CS2 which has native support, but the hackintosh can't sleep automatically. I got some info by "pmset -g assertions" command.

Assertion status system-wide:
   BackgroundTask                 1
   ApplePushServiceTask           0
   UserIsActive                   1
   PreventUserIdleDisplaySleep    0
   PreventSystemSleep             0
   ExternalMedia                  0
   PreventUserIdleSystemSleep     1
   NetworkClientActive            0
Listed by owning process:
   pid 119(hidd): [0x0000052200098435] 00:00:00 UserIsActive named: "com.apple.iohideventsystem.queue.tickle serviceID:1000007f3 name:AppleUserHIDEventSe product:Convertible 2 TKL eventType:3"
    Timeout will fire in 60 secs Action=TimeoutActionRelease
   pid 426(useractivityd): [0x000006e70001849f] 00:00:01 PreventUserIdleSystemSleep named: "BTLEAdvertisement"
    Timeout will fire in 58 secs Action=TimeoutActionTurnOff
   pid 394(sharingd): [0x0000061e00018459] 00:03:22 PreventUserIdleSystemSleep named: "Handoff"
   pid 316(UserEventAgent): [0x0000017c000b82ed] 00:23:09 BackgroundTask named: "com.apple.parsec-fbf.flush"
    Created for PID: 425.
Kernel Assertions: 0x4=USB
   id=506  level=255 0x4=USB mod=1970/1/1, 8:00 AM description=com.apple.usb.externaldevice.14300000 owner=Convertible 2 TKL
   id=508  level=255 0x4=USB mod=1970/1/1, 8:00 AM description=com.apple.usb.externaldevice.14400000 owner=Razer Mamba Elite
Idle sleep preventers: IODisplayWrangler

Any help will be appreciated! Thanks!!

EDIT:

• My hackintosh could sleep manually by the press of sleep in the Apple icon menu on the top-left conner.
• In the few minutes after login sleep could work.
• Not sleeping in this case means display could be turned off, however the computer won't.
• I notice there are some people talking about "com.apple.parsec-fbf.flush" which is the service for siri (indeed, siri was already disabled on my mac). I think it may be a bug on Catalina 10.15.2.

Bit late on this one. I did the the same swap as you and I nailed the reason for the hack not sleeping cause forgot to disable the on-board Wifi chip (DW1560) in my USB port definition when I swapped it to a PCI based chip. You may want to check that too.

 

[Henties]

Not sure if it makes any difference, but I've primarily been using OpenCore on my main system for the last few months.

Do you have Siri enabled?
Does the issue manifest if Siri is disabled?
Does the issue manifest if everything is disabled in System Preferences > Security & Privacy > Analytics & Improvements?
Have you tested on a completely clean install of of 10.15.2?

I have clean installed and still the same, but I don't really care because this problem manifests itself only if I do not logout
from my single user configuration, therefore if I want autosleep to work without a problem I just logout and voila sleep works. I am not going to trouble shoot this any further because for me logging out and then later maybe even a couple of days later logging in again kicks the machine alive as though nothing happened. Maybe this is the way Apple want us to work from now on, but I don't really think so, I believe the originally live sleep behavior will be restored/fixed by Apple further down the line. The way it works now by logging out when one is done with the machine is no schlepp and fine with me. For me the topic is closed for now, am nevertheless back on Mojave.
Greetings Henties