Illustartor CS5 cant open svg after upgrading to Mavericks

Hi,
I upgraded to OSX-10.9 Mavericks. Now, I cant open svg files in illustrator CS5. I could do it before upgrading to Mavericks. Whats the problem?
Thanks,
Ron.

If you do not have a backup then you will lose your photos ad all of yoru files sooner or later - hard drives, computers, software and humans fail and with no backup yu are 100% guarenteed to lose your phoots and files sooner or later - yhou need to purchase an external drive 2 1/2 times the size of your main drive and start using Time Machine all the time ASAP
For this a simple copy will works - but you must always have a backup if you care about anything on your oputer
LN

Similar Messages

Cant open itunes after upgrading to yosemite

Cant open itunes on my macbook pro after upgrading to yosemite. Someone please help if they have faced similar issues.
Thanks.

Try Terence's instructions here Is Iphoto gone ? i want it back!
Pete

Cannot open iPhoto after upgrade to Mavericks

I have a Macbook Pro 15' with Retina Display. I upgraded to Mavericks and afterwards ran the update to iPhoto. Now iPhoto will not launch. I tried using command+option to launch and tried all of those options. Nothing has worked.
iPhoto loads up, then a few seconds later the fan on my macbook revs up to just about max, then it quits with an option to report the crash to Apple.
Anyone have any suggestions?
Thanks in advance.

Thanks. Here you go.
Process:         iPhoto [1004]
Path:            /Applications/iPhoto.app/Contents/MacOS/iPhoto
Identifier:      com.apple.iPhoto
Version:         9.5 (902.7)
Build Info:      iPhotoProject-902007000000000~2
App Item ID:     408981381
App External ID: 15933459
Code Type:       X86-64 (Native)
Parent Process: launchd [152]
Responsible:     iPhoto [1004]
User ID:         501
Date/Time:       2013-10-25 11:26:46.159 -0400
OS Version:      Mac OS X 10.9 (13A603)
Report Version: 11
Anonymous UUID: 0441129D-9939-60BA-F69E-85E59886CC03
Sleep/Wake UUID: 188C2232-4EB5-44AA-AF28-A872BD2289D2
Crashed Thread: 0 Dispatch queue: com.apple.main-thread
Exception Type: EXC_BAD_ACCESS (SIGSEGV)
Exception Codes: KERN_PROTECTION_FAILURE at 0x00007fff5d642fd8
VM Regions Near 0x7fff5d642fd8:
    MALLOC_SMALL           00007fd2d0000000-00007fd2d1000000 [ 16.0M] rw-/rwx SM=PRV
