Aperture Black screen after edits...

After upgrading to Aperture 2.1 I have a strange thing:
After editing a picture the Screen turns completely black. The histogram displays only one spike.
Resizing the window brings back the Image, but the histogram remains only one spike.
Thanks for help
wok

It's a pretty common problem (do a search and you'll see some more topics regarding this). It happened again to me today for the first time in months. Except this time it wasn't the whole viewer but 3/4 of the viewer went black. Only things that were different today: I pressed i to remove the project pane, I straightened then cropped, I adjusted contrast. I rarely straighten and I rarely work without the project pane open. Also I was working while my MBP was not plugged in, and it was quite warm. Still can't really narrow down when it's going to happen.

Similar Messages

[SOLVED] Black screen after GRUB

Hello everyone
I was setting up a machine with E17 and was trying various DM's since none seemed to work. After attempting to use LightDM, I get a black screen after GRUB. I was trying to read the various logs at /var/log/ but I cannot understand them properly. I tried reinstalling entrance and LightDM with no luck. I even tried editing grub's entry appending '1' or 's' and still no dice. Any help would be appreciated.
Last edited by Linoman (2014-01-20 09:22:33)

Hi tnx for both answers.
I missed something important in Xorg.log. As you can see, fbdev and modesetting aren't loading as usual. I didn't check grub stuff, I don't think it's related, since loading in level 3 (text mode) I get a black screen but I can login as root and turn off the computer blindlessly.
[ 2.969] (II) LoadModule: "modesetting"
[ 2.969] (WW) Warning, couldn't open module modesetting
[ 2.969] (II) UnloadModule: "modesetting"
[ 2.969] (II) Unloading modesetting
[ 2.970] (EE) Failed to load module "modesetting" (module does not exist, 0)
[ 2.970] (II) LoadModule: "fbdev"
[ 2.970] (WW) Warning, couldn't open module fbdev
[ 2.970] (II) UnloadModule: "fbdev"
[ 2.970] (II) Unloading fbdev
[ 2.970] (EE) Failed to load module "fbdev" (module does not exist, 0)
[ 2.970] (II) intel: Driver for Intel(R) Integrated Graphics Chipsets:
i810, i810-dc100, i810e, i815, i830M, 845G, 854, 852GM/855GM, 865G,
915G, E7221 (i915), 915GM, 945G, 945GM, 945GME, Pineview GM,
Pineview G, 965G, G35, 965Q, 946GZ, 965GM, 965GME/GLE, G33, Q35, Q33,
GM45, 4 Series, G45/G43, Q45/Q43, G41, B43, HD Graphics,
HD Graphics 2000, HD Graphics 3000, HD Graphics 2500,
HD Graphics 4000, HD Graphics P4000, HD Graphics 4600,
HD Graphics 5000, HD Graphics P4600/P4700, Iris(TM) Graphics 5100,
HD Graphics 4400, HD Graphics 4200, Iris(TM) Pro Graphics 5200
[ 2.970] (II) VESA: driver for VESA chipsets: vesa
[ 2.970] (++) using VT number 7
[ 2.974] (WW) Falling back to old probe method for vesa
javex wrote:Post the content of the following files:
Also does disabling LightDM again help resolve the issue, i.e. can you get it to work without LightDM?
No, I can't get it to work changing DM's. I'm not sure if I pacman -Syu before changing DM's another time. Maybe it wasn't LightDM's fault afterall.
Spider.007 wrote:Additionally; try booting without the 'quiet' entry that is in the kernel line by default; and disable https://wiki.archlinux.org/index.php/Ke … de_Setting too
Thanks for pointing out that. I didn't knew I had it on.
Last edited by Linoman (2014-01-11 21:34:08)

[Solved]Black screen after "waiting for udev uevents to be processed"

Hello friends,
Starting from late Dec., my laptop goes black screen after "waiting for udev uevents to be processed", after updating kernel to 2.26.32.*. The strange thing is that even the screen is black, the keyboard is working. For example, I can turn on/off the status lights of capslock and others. I guess something might be wrong with udev uevents configuration with regard to the latest kernel. I've noticed that in the new kernel, there are two drivers for intel integrated graphics. My laptop has a 855G, which is supposed to be functional by both drivers, at least according to the kernel description. Maybe because the udev is configured to use the second driver (for newer graphic chips), rather than the first driver, which caused the problem?
Regards,
Wen
Last edited by Wen (2010-01-28 13:14:28)

