New: Netbook Tablet with touchscreen
Apple Security Update 2005-003 (#3): Apple pulls Mac OS X server version of update; Site compatibility problems within Safari
Apple pulls Security Update 2005-003 for Mac OS X Server Likely because of the severe issues affecting IMAP and APOP e-mail service (caused by a modification to the Cyrus mail service component of OS X server) reported here on MacFixIt yesterday, Apple appears to have pulled Security Update 2005-003 for Mac OS X Server.
No word has yet surfaced on when a revised update will be released.
In the meantime, if you are one of the users who applied Security Update 2005-003 to Mac OS X Server 10.3.8 and are experiencing adverse reactions, follow the procedure in our tutorial "Reverting to an earlier version of Mac OS X," applying all updates through Mac OS X 10.3.8, excluding Security Update 2005-003 (which will no longer appear in Software Update anyhow).
One typical manifestation of the APOP/IMAP problems reported yesterday is described in a report from MacFixIt reader Jason Self:
"I applied the Security Updated 2005-003 to my copy of Mac OS X Server 10.3.8. Disk permissions were repaired before and after.
"My server is no longer delivering mail. It had been configured to use Procmail using the directions from http://www.afp548.com/articles/Panther/procmail.html.
"Now messages are queueing up in the Postfix queue with the error "temporary failure. Command output: couldn't connect to lmtpd: Connection refused_ procmail: Program failure (75) of '/usr/bin/cyrus/bin/deliver'"
Site compatibility problems within Safari/Timeouts As is the case with most Apple security updates, changes to key Web page rendering/delivery components in Security Update 2005-003 break compatibility with a number of Web sites in Safari.
MacFixIt reader Nick reports issues with the popular AtomFilms Web site: Since installing Security Update 2005-003, Safari crashes every time when I visit the site www.atomfilms.com. I subscribe to this site, visit it regularly, and have never had this problem before. The site displays and behaves properly in Internet Explorer (on the same Mac). The crashes occur with every page on the Atom site that I have tried to access, and this happens just before the page has finished fully loading (status bar typically says 65 of 67 items loaded, or similar)."
A number of other readers report timeouts in Safari, which are similar to the aforementioned case -- Web pages start loading and fail, or never begin to load at all.
MacFixIt reader Mike writes "Since installing Security Update 2005-003 I have been having intermittent connectivity problems with Safari.
"Spontaneously (or so it seems), Safari's ability to access the web will fail, but I can still ping the sites from the command line, and open the URLs in other browsers. However, all attempts in Safari result in timeouts. Quitting and relaunching Safari fixes things."
Potential fix MacFixIt reader Daniel Welch reports a potential workaround which involves removing the Apple WebKitFramework (located in /System/Library/Frameworks/) then re-installing Safari:
Daniel writes:
"Just wanted to let you know that the latest security update left me with Safari completely unresponsive to clicks on links. To fix I downloaded Safari from Apple's website but didn't install it. I went to System/Library/Frameworks/WebkitFramework and dragged Webkit Framework to the trash. I then dragged Safari to the trash and reinstalled it from the new download. I repaired permissions from Disk Utility and everything works great again."
Note, however, that this procedure will remove any security modifications made by Apple as part of Security Update 2005-003.
Printer sharing difficulties Users continue to report problems with shared printers after applying Security Update 2005-003, likely due to modifications Apple made to the AFP (Apple File Protocol) as part of the update.
One reader writes:
"I also installed the Security Update on my G5 PowerMac. This seems to have broken the ability of my G5 to share a Brother laser printer and Canon ip 5000 attached via USB with an old iMac."
Potential Fix Some readers have reported that simply deleting then re-adding the afflicted printer from within Printer Setup Utility (located in Applications/Utilities on a standard Mac OS X installation) on the remote (not printer-attached) machine resolves the issue.Peter Schooley writes:
"When I updated my desktop (the machine sharing the printer) my Powerbook could not detect my Desktop print server. I was able to fix this problem by deleting the printer in my shared printer list on my Powerbook and then re-adding the shared printer. I had repaired permissions and rebooted both machines without success. I tried deleting and adding the printer on my print server (the desktop) without success. Deleting and adding the printer on the client (Powerbook) is what did the trick."
Feedback? Late-breakers@macfixit.com.
Resources
:%20Apple%20pulls%20Mac%20OS%20X%20server%20version%20of%20update;%20Site%20compatibility%20problems%20within%20Safari%20%7C%20MacFixIt%20-%20CNET%20Reviews&srcUrl=http://reviews.cnet.com/8301-13727_7-10334499-263.html){kind=small}
System Profiler still sees other FireWire devices (iSight) but cannot find the backup drives. Any thoughts? (This is also posted on Apple Discussions)
<meta HTTP-EQUIV="REFRESH" CONTENT="0 ; URL= http://thissite.com">
anymore. I know several sites that use them that it simply doesn't work
anymore. I have to 'click to continue' one example was downloading from
sourceforge, downloads didn't start automatically.
Actually I clicked on "Post a comment" button on this article and I got a blank
page so I had to click on a reply to the previous comment.
Wow, talk about proof. After commenting on this story I'm sent to a page that
called "comment.php" and this is the content:
<html><head><meta http-equiv="refresh" content="0;URL=http://
www.macfixit.com/article.php?story=20050323071022574"></head></
html>
It doesn't go anywhere, I just sit there.
No problems for me with refreshing after a post. It works as it always did and
I am returned to the forum page as usual. Best be looking somewhere else for
this problem. No proof of anything here.
too- and I have NOT installed Security Update 2005-003
I've visited this site often in the past without trouble, so they may have
changed something around the same time the update was issued. I'm
running 10.3.8 with Safari 1.2.4
MacFixIt reader Nick reports issues with the popular AtomFilms Web site:
Since installing Security Update 2005-003, Safari crashes every time when I
visit the site www.atomfilms.com.
Just visited that site and don't have any problems with any of atomfilms
pages. There's something else going on here. I suggest either 1) creating a
new admin user account, logging into it, and try replicating the problem or 2)
reinstalling the 10.3.8 Combo update.
When I hear reports of something wrong after an update I am often curious to
see whether I too have that problem. I had never heard of atomFilms, but just
went there, watched a few moments of an incredibly boring animation called
"Ego", left the site avowing never to return (sorry, folks, not my taste!), but
can confirm that it all works perfectly on my iMac G4 800 with this latest Sec
Update on top of OS 10.3.8. I suggest that those having that problem, rather
than blaming the Sec Update, do as Baltwo2 has suggested.
---
Andreas
I have a 1st generation TiBook as well & suddenly Atom is crashing Safari too.
The message above gave me the hint that I should delete the printers on the windows machines and reinstall them. One machine is a Win2000 desktop. Deleting and reinstalling the printer was SUCCESSFUL, it now prints as before.
The other machine is an older laptop running Win98SE. I was unable to reinstall the printer on it. When I look at the network neighborhood, I see the Mac and the "PDF printer" on it, but there is no sign of the Brother. On the Win2000 machine, the network neighborhood shows the PDF printer, the Brother printer, and the Epson 4000 printer that is also attached to the Mac.
Any suggestions?
--Dan Wheeler
- by Torky March 24, 2005 4:38 PM PST
- SU 2005-003 (Client) has its problems too.
- Like this Reply to this comment
-
(11 Comments)Since installing the 2005-003 Security Update I can no longer print
from a Windows XP on my Airport Express network to the printer
attached to my eMac (not the base station). Immediately after the
installation, the PC could not even connect to the eMac via the
network for file sharing. Found the reason was that the update had
actually turned off Windows Sharing in the Sharing pane of the
System Preferences on the eMac! Checked that on again (and
made sure that Printer Sharing was still on). File sharing was
restored and works OK.
However, I am still unable to print from the PC. It cannot connect to
the eMac's printer. When I introduced another Windows XP PC to
the network to test, same problem and this time was not even able
to add the printer in the first place. The PC could 'see' the printer
but refused to add it. (Error = incorrect printer name/lost connection
to server)
Spent three hours on the phone to the Apple fellows in India. No
progress. They said it was probably something to do with the part
of the update to do with Samba (whatever that is). They said they
had documented the problem and to wait for next update! That's no
good to the Windows person on my network who urgently needs to
print.
My further investigations found this change logged as follows at:
Macintosh HD/Private (hidden)/var/log/samba/log.nmbd
(before 2005-003 Security Update)
[2005/03/23 22:43:50, 0] /SourceCache/samba/samba-59/samba/
source/nmbd/nmbd.c:main(664)
Netbios nameserver version 3.0.5 started.
Copyright Andrew Tridgell and the Samba Team 1994-2004
(after 2005-003 Security Update)
[2005/03/24 15:02:53, 0] /SourceCache/samba/samba-60.1/
samba/source/nmbd/nmbd.c:main(668)
Netbios nameserver version 3.0.10 started.
Copyright Andrew Tridgell and the Samba Team 1994-2004
So, has the updated Netbios nameserver version from 3.0.5 to
3.0.10 (updated by SU 2005-003) caused the problem that
Windows computers no longer print over a network to Mac
attached printers?
Can anyone suggest a solution or fix and/or explain why this
happened?