--> STACK GUARD            00007fff59e43000-00007fff5d643000 [ 56.0M] ---/rwx SM=NUL stack guard for thread 0
    Stack                  00007fff5d643000-00007fff5de43000 [ 8192K] rw-/rwx SM=COW thread 0
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0   com.apple.CoreFoundation                0x00007fff8c1cd097 CFBasicHashFindBucket + 327
1   com.apple.CoreFoundation                0x00007fff8c1d3dce uniquedName + 190
2   com.apple.CoreFoundation                0x00007fff8c1d3603 _CFXNotificationPost + 1267
3   com.apple.Foundation                    0x00007fff856a24aa -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
4   com.apple.iLifeAssetManagement          0x0000000102c3d6c9 -[AssetManagementClient switchToCurrentLibrary] + 246
5   com.apple.iLifeAssetManagement          0x0000000102c3d3de -[AssetManagementClient libraryMatch] + 131
6   com.apple.iPhoto                        0x0000000101e107e8 0x101dbd000 + 341992
7   com.apple.iPhoto                        0x0000000101e10767 0x101dbd000 + 341863
8   com.apple.iPhoto                        0x00000001022ecd9e 0x101dbd000 + 5438878
9   com.apple.CoreFoundation                0x00007fff8c2dffcc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
10 com.apple.CoreFoundation                0x00007fff8c1d3c5d _CFXNotificationPost + 2893
11 com.apple.Foundation                    0x00007fff856a24aa -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
12 com.apple.iLifeAssetManagement          0x0000000102c3d6c9 -[AssetManagementClient switchToCurrentLibrary] + 246
13 com.apple.iLifeAssetManagement          0x0000000102c3d3de -[AssetManagementClient libraryMatch] + 131
14 com.apple.iPhoto                        0x0000000101e107e8 0x101dbd000 + 341992
15 com.apple.iPhoto                        0x0000000101e10767 0x101dbd000 + 341863
16 com.apple.iPhoto                        0x00000001022ecd9e 0x101dbd000 + 5438878
17 com.apple.CoreFoundation                0x00007fff8c2dffcc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
18 com.apple.CoreFoundation                0x00007fff8c1d3c5d _CFXNotificationPost + 2893
19 com.apple.Foundation                    0x00007fff856a24aa -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
20 com.apple.iLifeAssetManagement          0x0000000102c3d6c9 -[AssetManagementClient switchToCurrentLibrary] + 246
21 com.apple.iLifeAssetManagement          0x0000000102c3d3de -[AssetManagementClient libraryMatch] + 131
22 com.apple.iPhoto                        0x0000000101e107e8 0x101dbd000 + 341992
23 com.apple.iPhoto                        0x0000000101e10767 0x101dbd000 + 341863
24 com.apple.iPhoto                        0x00000001022ecd9e 0x101dbd000 + 5438878
25 com.apple.CoreFoundation                0x00007fff8c2dffcc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
26 com.apple.CoreFoundation                0x00007fff8c1d3c5d _CFXNotificationPost + 2893
27 com.apple.Foundation                    0x00007fff856a24aa -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
28 com.apple.iLifeAssetManagement          0x0000000102c3d6c9 -[AssetManagementClient switchToCurrentLibrary] + 246
29 com.apple.iLifeAssetManagement          0x0000000102c3d3de -[AssetManagementClient libraryMatch] + 131
30 com.apple.iPhoto                        0x0000000101e107e8 0x101dbd000 + 341992
31 com.apple.iPhoto                        0x0000000101e10767 0x101dbd000 + 341863
32 com.apple.iPhoto                        0x00000001022ecd9e 0x101dbd000 + 5438878
33 com.apple.CoreFoundation                0x00007fff8c2dffcc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
34 com.apple.CoreFoundation                0x00007fff8c1d3c5d _CFXNotificationPost + 2893
35 com.apple.Foundation                    0x00007fff856a24aa -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
36 com.apple.iLifeAssetManagement          0x0000000102c3d6c9 -[AssetManagementClient switchToCurrentLibrary] + 246
37 com.apple.iLifeAssetManagement          0x0000000102c3d3de -[AssetManagementClient libraryMatch] + 131
38 com.apple.iPhoto                        0x0000000101e107e8 0x101dbd000 + 341992
39 com.apple.iPhoto                        0x0000000101e10767 0x101dbd000 + 341863
40 com.apple.iPhoto                        0x00000001022ecd9e 0x101dbd000 + 5438878
41 com.apple.CoreFoundation                0x00007fff8c2dffcc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
42 com.apple.CoreFoundation                0x00007fff8c1d3c5d _CFXNotificationPost + 2893
43 com.apple.Foundation                    0x00007fff856a24aa -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
44 com.apple.iLifeAssetManagement          0x0000000102c3d6c9 -[AssetManagementClient switchToCurrentLibrary] + 246
45 com.apple.iLifeAssetManagement          0x0000000102c3d3de -[AssetManagementClient libraryMatch] + 131
46 com.apple.iPhoto                        0x0000000101e107e8 0x101dbd000 + 341992
47 com.apple.iPhoto                        0x0000000101e10767 0x101dbd000 + 341863
48 com.apple.iPhoto                        0x00000001022ecd9e 0x101dbd000 + 5438878
49 com.apple.CoreFoundation                0x00007fff8c2dffcc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
50 com.apple.CoreFoundation                0x00007fff8c1d3c5d _CFXNotificationPost + 2893
51 com.apple.Foundation                    0x00007fff856a24aa -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
52 com.apple.iLifeAssetManagement          0x0000000102c3d6c9 -[AssetManagementClient switchToCurrentLibrary] + 246
53 com.apple.iLifeAssetManagement          0x0000000102c3d3de -[AssetManagementClient libraryMatch] + 131
54 com.apple.iPhoto                        0x0000000101e107e8 0x101dbd000 + 341992
55 com.apple.iPhoto                        0x0000000101e10767 0x101dbd000 + 341863
56 com.apple.iPhoto                        0x00000001022ecd9e 0x101dbd000 + 5438878
57 com.apple.CoreFoundation                0x00007fff8c2dffcc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
58 com.apple.CoreFoundation                0x00007fff8c1d3c5d _CFXNotificationPost + 2893
59 com.apple.Foundation                    0x00007fff856a24aa -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
60 com.apple.iLifeAssetManagement          0x0000000102c3d6c9 -[AssetManagementClient switchToCurrentLibrary] + 246
61 com.apple.iLifeAssetManagement          0x0000000102c3d3de -[AssetManagementClient libraryMatch] + 131
62 com.apple.iPhoto                        0x0000000101e107e8 0x101dbd000 + 341992
63 com.apple.iPhoto                        0x0000000101e10767 0x101dbd000 + 341863
64 com.apple.iPhoto                        0x00000001022ecd9e 0x101dbd000 + 5438878
65 com.apple.CoreFoundation                0x00007fff8c2dffcc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
66 com.apple.CoreFoundation                0x00007fff8c1d3c5d _CFXNotificationPost + 2893
67 com.apple.Foundation                    0x00007fff856a24aa -[NSNotificationCenter postNotificationName:object:userInfo:] + 68
68 com.apple.iLifeAssetManagement          0x0000000102c3d6c9 -[AssetManagementClient switchToCurrentLibrary] + 246
69 com.apple.iLifeAssetManagement          0x0000000102c3d3de -[AssetManagementClient libraryMatch] + 131
70 com.apple.iPhoto                        0x0000000101e107e8 0x101dbd000 + 341992
71 com.apple.iPhoto                        0x0000000101e10767 0x101dbd000 + 341863
72 com.apple.iPhoto                        0x00000001022ecd9e 0x101dbd000 + 5438878
73 com.apple.CoreFoundation                0x00007fff8c2dffcc __CFNOTIFICATIONCENTER_IS_CALLING_OUT_TO_AN_OBSERVER__ + 12
74 com.apple.CoreFoundation                0x00007fff8c1d3c5d _CFXNotificationPost + 2893
75 com.apple.Foundation                    0x00007fff856a24aa -[NSNotificationCenter postNotificationName:object:userInfo:] + 68