Have a look here: http://bbs.archlinux.org/viewtopic.php? … 70#p695670

[Solved] Amilo XI 2550 - Black screen after fresh install

Dear archlinux users,
I have been reading the archlinux wiki and forums since I started using arch several years ago. It was always possible to solve the problems I ran into by consulting these webpages, therefore a big thanks to the community for the provided help.
Two weeks ago I installed arch on a Fujitsu Siemens Amilo XI 2550. The first problem I ran into was that booting the live-cd resulted in a black screen and I could not even start with installing arch. This problem was solved with the kernel parameter 'nomodeset'.
The first boot of the freshly installed arch also resulted in a black screen after the GRUB menu which was perfectly displayed. After some searching (here and here and ...) I plugged in an external monitor and it showed the login screen. I then installed KDE because I thaught the problem might not show up with X and KDE running. After the login to KDE I realized that the brightness of the laptop display is nearly black but not totally. It seems as if the brightness is at a very low level, but brightness cannot be controlled with the Fn+F8 or Fn+F9 commands. But I see a OSD that indicates that the controls are used but without effect. So at the moment it is only possible to work on the laptop with another display connected to it.
Maybe of use:
ls /sys/class/backlight/
acpi_video0
radeon_bl0
less /sys/class/backlight/acpi_video0/bl_power
0
less /sys/class/backlight/acpi_video0/actual_brightness
7
less /sys/class/backlight/acpi_video0/brightness
7
less /sys/class/backlight/acpi_video0/max_brightness
7
less /sys/class/backlight/radeon_bl0/bl_power
0
less /sys/class/backlight/radeon_bl0/actual_brightness
255
less /sys/class/backlight/radeon_bl0/brightness
255
less /sys/class/backlight/radeon_bl0/max_brightness
255
dmesg | grep drm
[ 0.736559] [drm] Initialized drm 1.1.0 20060810
[ 0.743608] [drm] radeon kernel modesetting enabled.
[ 0.743678] fb: switching to radeondrmfb from VESA VGA
[ 0.744054] [drm] initializing kernel modesetting (RV630 0x1002:0x9583 0x1734:0x1107).
[ 0.744065] [drm] register mmio base: 0xCFEF0000
[ 0.744067] [drm] register mmio size: 65536
[ 0.744172] [drm] Detected VRAM RAM=256M, BAR=256M
[ 0.744174] [drm] RAM width 128bits DDR
[ 0.744257] [drm] radeon: 256M of VRAM memory ready
[ 0.744259] [drm] radeon: 512M of GTT memory ready.
[ 0.744275] [drm] Loading RV630 Microcode
[ 0.744345] [drm] Internal thermal controller without fan control
[ 0.744386] [drm] radeon: power management initialized
[ 0.744389] [drm] GART: num cpu pages 131072, num gpu pages 131072
[ 0.762830] [drm] PCIE GART of 512M enabled (table at 0x0000000000040000).
[ 0.762873] [drm] Supports vblank timestamp caching Rev 2 (21.10.2013).
[ 0.762874] [drm] Driver supports precise vblank timestamp query.
[ 0.762937] [drm] radeon: irq initialized.
[ 0.794780] [drm] ring test on 0 succeeded in 1 usecs
[ 0.795253] [drm] ib test on ring 0 succeeded in 0 usecs
[ 0.795942] [drm] radeon atom DIG backlight initialized
[ 0.795945] [drm] Radeon Display Connectors
[ 0.795947] [drm] Connector 0:
[ 0.795948] [drm] LVDS-1
[ 0.795950] [drm] DDC: 0xac0 0xac0 0xac4 0xac4 0xac8 0xac8 0xacc 0xacc
[ 0.795951] [drm] Encoders:
[ 0.795952] [drm] LCD1: INTERNAL_LVTM1
[ 0.795953] [drm] Connector 1:
[ 0.795954] [drm] DIN-1
[ 0.795955] [drm] Encoders:
[ 0.795956] [drm] TV1: INTERNAL_KLDSCP_DAC2
[ 0.795957] [drm] Connector 2:
[ 0.795958] [drm] HDMI-A-1
[ 0.795960] [drm] HPD1
[ 0.795961] [drm] DDC: 0x7e50 0x7e50 0x7e54 0x7e54 0x7e58 0x7e58 0x7e5c 0x7e5c
[ 0.795963] [drm] Encoders:
[ 0.795964] [drm] DFP1: INTERNAL_KLDSCP_TMDS1
[ 0.795965] [drm] Connector 3:
[ 0.795966] [drm] VGA-1
[ 0.795968] [drm] DDC: 0x7e40 0x7e40 0x7e44 0x7e44 0x7e48 0x7e48 0x7e4c 0x7e4c
[ 0.795969] [drm] Encoders:
[ 0.795970] [drm] CRT1: INTERNAL_KLDSCP_DAC1
[ 1.278449] [drm] fb mappable at 0xD0141000
[ 1.278451] [drm] vram apper at 0xD0000000
[ 1.278453] [drm] size 9216000
[ 1.278454] [drm] fb depth is 24
[ 1.278455] [drm] pitch is 7680
[ 1.278527] fbcon: radeondrmfb (fb0) is primary device
[ 1.726069] radeon 0000:01:00.0: fb0: radeondrmfb frame buffer device
[ 1.770030] [drm] Initialized radeon 2.39.0 20080528 for 0000:01:00.0 on minor 0
Until now and amongst others I tried the following things.
Using kernel parameters
video.use_native_backlight=1
video.use_native_backlight=0
acpi_osi=linux
acpi_backlight=vendor
and others I just cannot remember.
Masking backlight
systemctl mask systemd-backlight@backlight:acpi_video0.service
systemctl mask systemd-backlight@backlight:radeon_bl0.service
Setting bl_power
echo 1 > /sys/class/backlight/acpi_video0/bl_power
echo 1 > /sys/class/backlight/radeon_bl0/bl_power
Nothing of the above was improving the situation.
Your help on the problem would be highly appreciated.
Best regards
mgs
Last edited by mgs (2014-10-27 10:15:11)

