10.6.6 - Major Airport Bug?

Hi Folks,
Recently upgraded to 10.6.6 (MacBook Pro) and I've noticed an odd Airport bug. The sequence is like this:
Cold Boot > Connect to Wifi > Surf Net > Close Lid & Sleep > Open Lid and Connect to Wifi
At this stage I cannot connect to the internet. I have a valid IP and its the same network. AirPort is showing connected. The only way to be able to surf again is to completely reboot (And it might take more that one reboot)
Its happened on two entirely separate networks. One is a open college network that worked flawlessly on 10.6.5. The other is a simple home network that again worked perfectly under 10.6.5.
The only thing I've been able to ascertain is I can't get a new IP. I constantly get the same one even when I cycle Airport. Eventually on a reboot I get a new IP (DCHP is on etc). On the packet side of things, lots of received packets but no many sent.

I feel 99.9% confident in saying this is not a bug in the update. If it were, we'd be seeing a lot of reports, and we're not. I sleep and wake my MacBook Pro many times per day every day and never have trouble with wireless access.
So, the question is, what's wrong with your machine? Try some of the recommendations in my post here:
http://discussions.apple.com/message.jspa?messageID=12952906#12952906
Hopefully, something there will lead you to a resolution of your problem.

Similar Messages

Airport bug, lost wifi...

Hello,
I have a macbook pro 15 inch (mid 2009) with snow leopard and for several days, sometimes the airport bug. Wireless internet is cut, it is impossible to reconnect to the network. I can not restart AIRPORT, sometimes it is marked "no card installed". I need to restart the computer, sometimes at least 3 times to find the wifi signal.
I made no program installation, no modification system and I tried five different important wireless network. I tried to delete AIRPORT preferences and then put it back but it did not work. I do not know what to do. I have a problem since "Security Update 2011-005".
The wifi working fine on my bootcamp partition.....so it's not an hardware issue;
thank you

Having the exactly same issue. At least once a day, Airport drops the connection and deactivates itself. Impossible to re-activate it, so I need to reboot the computer (sometimes 3 to 5 times in a row) in order to have Aiport reactivated.
I'm using a MacBook Pro 13" (mid 2010). The problem appeared with an update. It was so annoying that I installed Linux (Ubuntu) and it works just fine, which makes me think the issue is not hardware-related but strictly softare-related.
I don't know if Grégoire found a solution to the problem, but I would be very interested in any clue that might help me out. I've tried every suggestion found on the Apple website, but nothing helped so far. It's been more than a year now... Having a very bad experience with my MacBook Pro...

Major CS5 bug where Smart Objets get thin horizontal lines??

Our prepress company has come across and proven out a rendering bug in Photoshop CS5 for Mac. It has caused us to consider totally avoiding CS5 until it's fixed. We are finding that CS5 is putting in several randomly generated thin horizontal lines about a pixel in height and varying widths, in cases where CS4 does not. Some files get these lines when converting live "smart objects" from one ICC colorspace to another.
I am providing a link to a specific file that shows proof of this bug. The example file has an embedded sRGB profile. To see the bug, set you working RGB colorpsace to AdobeRGB, and set your Policies to "Ask". During opening, USe the embedded profile. Then convert it to the AdobeRGB 1998 colorspace using File Convert, and do not rasterize the smart objects. You will see lines in the lower right hand corner after it's converted. Now go back and rasterize the smart object layers first, and these lines will not show up. And now do the same with CS4, without rasterizing the smart objects and you will not get lines. CS5 bug, CS4 no bug.
Let me know what you find on your end. Can any of the adobe employees document this for me and get it on the fix list?
Test file:
http://www.mediafire.com/?ant3ya9aaft1a95

I also head a Graphics/Prepress department at a medium format digital print shop, with next day service to the casino industry. My two cents worth, CS4 did not have this issue, CS 4 was a Cocoa app and CS5 a Carbon app, to me that is not a reason why a major software company like Adobe has multiple leading products (PS, ID, Ill) that cause these kind of problems. I can't count the times my print opp's have come back with a file showing lines. Now, I have told my designers that we should also be looking for the lines, now that we know about it.
I have printed fabric before and it is a pain to print one and see if there are lines in it, but which is more painful, printing one to test? Or trashing $3k worth of fabric? I know this works for one image printed x times, but multiple images printing a couple each to fulfill the job would be a huge ordeal. Adobe doesn't understand that yet. The squeaky wheel gets the grease, maybe we should all start calling tech support daily.
I saw a post suggesting rasterize pdf's in lower PS to work around, clearly an ad agency/freelance solution, not a production house solution. Opening and closing PS12 and PS11 somewhere around 15 to 20 times, per work station? We process somewhere around 40 minimum pieces of art a day, and sometimes double that. I could rant on this suggestion all day.
The bottom line is Adobe has no clue where it is coming from, they are more worried about the iPad/mobile industry right now.

Major Safari bug re: private browsing

Hi everyone, I'm encountering a major bug in Safari's private browsing mode. Basically, after you exit Safari, even if you close all previous tabs and use Settings to clear the cache, after you return again to Safari's private browsing mode it briefly flashes a screenshot/grab from random video content you viewed prior. There doesn't seem to be any way to clear this ... any suggestions? I just tried resetting all settings and that didn't work. Side question: does Safari's cache automatically clear after a certain point in time, i.e. 30 days after site visits and content gets stored? Many thanks in advance for all input!

Same here!
I have ghost images which sometimes appear randomly when starting or returning to Safari. They last one or two seconds then go away. I can't really define a pattern but it happens quite frequently...
Tried clearing the cache and cookies but I didn't do anything as the problem still occurs.
Apparently this issue has been known for quite some time and everyone is waiting for it to be fixed.
See more here : Safari on ipad2 ios7 does not clear cache or history properly
Come on. How hard can it be to ask iOS to delete ALL the files in a specific folder?

Major JavaScript bug - form variables not submitted

I'm building a page where data is submitted to Paypal via a form and using Javascript to build Select statements on the fly. These appear as expected, but when the form is submitted none of the variables are POSTed through. The same page works perfectly in IE so there must be a major bug in Firefox's impementation of Javascript - this is a total show-stopper for the page I need to implement.
Go to the URL below and then check availability for type of room ANY. On the booking confirmation page if you leave the first select alone and hit the Pay Now button you will arrive at a debug page that dumps all the POST variables in a new window. Now go back and change the room type in the first select statement just above Pay Now - this updates the second select. Maybe even click it again to go back to the original setting. Now click Pay Now - nothing comes through from the select statement and some associated hidden vars.
Try it in IE and it works just like it should.
== URL of affected sites ==
http://www.west-end-bb.co.uk/test/

