The page “http://www.mikewood.org/stuff/BrianRollMoab.wmv” attempted to load an Internet plug-in named “QuickTime Plug-In 7.2”, but the plug-in failed to load successfully.
Try re-installing QuickTime. See Bug 14702 Comment #4.
(In reply to comment #1) > Try re-installing QuickTime. See Bug 14702 Comment #4. > Just got done re-installing, wish it did, but it did not solve the problem. Another thing, is webkit supposed to replace Safari? Webkit does not default launch, it does not save cookies ( I think ) it does not save things that Safari did, such as when typing in google search bar it does not remember recent searches and start to auto fill for me. I don't remember how I found webkit, I was looking for a fix to all the crashing and pages not loading on Safari after the update of 10.4.10 and even beta 3.0.3 does not work right either, I feel like I'm on an old windows system now with all the problems I did not have my previous 6 years of owning a mac. Here is one site I found where 2 other people were having the same problem. http://www.macworld.com/forums/ubbthreads/showflat.php?Cat=0&Number=516148&an=0&page=0
(In reply to comment #2) > Just got done re-installing, wish it did, but it did not solve the problem. > Another thing, is webkit supposed to replace Safari? Webkit does not default > launch, it does not save cookies ( I think ) it does not save things that > Safari did, such as when typing in google search bar it does not remember > recent searches and start to auto fill for me. The WebKit Nightly does not replace Safari. It's basically a launcher application that contains some magic that tells Safari to start up with different WebKit frameworks (libraries) and a different icon. This allows you to use the existing Safari application with an updated WebKit. There are known incompatibilities with this, though: http://trac.webkit.org/projects/webkit/wiki/Known%20incompatibilities%20between%20open-source%20WebKit%20and%20Safari The solution to this is to install the Safari 3 Public Beta for Mac OS X, which resolves these incompatibilities, and still lets you use the WebKit nightly builds (which currently are newer than the WebKit that comes with the Safari 3 Public Beta). http://apple.com/safari/ > I don't remember how I found webkit, I was looking for a fix to all the > crashing and pages not loading on Safari after the update of 10.4.10 and even > beta 3.0.3 does not work right either, I feel like I'm on an old windows system > now with all the problems I did not have my previous 6 years of owning a mac. > Here is one site I found where 2 other people were having the same problem. > http://www.macworld.com/forums/ubbthreads/showflat.php?Cat=0&Number=516148&an=0&page=0 That page talks about kernel panics and wireless issues, while you only mentioned that QuickTime would not load in Safari. Are you seeing the other issues as well? Is this a brand new Mac Book Pro that you're using? When you start the WebKit nightly, do you see any warning messages about extensions being installed (like Saft, PithHelmet, SafariStand)? If so, please remove ALL of those extensions and try using Safari again.
> > The solution to this is to install the Safari 3 Public Beta for Mac OS X, which > resolves these incompatibilities, and still lets you use the WebKit nightly > builds (which currently are newer than the WebKit that comes with the Safari 3 > Public Beta). ____________________________________________________ I have tried this already and have been on beta for a few days. Still not working. ___________________________________________ > http://apple.com/safari/ > > > I don't remember how I found webkit, I was looking for a fix to all the > > crashing and pages not loading on Safari after the update of 10.4.10 and even > > beta 3.0.3 does not work right either, I feel like I'm on an old windows system > > now with all the problems I did not have my previous 6 years of owning a mac. > > Here is one site I found where 2 other people were having the same problem. > > http://www.macworld.com/forums/ubbthreads/showflat.php?Cat=0&Number=516148&an=0&page=0 > > That page talks about kernel panics and wireless issues, while you only > mentioned that QuickTime would not load in Safari. Are you seeing the other > issues as well? _________________________________________________ I do not know what a kernal is much less a panic'd one ;-), but I started looking for solutions because after the last Safari update, not the beta, I started having crash issues, sometimes even before a page would load Safari would just shut off, and if I did get on a page, once I tried to go elsewhre it would crash, so I could only open up one page, crash, then open the next page, well since many pages require you to surf to another, that got frustrating really quick. I am on an iMac intell processor running Tiger 10.4.10. I have spent hours looking at apple trying to find what the solution to al this stuff is, I am just a user of my mac, but I don't know nor have time to learn how all this stuff works, that is why I bought a mac, I just want to use it and not have to be all up on the latest stuff, since I just can't do that even if I wanted to, so your help....... thank you so very much! __________________________________________ > When you start the WebKit nightly, do you see any warning messages about > extensions being installed (like Saft, PithHelmet, SafariStand)? If so, please > remove ALL of those extensions and try using Safari again. > __________________________________________ I don't see anything come up and tell me anything, I would not have a clue where to even look to find that stuff either. __________________________________________
OH btw, what is drosera for?
(In reply to comment #5) > OH btw, what is drosera for? Drosera is a developer tool for debugging JavaScript. It won't help to diagnose your crashes, though. http://webkit.org/blog/?p=61
(In reply to comment #4) > I do not know what a kernal is much less a panic'd one ;-), but I started > looking for solutions because after the last Safari update, not the beta, I > started having crash issues, sometimes even before a page would load Safari > would just shut off, and if I did get on a page, once I tried to go elsewhre it > would crash, so I could only open up one page, crash, then open the next page, > well since many pages require you to surf to another, that got frustrating > really quick. > I am on an iMac intell processor running Tiger 10.4.10. > I have spent hours looking at apple trying to find what the solution to al this > stuff is, I am just a user of my mac, but I don't know nor have time to learn > how all this stuff works, that is why I bought a mac, I just want to use it and > not have to be all up on the latest stuff, since I just can't do that even if I > wanted to, so your help....... thank you so very much! I'm sorry your initial experience with a Mac has been so frustrating. If Safari is crashing for you frequently, could you try pasting any "crash log" you get into this bug report? This web page tells you what to do when you see one (the irony is not lost on me!): http://webkit.org/quality/crashlogs.html Note that previous crash logs are saved in your home directory (Cmd-Shift-H in the Finder) in the Library/Logs/CrashReporter directory structure in a file called Safari.crash.log. If you could attach that file to this bug (via the "Create a New Attachment" link on this bug), that may be helpful in diagnosing the issue. If the file is too big to attach, please email it to me using my address on this page (if you don't mind). Thanks for your patience!
> I'm sorry your initial experience with a Mac has been so frustrating. If > Safari is crashing for you frequently, could you try pasting any "crash log" > you get into this bug report? This web page tells you what to do when you see > one (the irony is not lost on me!): > > http://webkit.org/quality/crashlogs.html > > Note that previous crash logs are saved in your home directory (Cmd-Shift-H in > the Finder) in the Library/Logs/CrashReporter directory structure in a file > called Safari.crash.log. If you could attach that file to this bug (via the > "Create a New Attachment" link on this bug), that may be helpful in diagnosing > the issue. > > If the file is too big to attach, please email it to me using my address on > this page (if you don't mind). > > Thanks for your patience! > Sorry to have given the impression I am not in love with my mac. This is gonna be 7 years of pleasurable ownership of a mac, I am just not happy with it since the last update. I was trying to briefly describe that I'm not a tech kinda guy and thus the reason I bought a mac to begin with..... ease of use, until lately ;) Here is my crash log as it is huge.( sent to you via e-mail ) Thanks again so much for the help. As far as you thanking me for my patience, no, thank you for yours!
One other thing to clarify, I've got the crash/just shutting down problem and no loading of some content with Safari, and then the QT plug-in problem with Webkit.
Created attachment 15977 [details] Safari crash log Latest Safari crash log.
Comment on attachment 15977 [details] Safari crash log I've never seen a crash log quite like this one, but I do see that you have SafariStand installed (/Users/kirk/Library/InputManagers/SafariStand/) as well as something called Magic Menu Enabler (/Library/InputManagers/MagicMenuEnabler/): 0x474000 - 0x474fff jp.hetima.SafariStand.loader SafariStand-loader version 1.0.1 (6) /Users/kirk/Library/InputManagers/SafariStand/SafariStand-loader.bundle/Contents/MacOS/SafariStand-loader 0x4fb000 - 0x4fbfff com.aladdinsys.mmenabler 7.1.0 (98) /Library/InputManagers/MagicMenuEnabler/MagicMenuEnabler.bundle/Contents/MacOS/MagicMenuEnabler 0x1020000 - 0x105bfff jp.hetima.SafariStand 2.0b14 (123) /Users/kirk/Library/InputManagers/SafariStand/SafariStand.bundle/Contents/MacOS/SafariStand 0x32000000 - 0x32042fff isao.sonobe.OgreKit ??? (2.1.0) /Users/kirk/Library/InputManagers/SafariStand/SafariStand.bundle/Contents/Resources/OgreKit.framework/OgreKit I would start by removing those items from their respective directories (drag them to the Desktop, for example), and reboot. Then try viewing a QuickTime movie to see if there are any issues remaining.
Please note that SafariStand (and similar software) are highly dependent on specific versions of Safari, and none of them have probably been updated to work with the Safari 3 Public Beta that you have installed.
(In reply to comment #12) > Please note that SafariStand (and similar software) are highly dependent on > specific versions of Safari, and none of them have probably been updated to > work with the Safari 3 Public Beta that you have installed. > Ok, have removed both stand and magic menu, ( don't even remember what I installed those for, much less what they are supposed to have done ) but alas..... nothing was fixed. Still can't get apples demo video to play for the new version of iMovie on Safari, and Webkit still can not load the QT plug-in. Here is one of the pages I tried to view. http://www.heli-chair.com/videos_public/full_scale_heli_videos/ground_resonance/Ground_Resonance_Rear_View.mpg
(In reply to comment #13) > Ok, have removed both stand and magic menu, ( don't even remember what I > installed those for, much less what they are supposed to have done ) but > alas..... nothing was fixed. > Can you upload a new crash log?
(In reply to comment #14) > (In reply to comment #13) > Can you upload a new crash log? > Nothing has "crashed" lately as I understand it to mean. IE Safari has not shut down, both it and webkit have mostly just not been able to open certain things. Am I correct in my thinking?
Ok, I found another crash log, the first one I sent was from the main library folder, I looked in my home library folder and found this one today. I'll try and upload it, if I copy and paste the text...well...uh.... I think I'd use up al this place's bandwidth. lol I tried to attach file, it is too big, 4.6 mb. Anyone want me to e-mail it to them? my e-mail is captkirkyota@gmail.com
Created attachment 15981 [details] Original Safari.crash.log (4.6 MB; bzip2) This is the original Safari crash log. It starts with OS X 10.4.7 and Safari 2.0.4 and progresses through various OS X upgrades and the Safari public betas. Nearly every single crash log is identical (some crash with Thread 0 or Thread 1 in strstr + 72) except two using a WebKit Nightly r24285 where one crashed in a Flash plug-in and one crashed in WebCore::RenderObject::setStyle(). I just noticed something REALLY strange. This is an Intel-based Mac, yet "Rosetta: Yes" is set on every one of the crash logs EXCEPT the ones where the WebKit nightly build was running. Why is Safari running under Rosetta on an Intel-based Mac when it should be a universal binary? That might explain the strange crashes and the reason why QuickTime won't work.
Kirk, please try following the step-by-step instructions in this article, except that you wan to UNCHECK the "Open using Rosetta" checkbox. http://docs.info.apple.com/article.html?artnum=303120 After doing that, please try viewing movies in Safari again.
Weird. Adobe recommends doing this so that Shockwave Player runs on Intel-based Macs: http://kb.adobe.com/selfservice/viewContent.do?externalId=82216d24&sliceId=2 And OS News recommends doing this so Microsoft's old WMV play will run on Intel-based Macs: http://www.osnews.com/story.php/13902/How-to-Get-Your-Intel-Mac-to-Play-WMV-Files/ Is this a common thing to suggest?
Disabled Rosetta, quit Safari, started back up and still no plug-in at the pages I've linked to. BTW, I've had this intel mac since late 2005 I think,( shortly after the intel ones came out) have always had Rosetta enabled for the reasons the linked articles state and the current issues are just that, current, but I'm willing to do what you guys ask since you are trying to help ME..... an unskilled user, so thanks. BTW, does anyone want me to e-mail them the crash log I found this morning? If so e-mail me so I can reply back to you with it. captkirkyota@gmail.com
(In reply to comment #20) > Disabled Rosetta, quit Safari, started back up and still no plug-in at the > pages I've linked to. Just for fun, you might try rebooting when convenient. Also, make sure that the Rosetta setting is unchecked before launching Safari after the reboot (just to be safe). > BTW, does anyone want me to e-mail them the crash log I found this morning? > If so e-mail me so I can reply back to you with it. Send it to me again.
Another thing you could try (to eliminate settings in your own account) is to create a brand new account on your Mac, log in, and try running Safari and viewing a QuickTime movie. This would eliminate anything wrong with the system in general, and narrow the issue down to settings in your primary account. (You may always delete the additional account later.)
(In reply to comment #22) > Another thing you could try (to eliminate settings in your own account) is to > create a brand new account on your Mac, log in, and try running Safari and > viewing a QuickTime movie. This would eliminate anything wrong with the system > in general, and narrow the issue down to settings in your primary account. > (You may always delete the additional account later.) That wasn't very clear. If Safari still crashes or doesn't play QuickTime in the new account, that means there's an issue with the system (not your account specifically). We won't know what, but we can eliminate settings in your account as being the cause. If Safari works in the new account (and doesn't crash), that means that there is probably some setting (or software in ~/Library/) in your primary account that is causing this issue.
Reboot.... as in trash Safari and download the app. again? Gonna try the account thing right now.
Ok, video does work on a virgin test account, it is kinda sketchy but it would play, so how do I proceed from here?
(In reply to comment #24) > Reboot.... as in trash Safari and download the app. again? > Gonna try the account thing right now. I didn't mean for you to delete Safari! But I guess it's easy enough to reinstall the public beta. (In reply to comment #25) > Ok, video does work on a virgin test account, it is kinda sketchy but it would > play, so how do I proceed from here? "Sketchy" meaning it stuttered when playing? That's could be any number of issues from your CPU load to internet bandwidth to how busy the web site on the other end is. We have movies playing, which is the first step. :) As far as how to proceed, if I had to guess, there is probably some setting (accessible through the "defaults" command in a Terminal) or some software that gets loaded at login time (under ~/Library somewhere). I'll give you some suggestions, but the fix will likely be technical in nature, and it's really beyond the scope of using Bugzilla. 1. It may be useful to make an appointment with the Genius Bar at a local Apple Store (if that's convenient) to take a look. 2. You could try using Spring Cleaning to see if that magically fixes the issue. Unfortuantely, it's $50 and there is no guarantee that it will fix the issue, so make sure you're prepared to "throw away" $50 if it doesn't work. (I don't own it, and I've never tried it, so take this with a grain of salt.) http://www.allume.com/mac/springcleaning/index.html 3. Copy files from your old account to your new account and just start using the new account as your primary one. This could be a bit tricky (you must be careful what you copy over from ~/Library). This article covers the basics: http://www.macfixit.com/article.php?story=20060123081353849 4. [HIGHLY TECHNICAL] Open a Terminal, run "defaults read | less", and review suspicious settings (anything to do with Rosetta, Safari, or QuickTime). You could then (after making a backup copy of the settings) start removing suspicious settings to see if they eventually fix the issue. You could also compare "defaults" settings from the old account with the new account to see what's different (especially with Rosetta, Safari and QuickTime), to get a better idea of what settings you may want to try removing first. Note that I've actually had to do this before after using an app that was supposed to let you manipulate all kinds of secret Safari settings. It set something that caused Safari to behave badly (I don't recall what it did), but I ended up getting back to a point where it worked again. Again, this is a highly technical operation, and you could make things worse if you're not sure what you're doing. :)
Kirk, since this appears to be a configuration issue and not a WebKit bug, I'm going to mark this bug as RESOLVED/INVALID. Note that you may still add comments to the bug if you eventually find the cause of the problems. Good luck!