Hello Trilby,
thanks for the reply.
Trilby wrote:If nomodeset worked with the installation medium, why haven't you tried that for the same problem on your installed system?
The kernel parameter 'nomodeset' results in a working display but without X support, due to the fact that with 'nomodeset' there is no KMS support and therefore no X. But nevertheless I tried it and as expected X did not start.
Trilby wrote:Could you also post information about your graphics card and what drivers you've installed.
The graphics card is a Radeon HD 2700 and according to the above dmesg log it is recognized as RV 630. The radeon module is loaded via /etc/mkinitcpio.conf and xf86-video-ati (1:7.5.0-1) is installed.
I hope the provided information is what you asked for, thanks for your help.
Best regards
mgs

MSI R9 270X - Black Screen after Win7 logo

Hello there.
About a week ago I upgraded my PC, buying several components and putting it to work. Here's the specs.
Main Board: M5A97 EVO R2.0
Bios Version: Latest
Video Card: MSI Radeon R9 270X TwinFrozr OC Edition 2Gb
PSU: Don't know
12v rail Rating of listed PSU:
CPU: AMD FX 8350 4.0Ggz BE SkAM3+
Memory: 8Gb Crucial Ballistix DDR3-1600Mhz
SSD/ HDD: Western Digital WD10EZRX-00A8LB0 1TB
CPU COOLER: The one that came with the CPU
Raid Card: Onboard
Sound Card: Onboard
OC: (Yes / No) Don't know
Operating System: Win 7 SP 1 64
So, it worked just fine for about 3 days. Last Saturday night I tried to open Google Chrome after some gaming and the the system froze. I got a screen with vertical black and white stripes. I had to reboot the system and it gave me a black screen, crashing again, after the Win Logo at start up. At this time I was running either 14.7 or 14.9 ATI drivers.
I could only start the PC on Safe Mode. Removing the drivers and getting Windows general VGA card settings would allow me to use Windows in normal mode though. Once I installed the Graphic Card's drivers it crashed on reboot, always with the black screen after Win logo. I installed several ATI drivers, namelly 14.9, 14.11 beta, 13.12... and nothing worked.
I flashed the Mother Board BIOS to the latest version, formatted the HDD doing a fresh install of Win 7, installed Catalyst first and then the drivers, the drivers without catalyst, etc. and nothing worked, always getting a black sreen on reboot once the Graphic Card's drivers were installed. I even swapped the Graphic Card to a different slot to no avail.
Right now I'm using my old Radeon HD 5670 with the latest drivers and everything works just fine. It even works fine if I keep both Graphic Cards installed with the monitor plugged to the older card. I find this odd since to do so, Windows loads both cards drivers with no errors. But once I switch to the new card everything goes black.
Can someone help me out? I've tried to contact my vendor's technical support through mail but they're not answering. I fear that I'll have to report it as DOA and swap it out, which will take quite some time taking into consideration the way things tend to work around here.
EDIT - I don't have a 2nd system to test it on.

