Mac OS X 10.4.1 (#11): Freezes in full-screen mode; Inherit permissions does not work for AFP service; more

CNET staff

Sept. 2, 2009 11:33 a.m. PT

6 min read

Freezes when using applications in full-screen mode Yesterday we noted a problem where opening a movie in QuickTime 7.0.x and entering full-screen mode causes a freeze where the system becomes unresponsive but the mouse cursor can still be moved.

It has now been confirmed that this bug affects a number of other applications, causing system-wide freezes when full-screen mode is entered.

MacFixIt reader Seth writes:

"I too am experiencing this problem. Its been there since I upgraded to Tiger. I used the 'Clean install -> copy users' option to install over 10.3.9. Any application that enters/exists full screen mode seems to be effected. I also have a Power Mac G5 1.8 GHz single processor machine. My machine has always recovered given enough time. But 'enough time' seems to be at least 2.5 hours. The Mac OS X 10.4.1 update did not fix this problem."

Another reader adds:

"Since the installation of Tiger, I've had freezes on my PowerMac 1,8 single after few hours of work, the freeze occurs often when i try to view something in full screen mode (diaporama, QuickTime 7, etc.). I've deactivated of the energy saver preferences (my PowerMac won't turn off or sleep even my apple display stays on) but same phenomenon after few hours the screensaver (full screen) causes the freeze of my PowerMac. I never had this kind of problem with Panther.

"When the system freezes, I need to push the power button to restart the PowerMac. I've tried to remotely connect the PowerMac (via SSH) but no response. The system logs are emptied. I've installed TechTool Pro 4.0.4 to check the system for hardware problem but no error is found."

Finally, another reader writes:

"Mac OS X 10.4 (Tiger) is freezing after 2-3 hours, as soon as i launch a Program in full screen mode, and also with Quicktime 7.xx in Safari. This doesn't happen with Mac OS X 10.3.x (Panther). Freezes in : Preview 3.0, Spotlight 1.0, Mail 2.0 and iPhoto 5.0.x, etc..."

If you are experiencing a similar issue, please let us know.

Inherit permissions does not work for AFP service (cont.) Yesterday we reported an issue where permissions for files and folders created through AFP (Apple filesharing protocol) under Mac OS X 10.4.x. are not correct.

Under Mac OS X 10.3.x (Panther), access is given to both the Owner of the file and the Group when a file is created by a client machine on a server. However, under Mac OS X 10.4.x, permissions for AFP-copied/created are set as read/write for the owner but not for the group, meaning that files cannot be shared between client users.

Apple confirms this issue in a Knowledge Base document (#301601):

"When offering Apple File Protocol (AFP) service, Workgroup Manager allows you to set the default permission on new files and folders to "Inherit permissions from parent." This option does not work presently with Mac OS X Server 10.4. Specifically, AFP server is not setting the permissions on files created in subfolders of a shared folder when inherit permissions is enabled.

"If the file system being shared is HFS Plus, you can work around this issue by using access control lists (ACLs)."

Apple is purported to be working on a fix for this issue that will be released in a future update to Mac OS X 10.4.x.

In the meantime, you can find instructions for setting up ACLs (access control lists) in this Mac OS X Server 10.4 manual.

As noted by MacFixIt reader Mark Daniel:

"With 10.4.x Server, using Apple's Access Control Lists, newly created files/folders automatically inherit the parent folder's permission settings. If (a user) is having this problem, it's most likely because he didn't correctly configure the ACLs... which can be daunting at times, but provide for almost unlimited flexibility.

"I've moved a few offices over to Server 10.4, and they're loving it... ACLs rock. This includes the DetroitMac office, as well as numerous other testing and odds n' ends servers I've got laying about. Permission problems are FINALLY out the door. One thing to keep in mind, though, is that ACLs ONLY take effect if you have them enabled for the volume (done through Workgroup Manager), and you have at least one ACE (access control entry) specified for a particular sharepoint's permissions. If you have one specified, POSIX-style permissions are ignored."

Kernel panics when copying large files (cont.) Users continue to report repeated kernel panics when attempting to copy large files from volume to volume under Mac OS X 10.4.x. The same kernel panics do not occur for the same files when running Mac OS X 10.3.x.

One reader writes:

"I just encountered this yesterday with a clients new Dual 2.7 GHz Power Mac G5. I was transferring large Final Cut files from the old G4 we were replacing via target mode and I got Kernel Panics twice. I then copied the files from the G4 to an external FireWire drive while booted from the G4 in Panther and all went well. Plugged the drive into the G5 and copied the files back, Kernel Panic again."

MacFixIt reader Paul Tansley adds:

"I have had this problem before and now it has occurred again. I have no idea why. I'm trying to copy large folders of images from one disk to another. I've tried over Firewire 800, Firewire 400. I've unplugged everything else. I've had 6 kernel panics in a row. I've started in single user and repaired my main drive using fsck (it found no problems). I've repaired permissions etc. The problem was not specific to one folder. I tried various, even one from my main hard drive."

Finally, Mark Grubbs adds:

"I was having this same problem, copying to a LaCie Big Disk 320 connected to a new 2x2.0 G5. It would panic at around 100-200MB copied. I tried connecting FW800, FW400, to the internal port, and an external LaCie FW800 card. The same disk worked fine on G4s installed with 10.3.9 and 10.4.1, and LaCie 160s worked on the G5

"I called Apple support and they ran me through a bunch of standard stuff which didn't help. The last thing was to boot from the Hardware Test DVD and run the extended tests. There were no problems found but when I rebooted, the disk has not been a problem. I can't imagine that a hardware *test* would fix anything... But it's working now."

Previous Mac OS X 10.4.1 coverage: