Ziphone creator Piergiorgio Zambrini has discovered a bug with the iPhone that causes the phone to crash when it starts to play a specially-created video. Forbes.com recorded a demonstration.

The bug apparently affects the audio track of the video, which takes down the iPhone operating system. I could not independently verify the bug, because the links to the movie (and the movie file itself) shown to Forbes were no longer available online.

The bug does not permanently damage devices, according to Zambrini. He said he hasn't yet contacted Apple's security response team. Forbes.com informed an Apple spokesman about the flaw and is still awaiting an official comment.

Zambrini claims he emailed Steve Jobs personally about the bug; around the same time, he applied for employment at Apple. Apple has not yet responded to his resume. It strikes me that Zambrini is trying to appeal to Apple in the same way that your ex-girlfriend tries to appeal to you by spray painting the front of your house.

In the Forbes.com article, Zambrini now claims his goal "...is not to work for Apple."

Zambrini created Ziphone, a popular iPhone unlocking tool.

Thanks, Taylor!

Update: A tipster sends word that he's been in touch with Apple's Product Security Team, and says the crash has been fixed as of iPhone OS 2.1. There is no threat to users as long as your iPhone software is up-to-date.

Some Windows Vista users are having significant problems using iTunes 8, which crashes the operating system with a "blue screen of death" when an iPod or iPhone is connected to the PC.

Apple today released a tech note, suggesting to uninstall Apple Mobile Device Support, restart the computer, and re-download and re-install the iTunes 8 installer. It's unclear what about Apple Mobile Device Support was causing the problem.

According to Macworld and ZDNet, Apple simply replaced the files associated with Apple Mobile Device Support (usbaapl.sys or usbaapl64.sys) with the versions shipped with iTunes 7.7.

Computerworld highlighted several irate comments from an Apple Discussions thread on the subject, including precious gems such as "I love how Apple owns up to problems... IT'S NOT US! IT MUST BE YOU! OR MICROSOFT! OR YOUR MOUSE! OR YOUR CHAIR!"

Adorable.

Don't you hate it when an application becomes unresponsive and crashes? Are you even more tired of reading annoying application crash dialog boxes? A simple Terminal hack allows you to never see these dialogs again. Just open Terminal (Applications > Utilities) and type:

defaults write com.apple.CrashReporter DialogType none

This will disable the "...unexpectedly quit" dialog that normally appears when an application crashes. If you ever want the dialogs to start appearing again, just replace "none" with "prompt".


Like tips like these? Try out TUAW's Mac 101 and Terminal Tips sections.

Jim Dalrymple at Macworld notes that the iPhone software update from Monday was mostly to handle issues with dropped calls on new iPhone 3G handsets. According to an Associated Press article, the update "improved communication with 3G networks," said Apple spokesperson Jennifer Bowcock.

However, some Macworld commenters are saying the update hasn't helped with dropped calls, even in areas with a strong signal.

What's more, according to an AppleInsider rumor, another update is scheduled for September that addresses an issue where non-default applications will repeatedly crash. A tipster claims to have received a Steveogram saying the issue "is a known iPhone bug that is being fixed in the next software update in September." (Chairman Jobs is known to occasionally respond to complaint emails with terse but sympathetic notes.)

The crashing problem has remained unresolved so far, and it has resulted in large and angry Apple support discussions about the topic. Steve's one-line explanation may at least provide a target for users for when they can start using their iPhones as intended.

AppleHound has posted a list of all the (supposedly) reproducible bugs they could find in iPhone 1.0. There's 68 in total, and they range from various system hangs (the Phone app will hang if you start a sync while editing a contact photo) to many different UI/Usability bugs. Some of the usability bugs are a little iffy if you ask me-- many of them, like the "bug" where photo albums with less than 20 images don't display an actual number of images, seem to be "working as intended" (because why would you need an image count when you can easily see how many images are there?), and others have already been shot down according to the Apple HIG.

But on the other hand, I can't really fault AppleHound for being such sticklers. First of all, this is a cell phone that costs $600, and you should get what you pay for-- quibbling about interface quirks now means there's a much better chance of getting them fixed in a future firmware update. And second, this is Apple we're talking about. While other cell phone companies get complaints about call reception and service outages, these are complaints about tiny, half-a-second visual inconsistencies. Heck, I love my Razr, and the screen goes nuts without reason almost daily. There's nothing wrong with holding Apple to a higher standard, and maybe if Apple is kept on their toes with the iPhone, hopefully other cell phone companies will find themselves with their feet held to the fire as well.

Thanks, Leonard Nimrod!

Over at Macworld Rob Griffiths has a great column on automatically restarting a program after a crash. Although it is much more stable these days, for a while last year Quicksilver was constantly crashing on me and often I wouldn't notice until ? + space was strangely unavailing. If there's any program for you, like Quicksilver for me, that simply must be running all the times (but which unexpectedly crashes sometimes), Rob's hint is potentially very handy. It basically involves using Lingon to create a launchd daemon that watches for a crash log and then restarts the application when it sees one. Full instructions are available at Macworld. I'm now going to go see if I can get this set up for Quicksilver.

What's better than a Dashboard widget that can display a Mac OS X kernel panic? A full-on screensaver that can simulate one, of course! Mark Johns of Doomlaser has built an eerily realistic kernel panic screensaver, right down to the slowly dropping grey shade of despair, that will surely induce panic in the hearts of its victims in the way that only the haunting question of "oh crap, did I save?!" can. For a nice touch of style, it can even pause iTunes to really stop the show.

Watch a demo of the screensaver here in this post, or head over to YouTube for the original. Finally, you can snag your own pranktastic copy from Doomlaser.

Security-Protocols has discovered a few more minor security issues in Mac OS X that mainly pertain to how the OS and a few of its apps handle images and opening zip archives. From a quick glance through the listed errors, they pretty much amount to crashing an app, though a couple of the Safari issues cause "the application to crash, and or may allow for an attacker to execute arbitrary code."

Apple has been notified of the issues and will apparently be fixing them in the next security update. As Tim Gaden at Hawk Wings (where I found this) says: the classic advice of being careful about what attachments and links you open and click on should keep your Mac humming along just fine.

Wanna have some fun with Safari (or apparently any WebKit-based browser), a certain picture, and a post at the DrunkenBlog? Apparently, drunkenbatman has come across another image that can crash WebKit and anything based on it, including the Finder and Preview.

If you want the full rundown, head over to the DrunkenBlog post using something like Firefox, Camino or Opera - just not Safari, OmniWeb or any other WebKit-based browsers. If you visit the post in Safari, it will crash; this has been tested in the latest 10.4.5 update on both PPC and Intel versions. Also, whatever you do, do not download the image to your desktop, especially if (like me) you have the Finder option to "show icon preview" turned on. It'll crash Preview and send Finder into a constant crashing/restart cycle.

Like I said, you can get the full, in-depth rundown (and I mean in-depth) on this issue and its specifics at the DrunkenBlog.