Found this which has solved the problem:
[http://www.infoqu.com/dev/javascript-development/crazy-firefox-javascript-bug-156760-1/]
There seems to be an issue with FF and InnerHTML when a form is in a table. By moving the form tag around I was able to place it within the table definition so that it works in FF.

Another Airport Bug

<div style="-webkit-border-radius: 15px; border: 1px solid grey; background: #eee; padding: 5px;"
I've been searching all over both Apple's knowledge base and the rest of the internet because of this problem. My Macbook Pro's built-in airport is totally unusable,
The menubar item displays the "airport on" image, but the only two options are "turn airport on," which does nothing, and the "Open Internet Connect..." item. Internetc Connect says the Airport is on, and the status is
"Status not availible"
"Status not availible"
"Status not availible".
The Airport will automatically connect to open wireless networks, but does not inform the user. The Airport menu bar remains the same.
Has anyone encountered this problem, or have a suggestion?
17" Macbook Pro Core 2, 2GB Ram, Bootcamp'd Mac OS X (10.4.8)

More info: these people seem to have the same bug::
http://discussions.apple.com/thread.jspa?messageID=4176858
This is another instance -- but the helpful responder confuzed the built-in airport with a base station.
http://discussions.apple.com/thread.jspa?messageID=4004411
Another thread; this seems to be a fairly common bug:
http://discussions.apple.com/thread.jspa?messageID=4087082&
I submitted a bug report on this, so hopefully Apple will get back to us (affected users).
Also: I don't seem to be able to edit my first message - that is REALLY annoying

Airport BUG

Whenever my computer wakes up from sleep it is incapable of detecting wifi networks!
Solutions attempted:
clearing stored preferred networks - does nothing
turning airport off and then on again - does nothing
restarting the airport extension (kext via command line) - results in failure of the airport card until reboot (can't reload it)
reboot - after reboot everything is fine again and wifi function works perfectly.
Despite reboot fixing the problem temporarily, this is frustrating enough to make me move to linux if I can't fix it soon. I'm guessing this is a bug in the most recent airport software update, because I haven't had this problem until recently and don't think I've modified any settings that would affect this.
Any assistance would be much appreciated.
PowerBook G4 Mac OS X (10.4.8)

Appears that quite a few folks are having this problem with OS X 10.4.8 using WPA2 security...
(ref: http://www.macfixit.com/article.php?story=20061004074201292 &
http://docs.info.apple.com/article.html?artnum=304482)
Try the following, in order, (sorry if there's any redundancy to what you may have already tried) until resolved:
1a. Delete Preferred Network(s)
- System Preferences > Network > AirPort > Configure
- In the "By default, join:" pull-down menu, select "Preferred networks"
- Delete the network(s) you regularly use from the list
1b. Delete AirPort Keychain Entries
- Launch the "Keychain Access" application located in Applications/Utilties.
- Click on the "Kind" filter at the top, and look for any "AirPort network password" entries...and delete them.
- Restart, or log out then back in.
1c. Add Preferred Network(s)
- System Preferences > Network > AirPort > Configure
- In the "By default, join:" pull-down menu, select "Preferred networks"
- Add the preferred network(s) using the "+" button.
- Restart or log out then back in.
2. Run the Disk Utility to repair Disk Permissions.
3. Turn off the Mac OS X Firewall
- System Preferences > Sharing > Firewall
- Click the "Stop" button.
4. Move System Configuration Files
(Note: You will have to reestablish your network connections settings.)
- Go to /Library/Preferences
- Move the SystemConfiguration folder and com.apple.networkConfig.plist file to the desktop.
- Restart your Mac. (Note: OS X will rebuild the files that are now sitting on your desktop. If this doesn't resolve the issue, you can move the folder & .plist file back to it's original location.)

Major Graphic BUG???

FCP6/HDV appears to have the same Bug that FCP5 had for a while. Imported Photoshop files (any still format) show up looking like they are single fields instead of frames. In other words, every other scan line of pixels is not showing.
Playback Quality changes don't help. And the truly weird thing is that the same file looks perfectly fine in the Viewer, but not in Canvas.
Rendering doesn't help.
Native Photoshop, JPEG, TIFF--all look horrid. Files that played last week just fine in PS 5.x now look like a mistake.
FCP5 had this bug--similar, but not exactly the same behavior--when it was brand new, and it took Apple months to realize it and fix the mother. In FCP6 the major difference is that the still image looks horrible as soon as it is inserted in the timeline. FCP5 looked fine in the timeline in Canvas, but lost integrity when rendered or viewed running.
All effects, titles, matte painting FX, still overlays, still insertions are affected.
Please, somebody, tell me there's a switch somewhere that fixes this?
-iNova
Dual 2.5GHz G5 Mac OS X (10.4.9)

While I'm not monitoring on an external monitor, the rendered file plays back with a perfectly clear background HD image and a flawed title overlay, so it's not the reviewing apparatus or conditions. Digital Cinema review shows the effect, too. Exported QT files show it, too.
What's significant about RT is that at High, the background is fine and the overlay still is corrupted, appearing to be 1/2 vertical resolution while maintaining full horizontal res. At Medium, being 2 x 2 pixels per detail, both clean background and overlay still look the same. At 50% scale Canvas viewing they look the same, too, which is to be expected. I'm not talking about field artifacts in motion. Those are easy to see on the computer monitor.
In the Viewer window, enlarged right next to the Canvas window, and both at 100%, pixel-direct viewing, the Canvas image is corrupt and the Viewer image of the same file, thrown into the View window from the timeline, looks 100% quality.
Since the Viewer window can portray the still bitmap image while looking perfect, and can portray moving footage perfectly, the issue seems to be in something that the Canvas window's handling routines are doing with the JPEG and .psd files. Since it does the same flaw with TIFF files, it seems logical to assume that it's not the incoming format, rather it's something in the way the timeline/Canvas handles bitmaps.
Are you seeing stills pixel perfect? Scale a 6MP digital image down to 1920 x 1080 and JPEG it, importing it into FCP6. Then view that in Viewer and Canvas at 100% scale after you drop it into the timeline.
One extra oddity; PS files import into the Browser as .psd format (1440 x 1080= exact resolution) self-contained sequences.
That's the way they show up normally--and must, if they had layers. If you double click on the source .psd file, opening it as a sequence, it shows up in its own timeline, and in the Canvas without the mangled look. It looks right.
But drop that source file into another timeline--the way you must to use it in an edit--and the corrupt appearance returns.
So we can add a new bit of mystery solving: It's possible for the Canvas to see a still image file with clarity--IF that file was imported as an existing sequence, the way .psd files do. But somehow still files of several formats can land in the timeline with this flaw. Making titles in Photoshop very ugly. Plus this: Do anything to the OK looking .psd image and render that--poof! The flawed appearance returns.
I'll bet Premiere doesn't make this mistake.
It's not a scaling artifact. It has the look of an image minus every other scan line, showing dramatic aliasing on shallow angle contours and loss of vertical resolution only.
Too much head scratching.

MAJOR TM Bug found in 10.6.1! Time Machine corrupts HFS+ Filesystem! Raid 0

Hey there,
i guess i just found a major bug in 10.6.1 and Time Machine which will corrupt the whole Partion which was selected for the Time Machine Backup.
This is what i got here atm:
2x Western Digital MyBook Mirror Ed. (ext. 2TB Raid0 HDD (2x1TB))
1x Mac Pro running 10.6.1
1x Macbook Pro running 10.6.1
1x Mac Mini running 10.5.8
Ok here we go:
I just updated to Snow Leopard a few weeks ago and wondered why my always working WD MyBook was not working as a Time Machine Backup Partition anymore.
Everytime i started a backup it failed after 10 gig or so. After reading all over the troubleshooting and this forum i am a 100% sure that this is not a usually bug like not formatting the hard drive to GUID Mode or so.
Well... i tried the second MyBook.. same result on both Macs running 10.6.1
Now i got suspicious and opened the MyBook in order to put those 2 HDDs in my Mac Pro and built a 2TB Raid0 via OSX.
Guess what? Same result when running Time Machine! Running Time Machine on a single 1 TB HDD was working perfectly fine.
No i just remebered that there was a Mac Mini hooked up to my TV that was still running 10.5.8 just because of Plex... Hooked up BOTH MyBook Mirror Editions and both worked perfectly fine!
Now where can i report this error? I have no doubt that Time Machine on 10.6.1 is corrupting the HFS+ Filesystem when the partition is a RAID 0 Partition.
Please let me know what you think and where i can report this bug. Anyone knows if this one is already fixed in 10.6.2?
Thanks!
André

Yeah i did check the firmware updates for both mirror editions. Both are up to date. What botheres me is that they are not working aswell when they are out of their enclosure and directly built in to the mac pro. Can this really be a firmware issue then?
From what I've read on repair/recovery sites, WD does put some of their firmware on a special part of the drive's platter itself. So it's still possible to have instructions on the actual disk that can create a problem. I do not know if this is causing your issue, it's just something I became aware of when shooting trouble on some MyBook/Mac issues. There are some WD enhancements to power management that may be problematic for Time Machine. I don't really know the whole story, just relaying what I've read.
It's also possible that 10.6.2 (in beta) will help with an issue like yours. In our machines we've been using Hitachi and Seagate and the occasion Samsung drives for the last few years. Our external closures come from OWC and we haven't had any of the firmware issues that happened with the Leopard release and WD and now maybe the SL release.
The only way I would be able to point a finger right now would be to swap in a couple of other drives and see how they work. Right now it doesn't matter who's at fault, Apple or WD. The drives don't work. If it's a problem with your installation you may be able to determine that by doing the above tests. If it's a problem with Apple's drivers there may not be a repair possible or a future update will be required. The same goes for the WD drives.
Sidenote: For our own network, we have decided to do away with Leopard Server on an old Dual G4 1.42 tower and use our new ReadyNAS drive from Netgear. It's already working perfectly with Time Machine for several computers, file storage for PC/Mac/Linux, torrent download machine, basic web server, etc. We've put in 4 1TB drives and got 2.7TB of redundant hot swap raid. We'll replace the 1TB drives with 2TB drives, one at a time (although the available space won't increase until all 4 drives are swapped in), while the NAS is online, to increase our storage as required and the drives come down in price.
We decided that if the data is important then a striped 2 drive volume isn't safe enough. We would have needed to mirror the drives and loose half the space and still have to keep the old server online.
I'll watch this thread for information from others. I don't have the drives you are using to test with.

Apple Released iOS 7.1 with Major AirPlay Bug Fix

Apple released iOS 7.1 with interface refinements, bug fixes, improvements and new features on Monday. But has the Airplay bug been fixed?
During the test of X-Mirage, we have found that AirPlay on iOS 7 is not as stable as on iOS 6 and we have reported a serious bug to Apple:
iOS 7 BUG – The devices stop sending mirroring data to Apple TV or X-Mirage one minute after iOS devices auto-locks
https://discussions.apple.com/thread/5468657
After using the iOS 7.1 today, we find that Apple has fixed the bug and AirPlay is more stable than before, so our distinguished X-Mirage users, you can update to iOS 7.1 freely and enjoy more fantastic AirPlay Mirroring and Streaming services. Getting the update is easy. Go to Settings. Select General. And tap Software Update.

thanks for the information?

Major Plugin Bug Passing Boolean Parameters via JavaScript

Calling an applet method that sets a boolean property fails under IE with the 1.3.1 Plugin. Method signature in a public object contained by the applet is:
public void setShowTitle(boolean newVal)
Attempting the following javascript in an HTML page fails with a "Type Mismatch" error:
document.MyChart.getChartObject().setShowLegend(true);
Interestingly, a method with a similar signature, which is in the top level object works fine:
document.MyChart.updateChart(true);
Definitely a bug in the plugin!
- Rick Bullotta
CTO
Lighthammer Software

Hi,
IE can only access attributes and methods from a class derived from java.applet.Applet. Therefor, Javascript cannot call methods from the object which is returned from your call to document.MyChart.getChartObject().
You should create a method (public void showLegend(boolean)) in your applet which can directly be accessed from Javascript, and let this method call the non-Applet derived methods (getChartObject().setShowLegend(boolean)).
Regards,
Kurt.

Major textfield bug AIR 3.7/3.8 on Android

Hey guys, I was wondering if anyone encountered this bug and managed to fix it. If not (or if this is not my fault somehow), I will open a bug report about it.
The bug does not happen on AIR 3.6 on any platform. It also does not happen on 3.7/3.8 for iOS. It only happens with 3.7/3.8 for Android.
There is a classic text input textfield on the screen. It is a singleline textfield. But somehow, it works like a multiline text. Whenever I press enter, I get a line break. Did anyone experienced this problem before?
Thanks everyone!

Could you please share the Android device(OS version) , AIR 3.x version you are using. I tried with classic text input textfield(Flash professional CS6) with Android OS versions 2.3.1, 3.1 and 4.1.2 but could not able to reproduce the issue. Please share a sample project at nimitja@adobedotcom (if possibe) to reproduce the issue. This will help us investigating the problem.
Regards,
Nimit

Experiencing major crashes, bugs still there

The last update was a giant step forward, I'm enjoying working with the new SG version (CC 7.0.1 x51).
But, I noticed the problems with CMD+Z (undo) are still there: sometimes works, sometimes stucks on "optimizing timeline", sometimes the thumbnails in the timeline are displayed, a lot of times my pointer disappears and I have to restart SG.
I'm afraid to press cmd+z now!
I'm doing my first client work with the new version, will report eventual bugs or problems.

Thanks Dennis, sorry I don't mean crashes. I completed the work yesterday and the main issues I encountered are with cmd+z (undo). When pressing cmd+z I got these effects (each time different):
1) The old problem of thumbnails, the bar came out and the "optimizing timeline" progress bar is shown.
2) "Optimizing timeline" progress bar is shown, when at 100%, the preview switches to "2 up" automatically with the same frame I actually was on in timeline in both panels.
3) Sometimes after the issues above, the mouse pointer disappears, I have to force quit and restart SG.
I am on a macbookpro (mid 2010) osx 10.8.4, Speedgrade CC updated to latest version.
Will also file a bug report via your link.
I finished the work smoothly and rendered a master, but I will open a new thread with some requests regarding the workflow and some features (missing or hidden!). Thanks
Andy

