Strange problem after updating to MacOS 14.4 - bad file descriptor

markusloffler commented 2 months ago

After updating to MacOS 14.4, connection to cups fails with "Bad file descriptor". I tried to find the error and made the following observations:

cupsctl prints "cupsctl: Unable to connect to server: Bad file descriptor"
cupsctl -h localhost:631 works
For some seconds after restarting cupsd (sudo launchctl unload /System/Library/LaunchDaemons/org.cups.cupsd.plist; sleep 2; sudo launchctl load /System/Library/LaunchDaemons/org.cups.cupsd.plist), cupsctl works. Then it fails again with bad file descriptor
After removing the socket "sudo rm /private/var/run/cupsd" (think it gets automatically recreated) - cupsctrl works for a few seconds, then it fails again with bad file descriptor

It seems that /private/var/run/cupsd gets broken by "something" periodically... Any ideas? Otherwise I need to reinstall my MacBook :(

markusloffler commented 2 months ago

Apparently other people are having this problem to: https://discussions.apple.com/thread/255522015?sortBy=best Looks more like a MacOS problem than a cups problem, so feel free to reject this issue if it does not belong here...

markusloffler commented 2 months ago

Apparently a problem with Microsoft Defender. Uninstalling it or giving it full disk access should fix the problem

apple / cups