Cant open ITunes after Upgrade

Must have upgraded my ITunes recently because ITunes will no longer open unless I download the new Quicktime 7.6. My company computer is running MAC OS 10 with no option for Leopard. APPLE! You idiots! If your upgrade is going to render a customers ITunes unnusable without a system upgrade you need to put a warning in the upgrade message so customers can choose not to run the upgrade!!!! Not everyone can run out and get the newest hardware and software.!!!! Now I cannot open my ITunes and can't go back to the old. Not to mention that my $260 ipod started to skip before it was even a year old and according the the discussion boards there was nothing to do to fix it. Get your stuff together Apple!!!!
This happened on my fathers ITunes operating on ad older Windows. He now cannot use his Ipod, because he cannot get an Itunes that will run on his computer!!! He can't upgrade without buying a new computer!!! And at 85 why should he buy a new one!!! Come on Apple!!!!

First, Apple product developers do not participate here, so rants posted here will do little good since the rant probably will be seen only by we your fellow users.
Second, why can you not upgrade to QuickTime 7.6? If it's just a matter of you not being able to find an appropriate version for your version of Mac OS X, just run Software Update on your computer, or look here:
http://support.apple.com/downloads/#quicktime
QuickTime 7.6 is available for Mac OS X versions back to and including 10.4.11, which is also the earliest version that the current iTunes release will run on. So there shouldn't be any problem, at least not as far as an available compatible version is concerned.
This happened on my fathers ITunes operating on ad older Windows. He now cannot use his Ipod, because he cannot get an Itunes that will run on his computer!
What version of Windows does he have? Did he have his iPod working before, or is this a new iPod? If so, the system requirements for the iPod are clearly stated, on Apple's web site and, I believe, on the iPod's box. If his system doesn't match the system requirements of the iPod, that's not Apple's fault.
Regards.
Message was edited by: Dave Sawyer

