Existing users, 
Advanced Search
 Apple QuickTime - 7.5multimedia player & authoring system |
|
||||||||||||||
|
|||||||||||||||
Feedback Summary:
| This Version: | |||||
| Overall Rating: | Not rated (0.0) | Features: | Not rated (0.0) | Support: | Not rated (0.0) |
| Ease of Use: | Not rated (0.0) | Quality / Stability: | Not rated (0.0) | Price: | Not rated (0.0) |
Key to Types of Feedback:
Reviews 
Troubleshooting 
Usage Tips 
Developer Notes 
Commentary 
Featured Reviews
WELL APPLE ???????????? 
- Version: 7.5, 7/26/2008 10:23PM PST
(1 of 1 users found this comment useful)
NeinJuden
Just Great... - Version: 7.5, 6/16/2008 09:50PM PST
(2 of 2 users found this comment useful)
MacGuffin
Between this and the iTunes update experienced LOUSY video playback so I took MacFixIt's advice and deleted the suggest files. Playback was restored to near-nomal level...for just about one day. Back to square one and lousy playback. This REALLY sucks. Yeah, yeah...repaired permissions before and after, rebooted in safe mode, removed third-party files...
QT 7.5 Breaks Safari 3.1.1 (Tiger; 10.4.11) - Version: 7.5, 6/14/2008 01:16PM PST
(2 of 2 users found this comment useful)
DrAnnAtomy
Prior QT versions have been A-OK for years. But 7.5...
Installation was uneventful but after reboot, Safari's kaput. Every attempt to start the app yields gobs of this kind of crashreporter data:
Sat Jun 14 12:27:19 2008 crashreporterd[175]: crashdump[336] exited due to signal 10
Sat Jun 14 12:27:19 2008 crashreporterd[175]: reaping /var/db/crashdump/crashdump.lock
Sat Jun 14 12:27:19 2008 crashreporterd[175]: eof from crashdump
Sat Jun 14 12:27:19 2008 crashreporterd[175]: crashdump[335] exited due to signal 10
Sat Jun 14 12:27:19 2008 crashreporterd[175]: reaping /var/db/crashdump/Safari.lock
Sat Jun 14 12:27:19 2008 crashreporterd[175]: eof from crashdump
Disk Utility reports that all's well. So I Googled an old Apple URL ("Safari quits unexpectedly"; http://support.apple.com/kb/TS1594) and manually removed the "com.apple.quicktime.plugin.preferences.plist" file.
No-go.
So I also removed the "QuickTime Plugin.webplugin" (again) as recommended by "iDelete QT and Flash Caches" (v1.3; freeware here on VT).
No-go.
So I re-installed Safari (via "Safari311UpdTiger.dmg" from "Safari311UpdPPC.pkg").
No-go.
So Tiger folks, beware. Install QT 7.5 at your (and/or Safari's) peril. Because as of this writing, I've no clue what to do. (And if it takes 'reinstalling my system software' or removing every single Safari-related plist to test for some newly QT-created conflict -- heck no. I'll simply use Firefox or Camino, tenkyewveddymuch.)
Installation was uneventful but after reboot, Safari's kaput. Every attempt to start the app yields gobs of this kind of crashreporter data:
Sat Jun 14 12:27:19 2008 crashreporterd[175]: crashdump[336] exited due to signal 10
Sat Jun 14 12:27:19 2008 crashreporterd[175]: reaping /var/db/crashdump/crashdump.lock
Sat Jun 14 12:27:19 2008 crashreporterd[175]: eof from crashdump
Sat Jun 14 12:27:19 2008 crashreporterd[175]: crashdump[335] exited due to signal 10
Sat Jun 14 12:27:19 2008 crashreporterd[175]: reaping /var/db/crashdump/Safari.lock
Sat Jun 14 12:27:19 2008 crashreporterd[175]: eof from crashdump
Disk Utility reports that all's well. So I Googled an old Apple URL ("Safari quits unexpectedly"; http://support.apple.com/kb/TS1594) and manually removed the "com.apple.quicktime.plugin.preferences.plist" file.
No-go.
So I also removed the "QuickTime Plugin.webplugin" (again) as recommended by "iDelete QT and Flash Caches" (v1.3; freeware here on VT).
No-go.
So I re-installed Safari (via "Safari311UpdTiger.dmg" from "Safari311UpdPPC.pkg").
No-go.
So Tiger folks, beware. Install QT 7.5 at your (and/or Safari's) peril. Because as of this writing, I've no clue what to do. (And if it takes 'reinstalling my system software' or removing every single Safari-related plist to test for some newly QT-created conflict -- heck no. I'll simply use Firefox or Camino, tenkyewveddymuch.)
Most Recent Replies: View All 2 Replies
- QT 7.5 Breaks Safari 3.1.1 (Tiger; 10.4.11)
It took me 3 to 4 weeks, 8 to 10 hours a day. I'm finally done, long story don't ask.
For everyone that hasn't upgraded, you've been warned.
If you upgrade now, the pain you suffer is your own fault.