Launching Aperture issues

When I launch Aperture, it initializes by showing "opening Aperture library" but after a few seconds it stops and does not open the program.  How do I launch Aperture?  It worked before, not anymore.  I've downloaded latest updates, but still have issues.

Allen,
In response to your request, here's my iMac's information:
Let me know if this helps....
  Model Name:          iMac
  Model Identifier:          iMac11,2
  Processor Name:          Intel Core i3
  Processor Speed:          3.06 GHz
  Number Of Processors:          1
  Total Number Of Cores:          2
  L2 Cache (per core):          256 KB
  L3 Cache:          4 MB
  Memory:          4 GB
  Processor Interconnect Speed:          5.86 GT/s
  Boot ROM Version:          IM112.0057.B00
  SMC Version (system):          1.64f5
Aperture:
  Version:          3.1.2
  Last Modified:          6/4/11 7:02 PM
  Kind:          Intel
  64-Bit (Intel):          Yes
  Get Info String:          Aperture 3.1.2, Copyright 2005-2011 Apple Inc.

Similar Messages

  • Vault status yellow when launching Aperture?

    I have noticed that when I launch Aperture, the Vault status is always yellow. This is even after I have updated the Vault before I quit Aperture. I think it started after I created a MobileMe Gallery. Is there a correlation?
    -Scrags

    Sounds like the vault might be corrupted. As vaults are just snapshots of the current state of the library I would try making a new one and see if that updates. If it does just abandoned the old vault and use the new.
    If the new vault fails also post back.

  • Unable to install (and or) launch Aperture

    I purchased Aperture 1.5 today, installed it and launched for the 1st run. It crashed. I then tried to install update (to 1.5.6). Update could not be installed ... I then removed all of the Aperture files, including the application and re-installed everything. I did not launch Aperture, but tried to update to 1.5.6 first. Update could not be installed this time either. Were did it (all) go wrong ? Looks ridiculous to invest more than 5000 euro in a computer and not being able to run an application labeled as professional ... Who can help ? Any suggestion is welcome.

    I can't launch Aperture after re-installation on my iMac G5 a new MacOS Leopard. It is not possible to update Aperture using automatic update. The system sends me a message that there is no digital signature found in my original Aperture software files (I don't use a copy) and it can not be launched and/or an update can not be installed. What to do???? PERHAPS I WILL GO BACK TO THE PREVIOUS MacOS X Tiger version on my iMac (Aperture worked without any problems). Very similar probvlems I have found also in case of Microsoft Office for Mac 2004 (it works even more funny, sometimes Excell and Word launch and after few minutes disappear from the screen).

  • Insufficient disk space on launching Aperture 3

    In the last couple of days I have been getting an error message on launching Aperture 3.1.3. It is running on a Snow Leopard system, 10.6.8.
    The message reads: "Insufficient disk space.There is not enough free space on your Aperture Library Volume."
    I have 100+ GB free on a 750 GB drive on which that particular library resides. ( I have several libraries due to the large number of raw photos that I have, somewhere north of 60k) It doesn't matter which library I choose, I get the message.
    I am NOT trying to import more files, nor am I trying to upgrade any libraries. I am just trying to launch the app. It does launch after I dismiss the message. What is going on, and how do I get rid of this message. I am having a hard time believing that 100 GB of free space isn't enough for Aperture.

    What I was thinking, and this probably confirms it, is that 100 GB free is not enough to allow the upgrade to a 750 GB Library.
    First check to see if you can successfully click to open one of those that have 3.1.3 as version.
    It did require an upgrade, but I don't rmember it taking very long.  I recently clicked to open some that were 3.1.2, and it took no time at all -- but they were small.
    Ernie

  • I am trying to launch Aperture for the first time and it won't open.  Any tips?

    I am trying to launch Aperture on a MacBook Pro for the first time.  It displays "Opening Aperture Library" with a moving wheel... but nothing happens.  Any thoughts on how to trouble shoot?
    Thanks.

    on a MacBook Pro for the first time.
    What do you mean? Have transferred your Aperture Library from a different machine to a MacBook Pro, or did you just upgrade from a previous version of Aperture?
    If it is hanging on opening your Aperture library, your Aperture library may need repairing.
    Make a backup of your Aperture library.
    Double click the Aperture Library while holding down the option-command key combination ⌥⌘.
    From the First Aid panel that appears, select "Rebuild database" (if you upgraded Aperture), else start with "Repair Permissions" and "Repair Database". See this section in the Aperture manual for how to run the First Aid Tools:
    Repairing and Rebuilding Your Aperture Library
    If none of this helps, post back please and tell us more about your Aperture library, where it is located, the type of images: raw or jpeg, if it referenced, the exact version of Aperture 3 you have.
    Regards
    Léonie

  • Major Aperture Issue - MBPR

    I recently bought a MBPR and bought the newest version of Aperture as i have been using it for years. One day I went to open the software (i think i may have also done an update) and it provided me with this error code -
    Process:         Aperture [1612]
    Path:            /Applications/Aperture.app/Contents/MacOS/Aperture
    Identifier:      com.apple.Aperture
    Version:         3.4.3 (3.4.3)
    Build Info:      Aperture-310022000000000~2
    App Item ID:     408981426
    App External ID: 12009533
    Code Type:       X86-64 (Native)
    Parent Process:  launchd [131]
    User ID:         501
    Date/Time:       2013-02-07 13:11:37.838 -0500
    OS Version:      Mac OS X 10.8.2 (12C3006)
    Report Version:  10
    Interval Since Last Report:          358593 sec
    Crashes Since Last Report:           221
    Per-App Crashes Since Last Report:   1
    Crashed Thread:  0
    Exception Type:  EXC_BREAKPOINT (SIGTRAP)
    Exception Codes: 0x0000000000000002, 0x0000000000000000
    Application Specific Information:
    dyld: launch, loading dependent libraries
    Dyld Error Message:
      Library not loaded: /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager
      Referenced from: /Applications/Aperture.app/Contents/MacOS/Aperture
      Reason: no suitable image found.  Did find:
              /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager: no matching architecture in universal wrapper
              /Library/Frameworks/PluginManager.framework/Versions/B/PluginManager: no matching architecture in universal wrapper
    Binary Images:
           0x10e7ee000 -        0x10ef43fff  com.apple.Aperture (3.4.3 - 3.4.3) <01A802BA-0100-3F80-947C-A8FEA4726352> /Applications/Aperture.app/Contents/MacOS/Aperture
           0x10f162000 -        0x10f16bff7  com.apple.PhotoFoundation (1.0 - 10.17) <C40F985F-9C0A-389A-9E21-684EB0A5B160> /Applications/Aperture.app/Contents/Frameworks/PhotoFoundation.framework/Versio ns/A/PhotoFoundation
           0x10f1e3000 -        0x10f703fff  com.apple.RedRock (1.9.4 - 310.33) <9B94495A-2267-3684-B6E8-9FE3D4B46495> /Applications/Aperture.app/Contents/Frameworks/RedRock.framework/Versions/A/Red Rock
           0x10fa0a000 -        0x10fa8dfff  com.apple.iLifePageLayoutCore (1.0 - 200.9) <8AAC1EB9-5823-3624-A525-635C2A77C34E> /Applications/Aperture.app/Contents/Frameworks/iLifePageLayoutCore.framework/Ve rsions/A/iLifePageLayoutCore
           0x10faeb000 -        0x10faf0fff  com.apple.iLifePhotoStreamConfiguration (3.4 - 2.5) <906317D7-09FF-3B77-8F35-01BB74C0109C> /Applications/Aperture.app/Contents/Frameworks/iLifePhotoStreamConfiguration.fr amework/Versions/A/iLifePhotoStreamConfiguration
           0x10fafc000 -        0x10fb2dff7  com.apple.iLifeAssetManagement (2.7 - 40.34) <E4E1A39C-E8AE-31D5-9C50-B392EBAD7447> /Applications/Aperture.app/Contents/Frameworks/iLifeAssetManagement.framework/V ersions/A/iLifeAssetManagement
           0x10fb5e000 -        0x10fb6bff7  com.apple.iphoto.AccountConfigurationPlugin (1.2 - 1.2) <0F515DED-D77E-3E4F-876D-F5CE596A844C> /Applications/Aperture.app/Contents/Frameworks/AccountConfigurationPlugin.frame work/Versions/A/AccountConfigurationPlugin
           0x10fb7e000 -        0x10fc21ff7  com.apple.MobileMe (13 - 1.0.4) <9A7FCC99-67CE-3F5E-98BB-9079B305087F> /Applications/Aperture.app/Contents/Frameworks/MobileMe.framework/Versions/A/Mo bileMe
        0x7fff6e3ee000 -     0x7fff6e42293f  dyld (210.2.3) <A40597AA-5529-3337-8C09-D8A014EB1578> /usr/lib/dyld
        0x7fff8b40e000 -     0x7fff8b5bcfff  com.apple.QuartzCore (1.8 - 304.0) <BDC66714-F60C-386D-A773-F897D1E87AB6> /System/Library/Frameworks/QuartzCore.framework/Versions/A/QuartzCore
        0x7fff8b804000 -     0x7fff8b813ff7  com.apple.opengl (1.8.6 - 1.8.6) <720CC06C-0D01-37AE-BB3D-D7F0242B262A> /System/Library/Frameworks/OpenGL.framework/Versions/A/OpenGL
        0x7fff8cb38000 -     0x7fff8cb38fff  com.apple.Carbon (154 - 155) <372716D2-6FA1-3611-8501-3DD1D4A6E8C8> /System/Library/Frameworks/Carbon.framework/Versions/A/Carbon
        0x7fff8cde1000 -     0x7fff8cfcafff  com.apple.CoreFoundation (6.8 - 744.12) <EF002794-DAEF-31C6-866C-E3E3AC387A9F> /System/Library/Frameworks/CoreFoundation.framework/Versions/A/CoreFoundation
        0x7fff8d63c000 -     0x7fff8d6d9ff7  com.apple.PDFKit (2.7.2 - 2.7.2) <DE5BE2EF-2570-3792-B1C3-AAD45765F533> /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/PDFKit.framew ork/Versions/A/PDFKit
        0x7fff8e0b8000 -     0x7fff8e0b8fff  com.apple.Cocoa (6.7 - 19) <1F77945C-F37A-3171-B22E-F7AB0FCBB4D4> /System/Library/Frameworks/Cocoa.framework/Versions/A/Cocoa
        0x7fff8e0b9000 -     0x7fff8e127fff  com.apple.framework.IOKit (2.0.1 - 755.20.4) <F2E5AC1B-F03D-3916-B239-7B421579DFA5> /System/Library/Frameworks/IOKit.framework/Versions/A/IOKit
        0x7fff8e155000 -     0x7fff8e3d5ff7  com.apple.AOSKit (1.05 - 151) <A34E8584-797C-318F-9E25-937A710C68AB> /System/Library/PrivateFrameworks/AOSKit.framework/Versions/A/AOSKit
        0x7fff91c81000 -     0x7fff91c81fff  com.apple.ApplicationServices (45 - 45) <A3ABF20B-ED3A-32B5-830E-B37831A45A80> /System/Library/Frameworks/ApplicationServices.framework/Versions/A/Application Services
        0x7fff92001000 -     0x7fff92052ff7  com.apple.SystemConfiguration (1.12.2 - 1.12.2) <E095637C-457F-3D8F-AE32-A032F9D5A46C> /System/Library/Frameworks/SystemConfiguration.framework/Versions/A/SystemConfi guration
        0x7fff938ba000 -     0x7fff93b8afff  com.apple.security (7.0 - 55179.1) <639641EF-8156-3190-890C-1053658E044A> /System/Library/Frameworks/Security.framework/Versions/A/Security
        0x7fff93b8b000 -     0x7fff93b8bfff  com.apple.CoreServices (57 - 57) <9DD44CB0-C644-35C3-8F57-0B41B3EC147D> /System/Library/Frameworks/CoreServices.framework/Versions/A/CoreServices
        0x7fff94294000 -     0x7fff9441efff  com.apple.WebKit (8536 - 8536.26.14) <7C4D5DE6-7153-3E54-8D4F-BB2E9AE74878> /System/Library/Frameworks/WebKit.framework/Versions/A/WebKit
        0x7fff9654b000 -     0x7fff9654bfff  com.apple.Accelerate (1.8 - Accelerate 1.8) <6AD48543-0864-3D40-80CE-01F184F24B45> /System/Library/Frameworks/Accelerate.framework/Versions/A/Accelerate
        0x7fff96658000 -     0x7fff9665efff  com.apple.DiskArbitration (2.5.1 - 2.5.1) <C0EC9C24-F5F4-3378-84DE-EA1073DA760E> /System/Library/Frameworks/DiskArbitration.framework/Versions/A/DiskArbitration
    Model: MacBookPro10,1, BootROM MBP101.00EE.B02, 4 processors, Intel Core i7, 2.6 GHz, 16 GB, SMC 2.3f32
    Graphics: Intel HD Graphics 4000, Intel HD Graphics 4000, Built-In, 512 MB
    Graphics: NVIDIA GeForce GT 650M, NVIDIA GeForce GT 650M, PCIe, 1024 MB
    Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
    Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1600 MHz, 0x80AD, 0x484D5434314753364D465238432D50422020
    AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xEF), Broadcom BCM43xx 1.0 (5.106.98.100.14)
    Bluetooth: Version 4.1.2f9 11046, 2 service, 18 devices, 1 incoming serial ports
    Network Service: Wi-Fi, AirPort, en0
    Serial ATA Device: APPLE SSD SM512E, 500.28 GB
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1a100000 / 2
    USB Device: FaceTime HD Camera (Built-in), apple_vendor_id, 0x8510, 0x1a110000 / 3
    USB Device: hub_device, 0x8087  (Intel Corporation), 0x0024, 0x1d100000 / 2
    USB Device: hub_device, 0x0424  (SMSC), 0x2512, 0x1d180000 / 3
    USB Device: Apple Internal Keyboard / Trackpad, apple_vendor_id, 0x0262, 0x1d182000 / 5
    USB Device: BRCM20702 Hub, 0x0a5c  (Broadcom Corp.), 0x4500, 0x1d181000 / 4
    USB Device: Bluetooth USB Host Controller, apple_vendor_id, 0x8286, 0x1d181300 / 6
    PLEASE NOTE - I have tried deleting the application and re-installing/downloading it from the app store.
    Please help!

    Let me guess: You installed Final Cut Express, or some other very very old version of a pro app?
    Two things I think you need to do:
    1) Remove Final Cut Express.  It's too old and damages things.  You can get the new iMovie or Final Cut Pro X
    2) Download and install the 10.8.2 combo update

  • Aperture Issue with my MAC Mail account

    I inadvertently started to have Aperture email several photos and instead of sending 3 photos I clicked 70 photos (raw about 300mb)
    I cancelled the transfer and MY MAC account keeps spinning and the Draft box shows a clock icon witha incomplete.
    I am guessing that my Mail account is stuck trying to download the photo files even after I cancelled.
    I reset the System Preps sync.
    I checked the Mobile Me internet and there is no problem with the online account.
    There is no email in drafts on in the internet Mobile Me /Mac.com when I log on.
    And I am receiving emails on the internet but not in my computer Mail mail that is spinning.
    I also did a test email from a ATT account and it is on the Internet Mobile Me BUT not on the mail account for my computer.
    All other ATT mailboxes are working fine for incoming and going.
    My Aperture has been running extremely slow since I installed Lion.
    Not sure if that is a separate issue, but I though I would mention it.
    I hope I explained my situation and :
    Any help is appreciated.
    Greg

    *"my problem has to do with mac."*
    What specifically is Mac in this instance? Your mail application? And what email account are you trying to send from?
    If you're using Apple's Mail application, then you should probably post your question in the Mail and Address Book forums:
    http://discussions.apple.com/forum.jspa?forumID=1223

  • ICloud, Mail, Safari, Aperture Issues

    Since upgrading to Mavericks I've had issues with Mail, Safari, and Aperture failing to quit.
    Also, in System Preferences, iCloud fails to load.
    I have re-installed Mavericks, performed a repair permissions, and the only thing that gets me going again (until the next fail) is to force quit the applications and re-start.
    Sure would appreciate some guidance here.
    Thanks, in advance.

    I'll try that next time one of those applications hangs.
    I did find the icloudhelper in Activity Monitor and force quit it, then did a restart.  It was back running after the restart, of course. 
    I'm hoping someone will help here with a permanent fix.
    Thanks for your post.

  • What's the dialog box when you launch Aperture for the first time?

    I bought Aperture 3 from the App Store, installed it, and when I launched it something odd happened: I was interacting with another application, and when Aperture started up it out up the main window and a dialog box popped up that asked "Would you like to..." with (presumably) Yes, No, OK, Cancel, or similar buttons. Unfortunately, it stole my mouse click from the other app and the dialog box vanished before I had a chance to read it, and so I have no idea what the question was or how I answered it. Aperture did not go off and do anything radical like convert my iPhoto library, so I guess it wasn't that, but I would like to know what it was I clicked.
    Unfortunately, I can't repeat it since it appears to be a one-time question. Does anyone know what the dialog box asked? (It's not the second dialog box, which is whether I wanted to enable GPS geotagging.)

    Thanks. On another forum, I have gotten two other answers: (1) whether I wanted to create an Aperture Library; and (2) whether I wanted to register Aperture.
    All three are plausible - I guess it's not crucial what it was, but it would be nice to know.
    (Weirdly, the forum software has lost my profile information and posting history & post count, and it populated the info box with "Model: PowerBook G4", which is about 3 machines back. What's up with that?)

  • Aperture issues.

    Hi
    I've started a new thread as my circumstances are different to most:
    I'm using 10.5.8 on a duo core 3.2 Mac Pro with 4meg of Ram.
    I loaded a trial version of aperture 2 and then deleted as much of it as I could ages ago.
    Downloaded Aperture 3 Trial and what I have seen it is great. However I cannot reference/load much of my library which is currently in a traditional folder system. All I see is some of the images and the message loading assets which spins for ages and then crashes.
    The remainder of the system is also unstable, although much improved after the following:
    Delete and Reload Aperture trial Version.
    Fixed Permissions in Utilities.
    Oynx everything a couple of times
    Several reboots
    deleted Aperture pList in pro-application support folder.
    Created a new Aperture library.
    Any thoughts would be good as this is such a great advance from light-room that I wish to use it ASAP!

    Unless you are absolutely limited to running 10.5.8, I'd start by spending $29 and upgrading to snow leopard. Aperture is faster in it, and you are using a mac pro, so you will notice a substantial performance boost.
    If you are unable to upgrade then there is probably something that could be done quickly to fix your issue. Turn off Faces and auto preview generation in the preferences and see if it still crashes.
    But seriously... As a mac pro owner. You are seriously missing out not running 10.6.

  • Nikon ViewNX 2 and Aperture Issues

    I recently addeded Descriptions/Captions to Nikon RAW files via Nikon View NX2. I originally had these same images in an Aperture library. When I went back to view the images in the Aperture Library they were no longer readable by Aperture. Each image that had benen loaded in to Aperture and was oringalnlly visable now shows up as Unsupported Image Format. Something Nikon has done to the file seems to be keeping Aperture from seeing the NEF's properly. Has anyone else experinced this issue and if so were you able to fix it?

    Hi Jim,
    Sadly you have run into the fact that Nikon software does not treat the NEF as sacrocanct.
    This is not something you would necessarily expect, as every other piece of non-camera manufacturer software PROCESSES the RAW file before it can use it...and they expect to be seeing a fresh out of camera original NEF. Nikon, being the only one that actually knows all the details of the file construction of a NEF, chose to edit the NEF directly.
    Aperture's hallmark is non-destructive editing, meaning it reads the NEF, processes it, and creates "Versions" which are nothing more than a recipe of what was done to the orignal file. If the NEF that Aperture relied upon as a basis for its processed versions is no longer the pure, out of camera Nikon NEF format, then it will no longer recognize them. You may or may not be able to re-import the edited NEFs into Aperture.
    I use the backup function in Aperture when I import, storing the NEFs to two places at once. I do not use View, but I did use Capture NX2 for a bit, and I always did it with copies of the NEFs, never the ones I was managing in Aperture.
    I guess my bigger question is why are you using View, and why didn't you add the captions in Aperture?
    Hope this was helpful,
    KJ Doyle

  • Starcraft II Beta Launcher (Wine) Issue

    Again I seem to be running into problems with this starcraft II beta, although this time it doesn't seem the problem has come up before -- wine doesn't have the answer after a fair amount of searching. I successfully installed it to one of my partitions, and the patches were all applied without a hitch, didn't get the slow firewall problem until the last patch application though, for whatever reason. I have an nVidia GTX 260 with the most current drivers installed. When I put the following command in the terminal it hangs on the bold and then goes through the rest to give me a popup window with a nice errorlog that I will post if someone thinks it is needed. Here is the terminal output.
    $ wine StarCraft\ II.exe
    fixme:wininet:InternetSetOptionW Option INTERNET_OPTION_CONNECT_TIMEOUT (3000): STUB
    fixme:wininet:InternetSetOptionW INTERNET_OPTION_SEND/RECEIVE_TIMEOUT 3000
    [stephen@acid StarCraft II Beta]$ err:module:load_builtin_dll failed to load .so lib for builtin L"winemp3.acm": libmpg123.so.0: cannot open shared object file: No such file or directory
    fixme:process:GetProcessWorkingSetSize (0xffffffff,0x3eaee88,0x3eaee84): stub
    fixme:ntdll:NtQuerySystemInformation info_class SYSTEM_PERFORMANCE_INFORMATION
    [b]fixme:win:EnumDisplayDevicesW ((null),0,0x3eae91c,0x00000000), stub!
    [/b]fixme:win:EnumDisplayDevicesW ((null),0,0x3eae850,0x00000000), stub!
    fixme:d3d:debug_d3dformat Unrecognized 909198916 (as fourcc: DF16) WINED3DFORMAT!
    fixme:d3d:getFormatDescEntry Can't find format unrecognized(909198916) in the format lookup table
    fixme:d3d:debug_d3dformat Unrecognized 909198916 (as fourcc: DF16) WINED3DFORMAT!
    fixme:d3d:getFormatDescEntry Can't find format unrecognized(909198916) in the format lookup table
    fixme:d3d:debug_d3dformat Unrecognized 875710020 (as fourcc: DF24) WINED3DFORMAT!
    fixme:d3d:getFormatDescEntry Can't find format unrecognized(875710020) in the format lookup table
    fixme:d3d:debug_d3dformat Unrecognized 875710020 (as fourcc: DF24) WINED3DFORMAT!
    fixme:d3d:getFormatDescEntry Can't find format unrecognized(875710020) in the format lookup table
    fixme:d3d:debug_d3dformat Unrecognized 1280070990 (as fourcc: NULL) WINED3DFORMAT!
    fixme:d3d:getFormatDescEntry Can't find format unrecognized(1280070990) in the format lookup table
    fixme:d3d:debug_d3dformat Unrecognized 1280070990 (as fourcc: NULL) WINED3DFORMAT!
    fixme:d3d:getFormatDescEntry Can't find format unrecognized(1280070990) in the format lookup table
    fixme:d3d:swapchain_init Add OpenGL context recreation support to context_validate_onscreen_formats
    fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
    fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
    fixme:thread:SetThreadIdealProcessor (0xfffffffe): stub
    err:ole:COMPOBJ_DllList_Add couldn't load in-process dll L"mmdevapi.dll"
    err:ole:create_server class {bcde0395-e52f-467c-8e3d-c4579291692e} not registered
    err:ole:CoGetClassObject no class object {bcde0395-e52f-467c-8e3d-c4579291692e} could be created for context 0x7
    fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x217530,0x217430): stub
    fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x217530,0x217430): stub
    fixme:dsalsa:IDsDriverBufferImpl_SetVolumePan (0x217530,0x217430): stub
    err:module:load_builtin_dll failed to load .so lib for builtin L"WLDAP32.dll": libssl.so.0.9.8: cannot open shared object file: No such file or directory
    err:module:import_dll Loading library WLDAP32.dll (which is needed by L"Z:\\media\\SC2\\StarCraft II Beta\\Support\\Battle.net.dll") failed (error c000007a).
    fixme:process:GetProcessWorkingSetSize (0xffffffff,0x3ead154,0x3ead150): stub
    fixme:process:GetProcessWorkingSetSize (0xffffffff,0x3eacdf4,0x3eacdf0): stub
    fixme:ntdll:NtPowerInformation semi-stub: SystemPowerCapabilities
    fixme:exec:SHELL_execute flags ignored: 0x00000100
    fixme:dxdiag:ProcessCommandLine /t unimplemented
    ^C
    fixme:win:EnumDisplayDevicesW ((null),0,0x3eae91c,0x00000000), stub!  <--- hangs here
    The same thing occurs when I use this command (or use the shortcut):
    $ wine "D:\SC2\Starcraft II Beta\StarCraft II.exe"
    Any ideas? The only other thing to note is before it hangs, my mouse will not show up on the screen where the game should launch.

    lymphatik wrote:
    You should have a look here instead
    http://appdb.winehq.org/objectManager.p … &iId=19376
    Thanks, and good call, but there is not any documentation I can find on a launcher failure, the bolded code above just seems to be associated with screen tearing -- which seems like usually is a driver issue (most of the examples are with WoW).
    Has anyone got the beta working with a GTX 260?

  • Aperture issues with video playback in slideshow

    I'm trying to add a few videos into a slideshow but seem to be hitting an issue with playback. The mpeg4 files play perfectly fine in my project folder but when I drag it into my slideshow I only hear the audio of the video, no picture. Anyone know what I'm doing wrong? I'm running Aperture 3.4.5

    Sorry, that should read .mp4. Have also tried .MOV with no success in the playback of the slideshow.

  • Cannot launch Aperture 3 bought in Apps Store

    Hi guys,
    I launched the Apps Store (10.6.6) and purchased Aperture 3.1.1 there. The download and installation looked normal, but when I press the Aperture 3 icon to launch the program, the icon just bounced-bounced and stopped.
    Any clue to open that program, or to download the Apps again from Apps Store?

    go into your applications folder on your HD, toss Aperture in the trash. To insure other files are not corrupted, you may wish to also throw away preferences and caches here:
    "your home folder"> "Library" > "Application support" > "Aperture" throw this Aperture folder away.
    "your home folder"> "Library" > "Caches" > "Com.Apple.Aperture" Throw the Com.Apple.Aperture file away.
    "your home folder"> "Library" > "Preferences" > "Com.Apple.Preferences.plist" Throw that .plist away
    Now is a good time to repair permissions and perhaps even check the disk / reboot
    Boot up and launch App Store. Click "purchases" on the title bar. Previously it would have said Aperture Installed, once you moved the Aperture application to the trash, it will say "Install". Click that and Aperture will download and re-install.
    Good luck.

  • ITunes won't sync - Aperture issue

    Since upgrading to OSX Lion, iTunes will no longer sync with my iPhone or iPad, I get the following error.  It appears to be something to do with photos which I am syncing from Aperture.  If I switch off photo syncing in iTunes it works.

    Thinl I founfd the solution. Its based on an older known issue:
    The "-50 error" appears to be overcome by doing the following. Essentially you have to delete your current iPhoto or Aperture cache files.
    Follow the instructions in the Apple articles below...it appears to be working for me.....
    iPod/Aperture photo Cache
    ref:
    http://docs.info.apple.com/article.html?artnum=300225
    http://docs.info.apple.com/article.html?artnum=301267
    and several others.
    The trick for people using aperture is that this directory is inside the aperture library file (the .aplibrary file).
    Having removed this directory itunes is now regenerating the optimized photos

Maybe you are looking for