Cant open documents after upgrade

I recently updated the "Pages" app on my iMac. I have created two documents since then and saved them. When I go to Pages, these documents are "greyed" out. They are there, I can see them, but they can't be selected to open. How do I open these and why did this happen. Looking through some of my other documents, I have noticed alot of them are grey as well and can't be opened. Especially PDF files. What is going on? I REALLY need those documents. 5 hours worth of work are saved in that unopenable space!

If you recently "updated" Pages, you probably upgraded to Pages 5 and have Pages '09 moved to your Applications/iWork folder.
Pages '09 can not open anything created by Pages 5 unless you exported the files to Pages '09 or Word .docx formats.
Mavericks also "locks" older unused files.
Are you sure that this is not what is happening.
Or did you delete all the necessary apps when you migrated?
Thirdly do you have them stored somewhere else that the Mac can't locate and those are just aliases?
Peter

Can't open iPhoto after upgraded to mavericks

After I updated to 10.9, the fan of my Macbook Pro keep spinning at high speed.
Secondly, I cannot open iPhoto which said I need to update the iPhoto to the latest version.
However, the app store does not have the update when I clicked the update button…
Now , I cannot use iPhoto… even I re-install it from CD...

it was the most up-to-date iphoto 11 before I up to 10.9..
It woundnt open
so I uninstalled it and re install it from iphoto 11 CD then it direct me to update to the latest version which does not exist in app store..

Cant open doc files from the server on MacBook Air after upgrading to Maverick

Cant open doc files from the server on MacBook Air after upgrading to Maverick, I can only open up docx file. Thank you!

Thanks for the suggestion! I don't use Phantasm or VectorScribe (or any Astute Graphics plugins for that matter). I do, however, have a Wacom tablet and have a few plugins that concern using Blurb Book Creator as well as LiveSurface Context.
I did the very unfortunate and foolish act of upgrading to Maverick without a backup, so postponing isn't an option for me.
I geuss my question at this point would be, would it be worthwhile to wipe all the adobe products from my harddrive and re-install them? Or would that be a useless endeavor.
I don't have an external hard-drive so backing up and re-installing the entire OS would be a bit much. Any suggestions?

After upgrade to mavericks: time machine keeps asking for my back up disk and won't open unless i plug in the disk. any solutions?

after upgrade to mavericks: time machine keeps asking for my back up disk and won't open unless i plug in the disk. any solutions?
before the upgrade, i could open time machine without the need for having the back up disk plugged in.

Ok. I got it to work, sort of....
As I mentioned before I tried the "disk password" and the "Time capsule Password" options to see if I can start the back up again or start a new backup. Neither worked. So I tried the firmware down grade, but like you said that did not work. I then decided to try the "Account password" option and I have never used this option before becasue it states that if there is data on the drive it would not be acessable after creating an account. Since I wiped out the disk that was nno problem. When I created the new account and choose the drive it asked for the user name and password. I entered the info for the new account I just created(FYI this has nothing to do with your login username and password), bingo! It worked!
Now I have two partitions on the TC disk. The old one and now the new account. I am guessing this is to be used if I have multiple computers, which I don't.
I any case, I am going to wipe out everything again and try again to do a backup the way I had it before.