Nope. Not driver issue at all. I tested at least 3 different drivers, all with the same result. Besides, I used both Driver Fusion and Driver Cleaner and CClean to remove any non-deleted registry entries. Always got the same problem. Went as far as formating the drive and doing a clean Win install. The problem persisted.
Tried installing drivers without Catalyst to no avail. Tried installing Cataltst first and then the drivers. Nothing. It always crashed omce the drivers were installed.

WINDOWS BLACK SCREEN AFTER VM WARE DEMO PLEASE HELP

I tried installing VM Ware Fusion Demo. I could not use my wireless mouse and keyboard, now I can't even startup with Windows. I get a black screen. Please help!

Go into safemode and uninstall the Nvidia driver you have installed and after restarting the computer and allowing extra time for windows to install a default driver for the graphics, install the Windows 7 driver for your computer found in the Toshiba download page for your laptop.
If you have issues with the screen blacking out after doing that, follow the instructions found here and this will correct that.
http://forums.toshiba.com/t5/Qosmio-Laptops/Qosmio-X305-Q701-Black-Screen-Crash-edit-Solution/td-p/9...
Welcome to the Toshiba user forums.
For those of you who do not know what a user forum is, it is a community of users who volunteer time to help other users. Anyone can participate. It's 100% voluntary.
Being super active is never a requirement

Lenovo G560 - Issue with won't boot and black screen after HDD upgrade

Lenovo G560 - Issue with won't boot and black screen after HDD upgrade.
What happen: My laptop was working fine, no blue screen issue, no funny business at all. I bought a new SSD Intel 120 GB and thought it would be a good idea to replace the HDD. I shutdown and disconnected the power adapter, waited a couple of minutes and removed the battery. I opened up the back case and replaced the HDD. And put all the screws back and put the battery back in.
Problem: The very first time I turned the power on, nothing happens besides a black screen. I pressed the dvd drive it works and opens up and closes. I waited for about 30 mins and still has blac screen. When I mean black screen, no bios menu, no logo, just a black screen with the fan sound on.
I have tried these:
1. Unplugged everything - battery, adapter, and pressed the power on button for about 60 seconds, nothing, the laptop turns on with the LED display on for both on and battery LED's. But nothing but black screen, no sound of windows loading just the fan and black screen.
2. I tried putting back my old 2.5" and nothing but black screen.
Thoughts and suggestions?
Solved!
Go to Solution.

Hi Autoexit173,
Welcome to Lenovo Community!
As per the query we understood that you are facing issue with system not booting in your Lenovo G560 laptop.
As you have mentioned that the system not booting, please try to remove the RAM and turn on the system and check if you can hear any beep sound. Also try to clean the RAM slots and check for the issue.
Click here for the steps to remove the RAM and refer page number 40.
Hope this helps. Do post back if issue persists!
Best regards,
Ashwin.S
Did someone help you today? Press the star on the left to thank them with a Kudo!
If you find a post helpful and it answers your question, please mark it as an "Accepted Solution"! This will help the rest of the Community with similar issues identify the verified solution and benefit from it.
Follow @LenovoForums on Twitter!

