home.social

#activitymonitor — Public Fediverse posts

Live and recent posts from across the Fediverse tagged #activitymonitor, aggregated by home.social.

  1. Due to updated on #macOS Sonoma or recent changes to #iCloud #encryption, some systems start running hot from overworked cores. I’ve found a common culprit on several machines: the address book and calendar daemons failing to sync with iCloud.

    If #ActivityMonitor shows that’s your issue too, a quick fix is to go to your iCloud settings and turn off calendar and contact syncing. After a few minutes or a reboot, turn them back on.

    That fixes the problem without data loss for me. YMMV.

  2. Due to updated on #macOS Sonoma or recent changes to #iCloud #encryption, some systems start running hot from overworked cores. I’ve found a common culprit on several machines: the address book and calendar daemons failing to sync with iCloud.

    If #ActivityMonitor shows that’s your issue too, a quick fix is to go to your iCloud settings and turn off calendar and contact syncing. After a few minutes or a reboot, turn them back on.

    That fixes the problem without data loss for me. YMMV.

  3. Due to updated on #macOS Sonoma or recent changes to #iCloud #encryption, some systems start running hot from overworked cores. I’ve found a common culprit on several machines: the address book and calendar daemons failing to sync with iCloud.

    If #ActivityMonitor shows that’s your issue too, a quick fix is to go to your iCloud settings and turn off calendar and contact syncing. After a few minutes or a reboot, turn them back on.

    That fixes the problem without data loss for me. YMMV.

  4. Is there a way to profile energy consumption by individual apps over longer durations—say 48 hours—in #macOS? #ActivityMonitor only shows the past 12 hours.

    #Apple

  5. Is there a way to profile energy consumption by individual apps over longer durations—say 48 hours—in #macOS? #ActivityMonitor only shows the past 12 hours.

    #Apple

  6. Is there a way to profile energy consumption by individual apps over longer durations—say 48 hours—in ? only shows the past 12 hours.

  7. Is there a way to profile energy consumption by individual apps over longer durations—say 48 hours—in #macOS? #ActivityMonitor only shows the past 12 hours.

    #Apple

  8. Is there a way to profile energy consumption by individual apps over longer durations—say 48 hours—in #macOS? #ActivityMonitor only shows the past 12 hours.

    #Apple

  9. @RogueAmoeba Also worth pointing out that, if I wasn’t an experienced Mac troubleshooter who knows about force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor, I would have no choice but to reboot my Mac in order to get things working right. That's just wrong. One of the main reasons for the very existence of #macOS is that our devices don't have to be rebooted all the time. Yet either you know all kinds of obscure workarounds or you have no choice but to reboot.

  10. @RogueAmoeba Also worth pointing out that, if I wasn’t an experienced Mac troubleshooter who knows about force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor, I would have no choice but to reboot my Mac in order to get things working right. That's just wrong. One of the main reasons for the very existence of #macOS is that our devices don't have to be rebooted all the time. Yet either you know all kinds of obscure workarounds or you have no choice but to reboot.

  11. @RogueAmoeba Also worth pointing out that, if I wasn’t an experienced Mac troubleshooter who knows about force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor, I would have no choice but to reboot my Mac in order to get things working right. That's just wrong. One of the main reasons for the very existence of #macOS is that our devices don't have to be rebooted all the time. Yet either you know all kinds of obscure workarounds or you have no choice but to reboot.

  12. @RogueAmoeba Also worth pointing out that, if I wasn’t an experienced Mac troubleshooter who knows about force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor, I would have no choice but to reboot my Mac in order to get things working right. That's just wrong. One of the main reasons for the very existence of #macOS is that our devices don't have to be rebooted all the time. Yet either you know all kinds of obscure workarounds or you have no choice but to reboot.

  13. @RogueAmoeba Also worth pointing out that, if I wasn’t an experienced Mac troubleshooter who knows about force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor, I would have no choice but to reboot my Mac in order to get things working right. That's just wrong. One of the main reasons for the very existence of #macOS is that our devices don't have to be rebooted all the time. Yet either you know all kinds of obscure workarounds or you have no choice but to reboot.

  14. I was initially tempted to blame a bug in one of my third-party @RogueAmoeba audio tools, namely either #SoundSource or #Loopback. But I knew very well it was actually more likely to be macOS itself.

    Ended up force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor and… sure enough, things were back to normal after that.

    Today’s Apple for ya. A picture of software unreliability and untrustworthiness.

    2/2

  15. I was initially tempted to blame a bug in one of my third-party @RogueAmoeba audio tools, namely either #SoundSource or #Loopback. But I knew very well it was actually more likely to be macOS itself.

    Ended up force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor and… sure enough, things were back to normal after that.

    Today’s Apple for ya. A picture of software unreliability and untrustworthiness.

    2/2

  16. I was initially tempted to blame a bug in one of my third-party @RogueAmoeba audio tools, namely either #SoundSource or #Loopback. But I knew very well it was actually more likely to be macOS itself.

    Ended up force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor and… sure enough, things were back to normal after that.

    Today’s Apple for ya. A picture of software unreliability and untrustworthiness.

    2/2

  17. I was initially tempted to blame a bug in one of my third-party @RogueAmoeba audio tools, namely either #SoundSource or #Loopback. But I knew very well it was actually more likely to be macOS itself.

    Ended up force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor and… sure enough, things were back to normal after that.

    Today’s Apple for ya. A picture of software unreliability and untrustworthiness.

    2/2

  18. I was initially tempted to blame a bug in one of my third-party @RogueAmoeba audio tools, namely either #SoundSource or #Loopback. But I knew very well it was actually more likely to be macOS itself.

    Ended up force-quitting #coreaudiod and #systemsoundserverd in #ActivityMonitor and… sure enough, things were back to normal after that.

    Today’s Apple for ya. A picture of software unreliability and untrustworthiness.

    2/2

  19. Not just my third-party external Logitech camera, but even the built-in camera in my new Apple Studio Display refused to work. Just a black picture instead. Both cameras worked fine in QT Player, Teams, Zoom, etc. But in the one app where I needed them to work (FaceTime), them wouldn’t. Maybe there is some kind of background process I can force-quit/relaunch via Terminal or #ActivityMonitor to avoid a reboot. Can’t find anything useful about this new #Ventura bug online, though. Sigh.

  20. Not just my third-party external Logitech camera, but even the built-in camera in my new Apple Studio Display refused to work. Just a black picture instead. Both cameras worked fine in QT Player, Teams, Zoom, etc. But in the one app where I needed them to work (FaceTime), them wouldn’t. Maybe there is some kind of background process I can force-quit/relaunch via Terminal or #ActivityMonitor to avoid a reboot. Can’t find anything useful about this new #Ventura bug online, though. Sigh.

  21. Not just my third-party external Logitech camera, but even the built-in camera in my new Apple Studio Display refused to work. Just a black picture instead. Both cameras worked fine in QT Player, Teams, Zoom, etc. But in the one app where I needed them to work (FaceTime), them wouldn’t. Maybe there is some kind of background process I can force-quit/relaunch via Terminal or #ActivityMonitor to avoid a reboot. Can’t find anything useful about this new #Ventura bug online, though. Sigh.

  22. Not just my third-party external Logitech camera, but even the built-in camera in my new Apple Studio Display refused to work. Just a black picture instead. Both cameras worked fine in QT Player, Teams, Zoom, etc. But in the one app where I needed them to work (FaceTime), them wouldn’t. Maybe there is some kind of background process I can force-quit/relaunch via Terminal or #ActivityMonitor to avoid a reboot. Can’t find anything useful about this new #Ventura bug online, though. Sigh.

  23. Not just my third-party external Logitech camera, but even the built-in camera in my new Apple Studio Display refused to work. Just a black picture instead. Both cameras worked fine in QT Player, Teams, Zoom, etc. But in the one app where I needed them to work (FaceTime), them wouldn’t. Maybe there is some kind of background process I can force-quit/relaunch via Terminal or #ActivityMonitor to avoid a reboot. Can’t find anything useful about this new #Ventura bug online, though. Sigh.