Pages on my iPad3 has become very slow to open documents after upgrading to ios7. I've clicked on a folder 5 minutes ago and am still waiting. The work-around seems to be to force-close it, but I've needed to do this many times in the last few days.

Pages on my iPad3 has become very slow to open documents after upgrading to ios7.
I posted on here about this a few weeks back and someone suggested force-closing Pages -- and that does indeed enable me to open things -- but I have had to force-close many times in the last 24 hours, which is worrying. Are there any other suggestions?
I am sometimes also finding that, when I have been writing something and then click on "documents" the screen goes blank, there is a wait of around a minute and then the same document is re-displayed, before clicking "documents" again lets me look at other documents -- which is a pain if I am trying to move between documents repeatedly. Again, words of wisdom on this would be great.
Pages under iOS6 opened quickly, and there was an immediate loss of performance when I upgraded. I am finding this very frustrating because I don't feel that the new Pages has added to the facilities I was using, but a slowness to open documents is frustrating.
Thanks
Mark

Pages on my iPad3 has become very slow to open documents after upgrading to ios7.
I posted on here about this a few weeks back and someone suggested force-closing Pages -- and that does indeed enable me to open things -- but I have had to force-close many times in the last 24 hours, which is worrying. Are there any other suggestions?
I am sometimes also finding that, when I have been writing something and then click on "documents" the screen goes blank, there is a wait of around a minute and then the same document is re-displayed, before clicking "documents" again lets me look at other documents -- which is a pain if I am trying to move between documents repeatedly. Again, words of wisdom on this would be great.
Pages under iOS6 opened quickly, and there was an immediate loss of performance when I upgraded. I am finding this very frustrating because I don't feel that the new Pages has added to the facilities I was using, but a slowness to open documents is frustrating.
Thanks
Mark

Can´t open LR after upgrade to 5.3 without entering a licens key

Can´t open LR after upgrade to 5.3 without entering a licens key

I have seen comments from someone who indicated that every time they started Lightroom they were prompted for the serial number, even though they had already entered it. Is this your situation? I can't remember what the solution is, but I have seen that problem mentioned in the past.

Can't open Pages after upgrading to snow leopard on 10.6.8

Can't open Pages after upgrading to snow leopard on 10.6.8

Has Spotlight finished its indexing? Check in the upper right. If you get just the search field, it has, if it says its indexing, you have to wait before you can use anything.

After upgrading to mavericks, i cannot open mac app store, preview, calendar, etc

Why i cannot open mac app store, preview, calendar, software update, etc after upgrading to mavericks? How can i fix this? please help me

Please read this whole message before doing anything.
This procedure is a diagnostic test. It’s unlikely to solve your problem. Don’t be disappointed when you find that nothing has changed after you complete it.
The purpose of the test is to determine whether the problem is caused by third-party software that loads automatically at startup or login, by a peripheral device, or by corruption of certain system caches.
Disconnect all wired peripherals except those needed for the test, and remove all aftermarket expansion cards. Boot in safe mode and log in to the account with the problem. Note: If FileVault is enabled on some models, or if a firmware password is set, or if the boot volume is a software RAID, you can’t do this. Ask for further instructions.
Safe mode is much slower to boot and run than normal, and some things won’t work at all, including sound output and Wi-Fi on certain models. The next normal boot may also be somewhat slow.
The login screen appears even if you usually log in automatically. You must know your login password in order to log in. If you’ve forgotten the password, you will need to reset it before you begin. Test while in safe mode. Same problem? After testing, reboot as usual (i.e., not in safe mode) and verify that you still have the problem. Post the results of the test.