Black Screen After Windows 8 64-bit Upgrade (Clean Install) on TouchSmart IQ508A (IQ500 series)

Hi there,
Just installed Windows 8 and am getting a black screen after booting up like many others. I currently have disabled the graphics driver and this has solved the black screen issue but I can no longer use my web cam for Skype (although web cam works for W8 Camera App oddly).
To date I have tried the following:
Loading up the latest Nvidia drivers from the Nvidia website
Attempting to use the drivers for Windows 7 both in compatability mode and normally. I unzipped SP44488 to get this working
I know many others are having this problem so I really would like someone from HP to respond and state whether a Windows 8 display driver for the Nvidia GE Force 9300M GS is being developed.
I ran the compatability wizard prior to the clean install and it came up with no issues so I am very disappointed I am having these problems.
I've found out that HP have a customised version of the above card so that explains why the Nvidia drivers dont work so I believe HP is therefore obligated to provide a driver.
If anyone else is having similar issues please respond as this will hopefully lead to more action.
cheers
Steve

I'm in the same boat. On my IQ804, the Nvidia GE Force 9300M GS card crashes when I use NVidia's latest Windows 8 driver and Microsoft's LIVE UPDATE drivers. I have to resort to the Standard VGA driver in order for the pc not to crash into a black screen.
I read on another forum you can try installing a July 2012 version of the driver from NVidia and that should solve the problem. I tried it once. Using the July 2012 version, the screen would stay on longer, but eventually it crashes into a black screen...but definitely more usable than the latest from NVidia and Microsoft.
I too have heard that HP used a customized version of the graphics card and that's why neither HP nor NVidia's drivers work.
I also tried installing the Nvidia GE Force 9300M GS drivers for Windows 7 that I downloaded from the HP website. It didn't work either. It actually failed to install altogether, saying my system is incompatible.
As is, the pc works fine. But videos and games that require motion is noticably choppy.
Any help from HP??

Black Screen after logging in locally to Windows 7 that previously had an open RDP session.

Here is what happens. I leave my home computer on (running Windows 7 Ultimate) and sometimes I will remote to it from another location (work, friends house, or wherever). When I return home, I will go to login, the screen then goes blank (no mouse cursor
or anything). I have to do a cold boot to get back into Windows. This only happens if I ever RDP into it sometimes during the day. It seems random. I've tried logging off the RDP session, just closing it without logging off, nothing seems to be the answer
in that regard. It seems very random at times. I'll go a week and I can come home and it will login fine with no problems. Then the next week it starts giving me the black screen after I come home and login locally. I've seen several black screen issues here,
but usually they are getting it before logon. Anyone have a clue what might be causing this?

Hello,
The Windows Desktop Perfmon and Diagnostic tools forum is to discuss performance monitor (perfmon), resource monitor (resmon), and task manager, focusing on HOW-TO, Errors/Problems, and usage scenarios.
As the question is off topic here, I am moving it to the
Where is the Forum... forum.
Karl
When you see answers and helpful posts, please click Vote As Helpful, Propose As Answer, and/or Mark As Answer.
My Blog: Unlock PowerShell
My Book: Windows PowerShell 2.0 Bible
My E-mail: -join ('6F6C646B61726C40686F746D61696C2E636F6D'-split'(?<=\G.{2})'|%{if($_){[char][int]"0x$_"}})

Black screen after login while on battery with graphics switching enabled

Getting a black screen after entering my password while logging into my account while on battery with graphics switching enabled. Everything is up and running, I just can't see it.
I can log into the guest account on battery
I can log into my account while plugged into power
I can log into my account on battery if graphics switching is disabled
I believe something that is starting up in my account is causing the system to switch from integrated to discrete graphics on login, and that switch isn't working correctly on battery power.
As a work around for now, I can run with graphics switching disabled, but I'd like to solve this so I get longer battery life.
MacBook Pro Retina 15"
Mountain Lion
All updates applied

