QT 7.3 not working in Leopard

Worked fine in Tiger, but I only get the ? icon in Leopard - this is in all apps., not just Safari.

Does this have anything to do with it?: When I create a report to send to Apple, I notice in the report that it says the Quicktime is version 7.2 --- HOWEVER, everything else says its version 7.3.
It could. Next time you open the player, check the version number. I have a similar problem. My second internal drive has an older OS with QT v7.0.3 on it. When I double-click on a movie in the finder the chances are 50-50 it will open in the older player if the v7.3 player is not already open.

Similar Messages

FileReference Select and Cancel Event Not Working in leopard

FileReference not working in leopard
<?xml version="1.0" encoding="utf-8"?>
<mx:Application xmlns:mx="
http://www.adobe.com/2006/mxml"
layout="absolute">
<mx:Script>
<![CDATA[
import mx.controls.Alert;
public function onClick():void{
var fr:FileReference=new FileReference();
//fr.addEventListener(
fr.addEventListener(Event.OPEN,openHandler);
fr.addEventListener(Event.COMPLETE,completeHandler);
fr.addEventListener(Event.SELECT,selectHandler);
fr.addEventListener(Event.CANCEL,cancelHandler);
fr.addEventListener(DataEvent.UPLOAD_COMPLETE_DATA,uploadCompleteDataHandler);
fr.addEventListener(HTTPStatusEvent.HTTP_STATUS,httpStatusHandler);
fr.addEventListener(IOErrorEvent.IO_ERROR,ioErrorHandler);
fr.addEventListener(ProgressEvent.PROGRESS,progressHandler);
fr.addEventListener(SecurityErrorEvent.SECURITY_ERROR,securityErrorHandler);
fr.browse([new FileFilter("images", "*.png;*.jpg;*.gif")]);
private function cancelHandler(event:Event):void {
trace("cancelHandler: " + event);
private function completeHandler(event:Event):void {
trace("completeHandler: " + event);
private function
uploadCompleteDataHandler(event:DataEvent):void {
trace("uploadCompleteData: " + event);
private function
httpStatusHandler(event:HTTPStatusEvent):void {
trace("httpStatusHandler: " + event);
private function ioErrorHandler(event:IOErrorEvent):void {
trace("ioErrorHandler: " + event);
private function openHandler(event:Event):void {
trace("openHandler: " + event);
private function progressHandler(event:ProgressEvent):void {
var file:FileReference = FileReference(event.target);
trace("progressHandler name=" + file.name + " bytesLoaded="
+ event.bytesLoaded + " bytesTotal=" + event.bytesTotal);
private function
securityErrorHandler(event:SecurityErrorEvent):void {
trace("securityErrorHandler: " + event);
private function selectHandler(event:Event):void {
Alert.show("XD");
]]>
</mx:Script>
<mx:Button x="205" y="198" label="Button"
click="onClick()"/>
</mx:Application>
Adobe Flex Builder 3 Beta3
Leopard 10.5.1
both Safari and firefox doesn't work

Flash version is 115 debug player

Photoshop 7 DOES NOT WORK with Leopard ( OS 10.5 )

If you are not prepared to upgrade your Photoshop 7, DO NOT UPGRADE TO LEOPARD.
Photoshop 7 and OS 10.5.x (Leopard) are not compatible. When Adobe released Photoshop 7 in 2001 as a Universal Binary for OS9 and OSX they had no idea that Apple would be switching to an Intel chip in 2006. As the release of Leopard is also the end of the Classic environment, this may be the reason Photoshop 7 does not work in Leopard.
As of the release of CS4, Photoshop 7 can no longer be used as a path to upgrade Photoshop. A full version has to be bought now. But Photoshop CS or later can still be used as an upgrade to Photoshop CS4.
It is recommended that Photoshop 7 owners still looking to save money on upgrades stay away from eBay, as, unfortunately, much of the software listed is pirated or misrepresented and you will still not be able to upgrade to CS4.
[topic updated by Forum Host]

There is a third party version of Firefox 4 that runs on OS X 10.4/10.5 and PPC Macs, for details see http://www.floodgap.com/software/tenfourfox

Widget: "screenshot plus", not working in leopard, etc...

widget: "screenshot plus", not working in leopard. another bug? kids digital camera opens iphoto but doesnt appear on desktop to eject w/out errors. another bug? if i havnt registered leopard yet, can i sell it, cuz i think i might not want it now.

These aren't bugs, they are 3rd party issues that are not Apple's responsibility. Whomever wrote the widget needs to update it for Leo. The camera manufacturer needs to update their hardware driver to be Leo compatible.
I'm sure someone will take Leo off you hands for a better price than elsewhere. It's a great OS.

TS1394 Software Update NOT WORKING (Snow Leopard)

Software Update NOT WORKING (Snow Leopard)
Hi, I am currently using Snow Leopard 10.6 on my iMac. I opened iTunes and was told there was an update available so I clicked the button to download it. This obviously opened up the 'download' screen with blue bar. The blue bar does not move and the message comes up that the download failed. I have tried troubleshooting, but the message I get is that I am not connected to the internet - which I am.
Please help.

Check your iTunes version, it's reporting v10.6.3 here on 10.6.8 and no updates required.
You should be able to download it from here
https://www.apple.com/itunes/

Adobe CS2 will not work in Leopard

Did you know *_Adobe CS2 will not work in Leopard?_* I found out the hard way that Leopard doesn't cost $129; It's $729, because CS2 will not work so you need to upgrade to CS3. This is straight from Adobe support (albeit in Manilla). I can find no documentation on either site that warns you not to upgrade to Leopard if you're running CS2. I am dead in the water until CS3 arrives. Nice move Apple and Adobe. I usually like to get kissed first.

I'm using Adobe Photohsop CS1 and it is working. There are a couple of little glitches, but nothing major. And whenever there is a major system upgrade you can ALWAYS figure there are some things that are going to break, which is why it is a good plan to install a new system on a new drive or second partition. AFAIK the things that don't work and will never work are Photoshop 7 and Elements 2.
Francine
Francine
Schwieder

FCP not working with Leopard

Every time I try and launch FCP5 Studio 2 it gives me the "This application Final Cut Pro quit unexpectedly." Anyone have a solution to this? Anyone else experienced this?
Do I just have to wait for an update?

Having same problem with FCP v 6.0.1 and tried the FCP Rescue 6..... Also does not work with Leopard.
I am just about to try this proceedure.
Delete the User Preferences
You can resolve many issues by restoring Final Cut Pro back to its original settings. This will not impact your project files, but you should verify your Scratch Disk location setting after doing this. To reset your Final Cut Pro user preference settings to their original state, do the following:
In the Finder, go to ~/Library/Preferences—the tilde (~) represents your Home folder.
Remove the “com.apple.finalcutpro.plist” file from the Preferences folder.
Remove the “Final Cut Pro User Data” folder from the Preferences folder.
Will report shortly.

Treo 700WX DUN: Does NOT work in Leopard! Anyone have luck?

I have a Treo 700WX with Sprint. I can't connect with Bluetooth or USB. When I used Tiger I was able to make it work just fine.
Now with Leopard...It does NOT work. The modem disconnects during connection. I just can't get online plain and simple.
At first I was blaming my Treo. But I tested it out on my Vista Partition and it worked! So the problem lies within Leopard.
Apple did a lowsy job on the Networking features in Leopard thus far.
*Has anyone gotten Leopard to use DUN (Dialup Networking) with a cellular Device?*
Again I'm using a Treo 700 WX (Windows Mobile 5) with the 1.15 software installed. I've also tried to install USB Modem (by Mobile-Stream) which enables USB connectivity. It still does not work. Same errors.
I was camping in the middle of nowhere for 5 WHOLE DAYS with no Internet!!!!!!! hehe jk I was actually happy about that. Excuse not to work! :P But there may be a day when I need DUN.
I don't have the "Phone as Modem" through Sprint. However you don't need it on your plan for this phone.

MikeyPD,
Sprint DUN is working just dandy for me, but I am using phone-as-modem, and with an A900M, not a Treo. You probably know more about the differences than I, but I would expect they both use the same protocols to connect (on both ends).
For me, it was a snap to set things up in Leopard. Actually easier than Tiger. Do you use a standard DUN connection, or must you use some other method for the Treo, running Windows Mobile?
Assuming it is standard DUN, let's go through the steps. First, is there any indication that the Treo is recognizing the connection as a request for DUN service (for example, my A900M clearly states that it is being used as a Data Modem)? Do you have the modem script set to dial #777? OK, here's the "Duh!!!" question: Do you have the modem script set to ignore the dial tone? If you do not have it set to "ignore," it will immediately fail every time.
Scott

Remote not working after Leopard update

I've read about, and have the problems reported with Front Row when it comes to viewing content on another (TV) screen, but does anyone share my problem about the remote control not working at all?
This morning before I upgraded to Leopard it worked fine, but since then, no matter which button I press, nothing happens at all.
I've to launch Front Row manually, either by launching the new app, or the CMD Esc command, but the 'Menu' button on the remote doesn't do anything.
It certainly isn't an issue with the remote as my iPod still responds to the commands when it is sat in the iPod Dock that has the remote receiver on it.

To provide closure on this thread, I now have it working!
Got all the ideas from the iSight thread listed above, here's what I did.
Firstly, shut down the computer, disconnected everything from the back of it, gave it a dust around the back of the iMac, blew out the cobwebs so to speak.
Left it ten minutes, made myself a drink.
Returned and restarted the computer, but applying the reset PRAM command, which is after switching on immediately hold down the Command, Option, P and R keys.
You'll hear a second chime, release the keyboard and the computer will boot up.
Once everything had loaded, I launched iSight and lo and behold, there was my ugly mug staring back at me, iSight was once again working.
I then proceeded to the System Preferences to see if I could get the remote working. There was the IR instructions at last including details on how to pair the remote.
Pointing my remote to the screen I held down the Menu and Next/FFWD button until a chain and the remote symbol appeared on the screen.
With my remote paired with my iMac, everything was finally working again after two days of installing Leopard, Tiger and the Leopard again!
Now Apple, how about sorting out Front Row working properly when pictures are DV'd out to a TV!??

DNS does not work after Leopard utdate

Hello!
We are using an G5 XServe. Until recently we used 10.3.9.
With this configuration everything worked, but when we updated from 10.3.9 to 10.5.1 the troubles began.
All the DNS info from server admin is gone. And the network does not work as it did before.
I can still see the info in the files via terminal, but it is not present in server admin.
We cloned the server disk to an external drive before updating. When we start from this disk everything works great.
I have been searching the net for a while and found this article:
http://www.afp548.com/article.php?story=20071031195155456&query=Leopard%2BDNS
It mentions a bug causing DNS to crash badly if service is updated and saved. I updated the service when I updated to 10.5, and I saved it afterwards...
Does anyone have any tips? Im really need to get this up and running!
I suppose I could clone the server back from the backup, update to 10.5 and NOT upgrade the DNS service. However I hope there is another solution..
Any help would be greatly appreciated!
Thanks
Message was edited by: wiitho

In a few hour its back to work..
I have not found any absolute answer to my problem.
I thing Ill try the "clone back and dont update DNS service" option. However, there is one concern:
Will it help to not update the DNS service? Or will I be facing the same problem again after updating to 10.5? If anybody knows I would appreciate any answer
Thanks!

Wacom Intous2 not working in Leopard 10.5.1

Today I suddenly found that my Wacom Intous2 no longer works with Leopard (iMac 24", 2.4G Core2Duo). Nothing happens when I tap/move the pen on the tablet, as if the tablet is not connected at all. However, here comes the funny part: if I uninstall the tablet driver (6.0.5-3), the tablet acts like a mouse (but it's useless for my job because I can't map the tablet area to the screen area). So it must be the driver that causes the problem.
When the 6.0.5-3 driver is installed and I launch the tablet preference applet, it does show "Intuos2 6x8" in the "tablet" row. But the lower half of the window is different than what I saw on Tiger: on Tiger I had a mapping diagram that allows me to map the tablet area to screen area. Now I don't have it. And as mentioned earlier, when driver is installed, the tablet doesn't respond at all -- as if it were not connected though the LED light on the tablet is on (orange).
In the diagnose screen of tablet preference, it does show the following info:
Driver info: version: 6.0.5-3
Tablet: Intuos2 6x8
Model: Intuos2 6x8
Version: 1.15
OEM Code: 0
But all other rows are grayed out and blank. If I unplug the USB cable I saw the same info in Diagnose screen.
The tablet hardware itself is fine because it works with other computers (PC & other Tiger Macs). The tablet also worked well with Tiger on the same iMac. I haven't used it for a while since upgrading to Leopard and then 10.5.1. So I'm not sure at which exact moment it stopped working.
I've spent hours searching on google and this forum for solutions. I've tried everything I read, including the following:
1. Uninstall current driver, restart, install the latest Leopard driver -- which is 6.0.5-3 dated Nov 29 2007 -- no help.
2. Uninstall current driver, fix hard drive permission (as suggested by Wacom FAQ), install the latest driver -- no help.
3. Change a different USB port (it's always connected directly to the USB ports on the back of iMac. Never used a hub or extension cable) -- no help. The USB port must be fine because it works with other devices like kb, mouse, usb driver, ext hd, etc.
4. I have another 2 macbooks with Leopard 10.5.1. I tried to connect tablet on each of them but saw exactly the same problem: no driver -- acts as mouse; with driver -- not responding.
Did any one meet the same problem? Any hints? Thanks a lot for any info that might or might not help.

I don't know if this will help but I'm posting it anyways, because it worked for me.
I called into apple support and explained my problem.
First thing he had me do was shut down my computer, unplug everything, take the battery out (i have a macbook pro) then with the battery out hold down the power button for "5 to 8 seconds".
After that I put the battery back in, plug the power cord and the tablet in, turn on the computer...
tablet still doesn't work right, but that's not to say that didn't help.
So I go to the applications folder, go to the pen tablet folder, and open up the file "Remove Pen Tablet".
First I do "Remove all Preference files"
than I do "Remove Tablet Software"
I restart my computer, open up the wacom driver that I downloaded from wacom's website. run the installation. And now my tablet is working just like it should.
I don't know if I'll have the problem where I'm going to have to reinstall the driver after every reboot, but as of now it's good.
For that first step I don't know what it's called, something like power rebooting or something, i only know how to do it for my computer not a desktop or anything
hope that helps

Internet working in windows xp, not working in leopard (dual boot)

i have a problem with connecting to the internet in leopard, but not in windows xp. i'm on a dual boot machine (mac mini g5 1.66).
the problem started in an odd way:
everything was working fine, i left the computer open for a few hours (fell asleep) and when I came back I couldn't connect to the internet whatever browser I was using. I restarted the computer in windows and it works fine. Obviously this is not a problem related to the modem or the cables - something must have changed in Leopard. But I did not install any program recently.
I checked the Network tab in System Pref - nothing wrong, I checked disk permissions and corrected them - no change, I checked for unusual threads or processes in Activity Monitor - nothing.
I tried using the Network Utility and sent a few pings, but it's not working. However, both the Network Utility and Activity Monitor report outgoing and incoming packets of data, as if the connection were working.
Can you help me solve this problem without reinstalling the entire operating system? Thanks.

Is there anyone who knows the networking workings in Leopard to help me identify the problem??
I have no modem problem, since I can use the same system in dual boot with Windows XP. The problem must be a file or a setting in Leopard that is blocking my connection to the internet.
I dunno, it could be related to Java or how some scripts are executed by the operating system.
If I don't solve this one, I'll have to reinstall the whole system again. Come on, help me guys!

Photoshop CS not working in Leopard !

Got Snow Leopard when it came out and had no problems at all for the last few weeks using Photoshop CS until today when i get," Adobe CS quit unexpectedly".
I can't think of anything that has changed,it was working fine yesterday.
Here is the "Problem Details and System Configuration " report:
Process: Photoshop [222]
Path: /Applications/Adobe Photoshop CS/Adobe Photoshop CS.app/Contents/MacOSClassic/Adobe Photoshop CS
Identifier: com.adobe.Photoshop
Version: ??? (???)
Code Type: PPC (Translated)
Parent Process: launchd [90]
Date/Time: 2009-10-26 09:47:48.251 +0000
OS Version: Mac OS X 10.6.1 (10B504)
Report Version: 6
Interval Since Last Report: 1181 sec
Crashes Since Last Report: 8
Per-App Crashes Since Last Report: 8
Anonymous UUID: 11B008B4-2212-4C4E-A2F1-634C284CC805
Exception Type: EXCBADACCESS (SIGBUS)
Exception Codes: KERNPROTECTIONFAILURE at 0x0000000000000000
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Thread 0 Crashed: Dispatch queue: com.apple.main-thread
0 LaunchCFMApp 0xb80c5e94 0xb8000000 + 810644
1 LaunchCFMApp 0xb80c01bb 0xb8000000 + 786875
2 LaunchCFMApp 0xb80dda6c 0xb8000000 + 907884
3 LaunchCFMApp 0xb814551b spinlockwrapper + 1791
4 LaunchCFMApp 0xb801d03b 0xb8000000 + 118843
Thread 1:
0 libSystem.B.dylib 0x800c57da machmsgtrap + 10
1 libSystem.B.dylib 0x800c5f47 mach_msg + 68
2 LaunchCFMApp 0xb819448f CallPPCFunctionAtAddressInt + 206155
3 libSystem.B.dylib 0x800f2f39 pthreadstart + 345
4 libSystem.B.dylib 0x800f2dbe thread_start + 34
Thread 2:
0 LaunchCFMApp 0xb815ae44 spinlockwrapper + 90152
1 LaunchCFMApp 0xb8179d27 CallPPCFunctionAtAddressInt + 97763
2 LaunchCFMApp 0xb80c6c97 0xb8000000 + 814231
3 LaunchCFMApp 0xb80c01bb 0xb8000000 + 786875
4 LaunchCFMApp 0xb80dda6c 0xb8000000 + 907884
5 LaunchCFMApp 0xb814551b spinlockwrapper + 1791
6 LaunchCFMApp 0xb801d03b 0xb8000000 + 118843
Thread 3:
0 LaunchCFMApp 0xb815aa83 spinlockwrapper + 89191
1 LaunchCFMApp 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
2 LaunchCFMApp 0xb80c6c97 0xb8000000 + 814231
3 LaunchCFMApp 0xb80c01bb 0xb8000000 + 786875
4 LaunchCFMApp 0xb80dda6c 0xb8000000 + 907884
5 LaunchCFMApp 0xb814551b spinlockwrapper + 1791
6 LaunchCFMApp 0xb801d03b 0xb8000000 + 118843
Thread 4:
0 LaunchCFMApp 0xb815aa83 spinlockwrapper + 89191
1 LaunchCFMApp 0xb8176f29 CallPPCFunctionAtAddressInt + 85989
2 LaunchCFMApp 0xb80c6c97 0xb8000000 + 814231
3 LaunchCFMApp 0xb80c01bb 0xb8000000 + 786875
4 LaunchCFMApp 0xb80dda6c 0xb8000000 + 907884
5 LaunchCFMApp 0xb814551b spinlockwrapper + 1791
6 LaunchCFMApp 0xb801d03b 0xb8000000 + 118843
Thread 0 crashed with X86 Thread State (32-bit):
eax: 0x00000000 ebx: 0xb80c5e6c ecx: 0x00000000 edx: 0x00000003
edi: 0x00000000 esi: 0x804037f0 ebp: 0xb7fffa08 esp: 0xb7fff9d0
ss: 0x0000001f efl: 0x00010206 eip: 0xb80c5e94 cs: 0x00000017
ds: 0x0000001f es: 0x0000001f fs: 0x00000000 gs: 0x00000037
cr2: 0x00000000
Binary Images:
0x80000000 - 0x8006afe7 libstdc++.6.dylib ??? (???) <411D87F4-B7E1-44EB-F201-F8B4F9227213> /usr/lib/libstdc++.6.dylib
0x800c5000 - 0x80269feb libSystem.B.dylib ??? (???) <E58B649F-FFDC-AB09-2028-8B706BEF7C0F> /usr/lib/libSystem.B.dylib
0x802e9000 - 0x802ecfe7 libmathCommon.A.dylib ??? (???) <1622A54F-1A98-2CBE-B6A4-2122981A500E> /usr/lib/system/libmathCommon.A.dylib
0x8fe00000 - 0x8fe4162b dyld 132.1 (???) <211AF0DD-42D9-79C8-BB6A-1F4BEEF4B4AB> /usr/lib/dyld
0xb8000000 - 0xb81defff LaunchCFMApp ??? (???) <3E4E06B8-E1FC-B232-1371-643DC0FBE8C9> /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp
0xffff0000 - 0xffff1fff libSystem.B.dylib ??? (???) <E58B649F-FFDC-AB09-2028-8B706BEF7C0F> /usr/lib/libSystem.B.dylib
Translated Code Information:
Rosetta Version: 22.23
Args: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp /Applications/Adobe Photoshop CS/Adobe Photoshop CS.app/Contents/MacOSClassic/Adobe Photoshop CS
Exception: EXCBADACCESS (0x0001)
Thread 0: (0xb009ad38, 0xb815ae44)
0x95c8d588: /usr/lib/libSystem.B.dylib : _dispatch_mgrinvoke + 228
0x95c8d0c0: /usr/lib/libSystem.B.dylib : _dispatch_queueinvoke + 320
0x95c8d244: /usr/lib/libSystem.B.dylib : _dispatch_workerthread2 + 364
0x95c8d380: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 76
0x95badda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x95c8d550 ctr: 0x95b512d4
r00: 0x0000016b r01: 0xf0080bb0 r02: 0x00000000 r03: 0x00000004
r04: 0x00000000 r05: 0x00000000 r06: 0xf0080d0c r07: 0x00000001
r08: 0xf0080d28 r09: 0x00000000 r10: 0x0000003e r11: 0xa0922524
r12: 0x95b512d4 r13: 0x10624dd3 r14: 0x95cdcb2c r15: 0xf0080c0c
r16: 0xf0080c8c r17: 0xa093d4ac r18: 0xf0080d28 r19: 0xa09374f8
r20: 0xa09384f8 r21: 0xf0080d0c r22: 0xa0937478 r23: 0xa09373f8
r24: 0xa093d4ac r25: 0x00000000 r26: 0x00000000 r27: 0xa09295c8
r28: 0xa0929300 r29: 0xa09295c8 r30: 0xf0080d28 r31: 0x95c8d4ac
Thread 1: (0xb011cd74, 0xb815aa83)
0x95c8f0b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
0x95c8d3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
0x95badda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x95c8f0cc ctr: 0x95b0d6c0
r00: 0xffffffda r01: 0xf0101dc0 r02: 0x00000000 r03: 0x00002403
r04: 0x00000040 r05: 0x3b9aa752 r06: 0x00000020 r07: 0x00000000
r08: 0x3b9aa752 r09: 0x00000000 r10: 0x3b9aa752 r11: 0xa0923670
r12: 0x95b0d6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa0929790 r22: 0xa0929784 r23: 0xa092978c
r24: 0x000000e0 r25: 0x1646e6f6 r26: 0xa09294d0 r27: 0x00000040
r28: 0x0000000f r29: 0x224d2752 r30: 0xa0929764 r31: 0x95c8efc4
Thread 2: Crashed (0xb7fff9d0, 0xb80c5e94)
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
0x84060604: No symbol
0x84060670: No symbol
0x84050574: No symbol
0x8408de58: No symbol
0x92126974: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _PrepareClosure + 3816
0x921235a0: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : _PCFragPrepareClosureByName + 336
0x92122d54: /System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/CarbonC ore.framework/Versions/A/CarbonCore : CCFMLaunchApplication + 776
0x0000274c: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : _main + 1256
0x00002230: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : start + 68
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x00000000 lr: 0x84060604 ctr: 0x95bf7504
r00: 0x84060604 r01: 0xbfffec30 r02: 0x01860c00 r03: 0x00000000
r04: 0x00000000 r05: 0x000007d9 r06: 0x00500e30 r07: 0x00000014
r08: 0x000007d9 r09: 0x00000000 r10: 0x0180af50 r11: 0x44424048
r12: 0x95bf7504 r13: 0x00000041 r14: 0xbfffeeb4 r15: 0xbffff2f0
r16: 0xbffff164 r17: 0xa0436dfc r18: 0x9212678c r19: 0xa0432751
r20: 0xbffff154 r21: 0x0000000a r22: 0x00000002 r23: 0x0185ad34
r24: 0x005187a0 r25: 0x00515f50 r26: 0x00518810 r27: 0x00515f50
r28: 0x00000000 r29: 0xa0432724 r30: 0x00515e90 r31: 0x00000000
Thread 3: (0xb019ed74, 0xb815aa83)
0x95c8f0b4: /usr/lib/libSystem.B.dylib : _dispatch_semaphore_waitslow + 248
0x95c8d3a8: /usr/lib/libSystem.B.dylib : _dispatch_workerthread + 116
0x95badda8: /usr/lib/libSystem.B.dylib : _pthreadbody + 40
0x00000000: /System/Library/Frameworks/Carbon.framework/Versions/A/Support/LaunchCFMApp : + 0
PPC Thread State
srr0: 0x00000000 srr1: 0x00000000 vrsave: 0x00000000
cr: 0xXXXXXXXX xer: 0x20000000 lr: 0x95c8f0cc ctr: 0x95b0d6c0
r00: 0xffffffda r01: 0xf0182dc0 r02: 0x00000000 r03: 0x00002403
r04: 0x00000040 r05: 0x35e0f8d9 r06: 0x00000020 r07: 0x00000000
r08: 0x35e0f8d9 r09: 0x00000000 r10: 0x35e0f8d9 r11: 0xa0923670
r12: 0x95b0d6c0 r13: 0x00000000 r14: 0x00000000 r15: 0x00000000
r16: 0x00000000 r17: 0x00000000 r18: 0x00000000 r19: 0x00000000
r20: 0x00000000 r21: 0xa0929790 r22: 0xa0929784 r23: 0xa092978c
r24: 0x000000e0 r25: 0x108b4809 r26: 0xa09294d0 r27: 0x00000040
r28: 0x0000000f r29: 0x1c9378d9 r30: 0xa0929764 r31: 0x95c8efc4
Model: iMac6,1, BootROM IM61.0093.B07, 2 processors, Intel Core 2 Duo, 2.16 GHz, 2 GB, SMC 1.10f3
Graphics: NVIDIA GeForce 7600 GT, NVIDIA GeForce 7600 GT, PCIe, 256 MB
Memory Module: global_name
AirPort: spairportwireless_card_type_airportextreme (0x14E4, 0x87), Broadcom BCM43xx 1.0 (5.10.91.19)
Bluetooth: Version 2.2.1f7, 2 service, 1 devices, 1 incoming serial ports
Network Service: AirPort, AirPort, en1
Serial ATA Device: WDC WD5001AALS-00L3B2, 465.76 GB
Parallel ATA Device: PIONEER DVD-RW DVR-K06
USB Device: Built-in iSight, 0x05ac (Apple Inc.), 0x8501, 0xfd400000
USB Device: Bluetooth USB Host Controller, 0x05ac (Apple Inc.), 0x8206, 0x7d100000
USB Device: IR Receiver, 0x05ac (Apple Inc.), 0x8240, 0x7d200000
USB Device: Kensington PocketMouse Pro, 0x047d (Kensington), 0x101f, 0x5d100000
Any ideas people?

Since the problem is system wide, you can try booting into Safe Mode, which cleans out a buncha cache files, and then reboot normally and see it that works. To reboot in Safe Mode you need to restart and as soon as you hear the chime press and hold the Shift key. The reboot will take longer as the system cleans the caches and runs a disk check procress (it also disables all third party kernel extensions, and some Apple ones as well, so some things may not work--notably a third party mouse or tablet). If that works you may also want to run Font Book and validate your fonts. Photoshop can react very badly to corrupted fonts.
Francine
Francine
Schwieder

Dvd player does not work after Leopard upgrade

I installed Leopard, had to upgrade because my printer died and no printers now work with Tiger. Since the upgrade, my DVD player does not work. I have problems burning some cd's too. Is this a known issue? What is the fix?

I have read a couple of complaints like that, but not sure it's widespread.
At this point I think you should get Applejack...
http://www.macupdate.com/info.php/id/15667/applejack
After installing, reboot holding down CMD+s, (+s), then when the DOS like prompt shows, type in...
applejack AUTO
Then let it do all 6 of it's things.
At least it'll eliminate some questions if it doesn't fix it.
The 6 things it does are...
Correct any Disk problems.
Repair Permissions.
Clear out Cache Files.
Repair/check several plist files.
Dump the VM files for a fresh start.
Trash old Log files.
First reboot will be slower, sometimes 2 or 3 restarts will be required for full benefit... my guess is files relying upon other files relying upon other files! :-)
Disconnect the USB cable from any Uninterruptible Power Supply so the system doesn't shut down in the middle of the process.
If that does NOT help, Safe Boot , (holding Shift key down at bootup), use Disk Utility from there to Repair Permissions, test if things work OK in Safe Mode.
Then move these files to the Desktop...
/Users/YourUserName/Library/Preferences/com.apple.finder.plist
/Users/YourUserName/Library/Preferences/com.apple.systempreferences.plist
/Users/YourUserName/Library/Preferences/com.apple.desktop.plist
/Users/YourUserName/Library/Preferences/com.apple.recentitems.plist
Reboot & test.
PS. Safe boot may stay on the gray radian for a long time, let it go, it's trying to repair the Hard Drive.
If that does NOT help then I suspect the optical drive or media itself, or possibly just needs a cleaning CD run on it.

ISight Camera not working after Leopard install

On my 1st gen Intel 20" iMac, after the Leopard upgrade -- which went very smoothly -- my iSight camera no longer works. I have tried it in Photo Booth and iChat Video and it is the same in each, so it is the camera, apparently, not the application using it.
In the self-viewing screen on my iMac, I see myself for just a second or so, then I fade out quickly and there is nothing to see but black. If I shine a desk lamp in my face, then I can just barely see the outline of my image but the picture is mostly black. It seems like an exposure problem: the camera seems to adjust, shutting down as though I am very brightly lit but since I am not, it produces only a black picture.
I also have a 1st gen Intel white MacBook that I have also upgraded to Leopard. The iSight camera seems to work just fine on that computer. I tried out the video in Photo Booth and it worked great.
Any ideas?

Hi,
I too am having the same problem, and I'm using the old school iSight camera and immediately after installing Leopard, it won't work. I can't even power up the camera. It will power up for about 3 seconds then power down as fast as the little green light came on. It was fine about an hour before the 10.5 install. I powered down and unplugged everything for about 10 mins. then plugged it all back in, and still not working. So I am back to the drawing board trying to sort this out. If anyone has anymore thoughts on this, pls. chime in. All the suggestions seem to work for you folks after a little tweak. I even booted into OF mode and reset-nvram and reset-all for kicks to give it an even fresher start.
thanks!

HP PSC 750 - not working on Leopard 10.5.1

Following some previous advice I saw upon encountering this problem, I deleted and reinstalled the original HP drivers (from the HP website). This fixed it, for a short while. But within days or even hours, the printer stops working again completely:
1) After this time during troubleshooting I notice under System Prefs> Print & Fax that 2 printers have become listed with the same name, PSC 750. One of them is default.
2) Trying either printer does not work. Using generic drivers (included with Leopard) does not work.
3) The printer is connected by USB.
4) When sending a print job, I can click on Info and see supply levels of black and color ink etc., but the print job will just get stuck at "Connecting" or "Printing" and won't actually print.
5) The only way I can get the printer to work again is to delete all printers, choose Applications> HP> Uninstall and then reinstall from the downloaded installer.
Suggestions? I can't figure this out.

I plugged my old PSC 750 into a new MacMini Intel running 10.5.2 today and spent hours to get all functions back to work.
I was not surprised as many problem arose when i upgraded to Tiger allready.
I got EVERYTHING (print and scan) back in operation finally, but it was a bit of a nightmare.
HP claims to have achieve (together with Apple) a print-only integration of all PSC AIO into Leopard, but looking around in google following my troubles, it appears to be a delusion for many.
My solution so far:
You need to press the minus sign twice in the preference panel to delete all printers from the list and download and run the three installers you can find there. First install Foomatic-RIP + gplgs-8.61-ub.dmg and then only hpijs-2.7.10-UB.dmg or it won’t run.
I don’t link them directly as it would fail to follow update, and become dead links in a matter of weeks...
You may then select the proper PSC 750 Foomatic driver within the preference pane.
Works like a charm. I tried Gutenprint 5.1.7 before but no result, printing was just getting stuck on the way.
This HP FAQ section can be useful as well...
I also have troubles scanning with HP scan software from the last (probably ppc) release of HP proprietary drivers and utilities for Tiger, but it DOES scan at least once, then says it has problem to connect to the TWAIN source.
The solution i found in HP FAQ is hilarious. I bumped into this official workaround on their support site, when i had the same trouble after upgrading my PB800 to Tiger.
HP support diagnosis:
Airport and Built-in Ethernet cannot be enabled at the same time.
If you are using Airport to connect to the internet they suggest to go to System Preference-Network and JUST GET RID of the ethernet connection in Network Status!!!
Well that WAS true in Tiger.
And if, like i do, you have a home cable network for old non-airport machines you may as well think about buying a new scanner...
Even after setting Ethernet off, at many occasions the scanner freezes on preview or scan and comes back to work after an USB unplugging and sometimes only after a restart of the PSC or even a reboot of the mac with the printer unplugged (to the worse you might need to unplug the PSC power cable) .
Good luck!

QT 7.3 not working in Leopard

Similar Messages

Maybe you are looking for