Major iPhoto bug - TIFFs compressed and overwritten

I just sent this bug report to Apple. I want it to be known. It is tested and discussed in http://discussions.apple.com/thread.jspa?threadID=1342564&tstart=0
In version 7.1.1, TIFF files are processed into Canon Raw files when setting the date and time using Photos > Batch Change and possibly also with Photos > Adjust Date & Time. The criterion is that you have "Modify original files" checked.
These Raw files are much smaller than the original TIFFs! During experimenting, 12MB TIFFs were overwritten by 400KB files! 42MB TIFFs by 1 to 2MB files!
This happens regardless whether the photos are copied into the iPhoto Library or not. So if not, the original files are modified and there is NO BACKUP!
Another issue is that the files keep the extension .tif in the Finder. Adobe also maintains that they are TIFFs. iPhoto only unveils them as being Canon Raw images when reimporting! So there is no way of telling until you check. By then it's already done, and quite irreversibly.
This should not be possible. Those working with TIFF files are usually people who want to preserve their uncompressed originals at all times. For me, this bug is really a shock! If this function is here to stay, iPhoto should at least warn the user what happes if "Modify original files" is checked.

With the amount of people on these discussion boards saying that their iPhoto Library has vanished, I presumed the trouble lay in iPhoto.
Not necessarily. Maybe there are 100 reporting the problem. That's insignificant when compaired to the number using iPhoto without a problem. Judging iPhoto by what you read here in the forum where only those with problems post is like judging the health of a city by what you observe in the Emergency Room of one of its hospitals.
OT