I had the same issue and managed to reslove it.
Shut down your machine.
Power it back on while holding the 'shift' key (left or right, doesn't matter)
You will see a greay progress bar go across the screen while you boot in to 'safe boot'
Once booted, login, and go to Energy Saver and turn on 'Automatic Graphics Switching'.
Reboot back in to normal mode, and you should be able to log back in and see again.
I did this without being plugged into AC power.
Hope it helps!
Cheers!

Qosmio X870-149 - Black screen after Update to win 8.1

After an update to win 8.1 I got a black screen after login , the only thing I could do was to press zero during startup and make a recovery installation .
It took 40 houres , I do not know why it took so long , but when it was over, the HDD was completely empty , so I installed win 7 instead , since I had not made ??a recovery CD . The problem now is that I still get black screen in between , and thinking that it might be a heat problem , I still have warranty , but I do not know if it applies when I installed win 7 on the machine.
I still have a warranty on my toshiba Qosmio

Hi
Well, the warranty covers the hardware related problems. It does not cover any issues related to the software.
Now the open question is: why the black screen appears?
Is it hardware or software issue?
What happens if you access the BIOS?
Can you see anything on the screen?
Is something visible on the external monitor?

WINDOWS 8 BLACK SCREEN AFTER LOGIN PROBLEM

Please help me i have a problem with my computer it goes black screen after i login
my desktop is hp pavilion a5055d my os is windows 8 i dont know what the problem
i have a ati radeon xpress 1100 for videocard ..
I tried to restart many times.

Hi,
Did this issue occur before?
Try to logon with Safe Mode to see if the same issue occurs.
Furthermore, you can try to update BIOS for your machine?
You can refer these article to update BIOS if your machine cannot boot:
http://www.ehow.com/how_7356859_update-bios-windows-won_t-boot.html
http://www.wikihow.com/Fix-a-PC-Which-Won't-Boot
Hope that helps.
Leo Huang
TechNet Community Support

Black Screen After Upgrading to Windows 8

Hi
I'm experiencing a black screen after upgrading a Dell N5050 B890 to Windows 8.
Tried to refresh the installation but the problem persited. re-installed the Windows 8, the machine logged in successfully but the problem arose again after reboot.
Urgent assistance needed

This problem is solved...
I guess the problem is concerned with the display module controller in the BIOS which is having a slight compatibility issue with windows 8.
This issue is solved by updating the BIOS of your Laptop/PC to the latest version. You can download the latest BIOS from the website of the Laptop company/Motherboard Company.
But for updating the BIOS, you have to start your computer/Laptop for at least one time in Normal Mode. So here are the steps to do so...
1) Boot the Laptop/PC.
2) After the boot screen (The Circle Animation & Windows 8 logo), you will be presented by the lovely & awesome blank screen.
3) Wait for 1 minute so that drivers load into the memory.
4) Press the Power button of your laptop/PC for only a moment (Just Press and release it quickly. Don't hold. We don't want to shut down).
5) This will force the laptop/PC to go into Sleep mode.
6) When the laptop/PC goes in sleep, the laptop fan & other sounds will stop.
7) After 4-5 seconds, press the power button again & release it quickly.
8) Voilllaa!!! The laptop/PC starts & you are presented with the lock screen. Now..... Login! What are you waiting for! :P
This is not the permanent solution. It just lets you start you Laptop/PC.
After updating the BIOS, I strongly suggest that you must download the latest graphics driver for your Computer/Laptop to avoid any further issues.

IOS adhoc displays black screen after launch