After upgrading to Mavericks my Mac Pro does not open my double CD drives when I hit eject in the menu bar it locks up (please Help)?

After upgrading to Mavericks my Mac Pro does not open my double CD drives when I hit eject in the menu bar it locks up (please Help)?

If you have more than one user account, these instructions must be carried out as an administrator.
Launch the Console application in any of the following ways:
☞ Enter the first few letters of its name into a Spotlight search. Select it in the results (it should be at the top.)
☞ In the Finder, select Go ▹ Utilities from the menu bar, or press the key combination shift-command-U. The application is in the folder that opens.
☞ Open LaunchPad. Click Utilities, then Console in the icon grid.
Step 1
Make sure the title of the Console window is All Messages. If it isn't, select All Messages from the SYSTEM LOG QUERIES menu on the left. If you don't see that menu, select
View ▹ Show Log List
from the menu bar.
Enter "BOOT_TIME" (without the quotes) in the search box. Note the timestamps of those log messages, which refer to the times when the system was booted. Now clear the search box and scroll back in the log to the last boot time after you had the problem. Select the messages logged before the boot, while the system was unresponsive or was failing to shut down. Copy them to the Clipboard by pressing the key combination command-C. Paste into a reply to this message (command-V). Please include the BOOT_TIME message at the end of the log extract.
If there are runs of repeated messages, post only one example of each. Don’t post many repetitions of the same message.
When posting a log extract, be selective. In most cases, a few dozen lines are more than enough.
Please do not indiscriminately dump thousands of lines from the log into this discussion.
Important: Some private information, such as your name, may appear in the log. Anonymize before posting.
Step 2
Still in Console, look under System Diagnostic Reports for crash or panic logs, and post the entire contents of the most recent one, if any. In the interest of privacy, I suggest you edit out the “Anonymous UUID,” a long string of letters, numbers, and dashes in the header of the report, if present (it may not be.) Please don’t post any other kind of report — it will be very long and not helpful.

A FCP user gave me .mov's that PP CS5 cant open, what can I do? (File link enclosed)

A FCP shooter gave me .mov's that PP CS5 cant open, what can I do? I guess she rewrapped the files because as they try to import into cs5 a FCP loading diologe box opens stating: Importing FCP XML.... Afterwards it says i dont have the codec necc.
I'm PC based only.
Here is a link to a short clip that can be downloaded.
I'm really stuck here guys. Cant reach the shooter.
The 5 second clip can be seen & downloaded from Vimeo:
http://vimeo.com/27230969

If you tried XD Decode you must think that they originated as XDCam then, right? That is the codec I had to buy and once it was installed everything was transparent and normal. So I'm not sure what the crashing is all about, assuming your system meets the minimal tech. requirements. I'd give it another try if you haven't already.
Your best hope would be to locate the original camera files, which could very well have been deleted following the .mov copying via the Mac. I've had no problem with native XDCam in Premiere. The next best solution might be to have that FCP user do the conversions to another file format you can use. Hopefully there aren't thousands of them.
Firstodd, that's very interesting that your Avid MC was able to work with those files. I just found this from an Avid doc of last year: "If you want to play the exported movie in QuickTime, you need to purchase a third-party QuickTime plug-in. Avid recommends the Calibrated{Q} XD Decode from Calibrated Software"
Still, for the $80 I spent a year ago, XD Decode was well worth it in time saved. I see the price has gone up $50 since then though.

Iphoto won't open after upgrade to Mavericks

After upgrading to Mavericks a few wks ago I am having an issue with iphoto. It did an auto update after upgrading to Mavericks, but now it has a circle with a line through it (blocked). The pop up window says cannot open iphoto because it may be damaged or incomplete.

Delete it and download from the App Store.

Illustartor CS5 cant open svg after upgrading to Mavericks

Similar Messages

Maybe you are looking for