Final Cut Pro X & ProRes Major Funny BUG - Pertains to AE also !!!

This must be the weirdest BUG I have ever experienced... And the most difficult to find. I found it via coincidence ;-)
I playback and use ProRes 4444 inside of FCPx. And generally there is NO problem doing so. Until yesterday...
In After Effects I converted a bunch of H.264 Canon 5DMKii movies, after denoising them, to ProRes4444.
I imported the movies into Final Cut X and immediately noticed that they were jerky in playback. So I loaded the original files and wanted to see whether they were jerky as well. They were not... Here comes the funny part...
The Original H.264 had AUDIO on them the ProRes version I had stripped the audio from as I did not need it. To better compare the two files (Don't know why I did it but I did) in the timeline I just copied the audio from H.264 file over underneath the ProRes4444-jerky file. Then I compared again. This time the ProRes was playing smooth as silk. I could NOT believe my eyes. I was cursing at the Mac but after smoking a cigarette and contemplating, I went back an deleted the audio from underneath the Prores 4444 file. Back to jerky. I put the audio back - jerkiness GONE...
So I did some more testing...
I took a completely different clip and imported that into After Effects.
I did the same denoising to it and exported TWO versions to PRORES 4444.
1 with Audio and 1 without it...
Then imported the two into FCPx...
We are talking TWO identical files here expect one has audio to it.
The one with audio played back silky while the one without was jerky.
I copied the audio (any audio will do) underneath the jerky one and it stopped jerking around.
I opened the two test files in QuickTime 7 and 10 and NONE of them were Jerky... This issue seems to pertain to FCPx only....
So if any of you export from AE to ProRes4444 and the guy on the FCPx station gets agitated because of the jerkiness,
before you blame adobe (like I did) tell him to just copy some sound underneath the sound-less video clip. That will take care of the problem,
untill Apple fixes the problem ;-)

Glad you found a solution, AtonMusic! Did you bring the issue up to Apple?

10.6.6 - Major Airport Bug?

Similar Messages

Maybe you are looking for