Hi,
my iOS application displays black screen after slash screen.nothing happens and couldn't see any proper errors on debug utility.
I can build adhoc using flash builder and it's works fine but problem occurs when I create ipa using dumped config file on command line(ant)
I'm using flex sdk 4.6 and AirSDK 15.0(overladed) .my application includes few native extensions.
mxmlc
mxmlc -load-config app-config.xml src/mobapp.mxml -output myapp.swf
adt
<target name="build-release-adhoc-package-ipa">
    <echo>::building captive-runtime release-adhoc ipa..</echo>
    <exec executable="${FLEX_BIN}/adt" failonerror="true">
        <arg line="-package" />
        <arg line="-target ipa-ad-hoc" />
        <arg line="-storetype pkcs12" />
        <arg line="-keystore ${provision.dir}/release-adhoc.p12" />
        <arg line="-storepass 12345" />
        <arg line="-provisioning-profile ${provision.dir}/release_adhoc.mobileprovision" />
        <arg line="${adhoc.dir}/ios-adhoc.ipa" />
        <arg line="${src}/mobapp-app.xml" />
        <arg line="myapp.swf" />
        <arg line="${icon.dir}/applicationIcon16.png" />
        <arg line="${icon.dir}/applicationIcon32.png" />
        <arg line="${icon.dir}/applicationIcon36.png" />
        <arg line="${icon.dir}/applicationIcon48.png" />
        <arg line="${icon.dir}/applicationIcon57.png" />
        <arg line="${icon.dir}/applicationIcon72.png" />
        <arg line="${icon.dir}/applicationIcon76.png" />
        <arg line="${icon.dir}/applicationIcon114.png" />
        <arg line="${icon.dir}/applicationIcon120.png" />
        <arg line="${icon.dir}/applicationIcon128.png" />
        <arg line="${icon.dir}/applicationIcon152.png" />
        <arg line="${base.dir}/[email protected]" />
        <arg line="-extdir ${src}/ane" />
        <arg line="-platformsdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPh oneOS.sdk" />
    </exec>
    </target>
please help.

Hi,
my iOS application displays black screen after slash screen.nothing happens and couldn't see any proper errors on debug utility.
I can build adhoc using flash builder and it's works fine but problem occurs when I create ipa using dumped config file on command line(ant)
I'm using flex sdk 4.6 and AirSDK 15.0(overladed) .my application includes few native extensions.
mxmlc
mxmlc -load-config app-config.xml src/mobapp.mxml -output myapp.swf
adt
<target name="build-release-adhoc-package-ipa">
    <echo>::building captive-runtime release-adhoc ipa..</echo>
    <exec executable="${FLEX_BIN}/adt" failonerror="true">
        <arg line="-package" />
        <arg line="-target ipa-ad-hoc" />
        <arg line="-storetype pkcs12" />
        <arg line="-keystore ${provision.dir}/release-adhoc.p12" />
        <arg line="-storepass 12345" />
        <arg line="-provisioning-profile ${provision.dir}/release_adhoc.mobileprovision" />
        <arg line="${adhoc.dir}/ios-adhoc.ipa" />
        <arg line="${src}/mobapp-app.xml" />
        <arg line="myapp.swf" />
        <arg line="${icon.dir}/applicationIcon16.png" />
        <arg line="${icon.dir}/applicationIcon32.png" />
        <arg line="${icon.dir}/applicationIcon36.png" />
        <arg line="${icon.dir}/applicationIcon48.png" />
        <arg line="${icon.dir}/applicationIcon57.png" />
        <arg line="${icon.dir}/applicationIcon72.png" />
        <arg line="${icon.dir}/applicationIcon76.png" />
        <arg line="${icon.dir}/applicationIcon114.png" />
        <arg line="${icon.dir}/applicationIcon120.png" />
        <arg line="${icon.dir}/applicationIcon128.png" />
        <arg line="${icon.dir}/applicationIcon152.png" />
        <arg line="${base.dir}/[email protected]" />
        <arg line="-extdir ${src}/ane" />
        <arg line="-platformsdk /Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/SDKs/iPh oneOS.sdk" />
    </exec>
    </target>
please help.

My early 2008 Macbook Pro is suffering from black screen after Yosemite update

My early 2008 Macbook Pro is suffering from black screen after Yosemite update. It ran beta 5 great but failed on restart after beta 6 install. There is no cursor but I can hear the HDD spooling up. I have tried booting in safe mode, PRAM reset and SMC reset but nothing works. After the first 5 days of every now and then trying to start it, it started fine. I used the machine all day with no problems, it had rolled back the install and was back on beta 5. I decided to try the update again, the same thing happened and it has stayed black for over a week now. It wont work with a monitor either. Help!

Hello Adam,
I would try instead of installing the beta software, to install the official build of OS X Yosemite from the Mac App Store to see if that gets you passed the no video issue when updating the beta software.
How to install OS X Yosemite on your Mac
http://support.apple.com/en-us/HT6412
Regards,
-Norm G.

Aperture Black screen after edits...

Similar Messages

Maybe you are looking for