4 Replies Latest reply on Oct 20, 2009 8:30 AM by C. Agruss (Adobe)

    Strange launching problems on OS X 10.6

    Crt Gorup Level 1

      I was using Flex 3 (on main disk drive) and Flash Builder 4 beta 2 (installed on non-case sensitive partition on USB drive). Flash Builder 4 was working fine until I tried to deactivate (function in Help menu) Flash Builder 4 to change its serial number. I was expecting that FB4 would restart and ask me for a new serial number, but that didn't happen. When I reopened it wasn't even able to get until to the welcome window. Then I uninstalled Flex 3 and Flash Builder 4 from my computer, rebooted and reinstalled the new FB4 beta 2. When I run it I see the window where I can choose the language and agree with the license agreement, but when I click "Agree" FB4 beta 2 crashes. Does anybody have and idea how to fix this?

       

      I have also attached atm.log, system.log shows this exception:

       

      Oct 19 10:33:18 jabuk-2 /Volumes/Mikrofoncek/fb4/FlashBuilder.app/Contents/MacOS/FlashBuilder[42136]: Unrecognized Java VM option ignored: -Xdock:name=Flash Builder

      Oct 19 10:33:18 jabuk-2 /Volumes/Mikrofoncek/fb4/FlashBuilder.app/Contents/MacOS/FlashBuilder[42136]: Unrecognized Java VM option ignored: -Xdock:icon=../Resources/fb_app.icns

      Oct 19 10:33:18 jabuk-2 /Volumes/Mikrofoncek/fb4/FlashBuilder.app/Contents/MacOS/FlashBuilder[42136]: Unrecognized Java VM option ignored: -XstartOnFirstThread

      Oct 19 10:33:21 jabuk-2 /Volumes/Mikrofoncek/fb4/FlashBuilder.app/Contents/MacOS/FlashBuilder[42136]: CPSSetForegroundOperationState(): This call is deprecated and should not be called anymore.

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: Exception in thread "Thread-0"

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: org.eclipse.swt.SWTException: Invalid thread access

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: at org.eclipse.swt.SWT.error(SWT.java:3777)

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: at org.eclipse.swt.SWT.error(SWT.java:3695)

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: at org.eclipse.swt.SWT.error(SWT.java:3666)

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: at org.eclipse.swt.widgets.Widget.error(Widget.java:681)

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:341)

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: at org.eclipse.swt.widgets.Shell.getShells(Shell.java:885)

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: at org.eclipse.swt.widgets.Shell.kEventWindowHidden(Shell.java:1213)

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2044)

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: at org.eclipse.swt.widgets.Display.windowProc(Display.java:4163)

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: at org.eclipse.equinox.launcher.JNIBridge._takedown_splash(Native Method)

      Oct 19 10:33:37 jabuk-2 [0x0-0x2f02f].org.eclipse.eclipse[42136]: at org.eclipse.equinox.launcher.JNIBridge.takeDownSplash(JNIBridge.java:110)

      Thanks, Crt
        • 1. Re: Strange launching problems on OS X 10.6
          Crt Gorup Level 1

          SInce my last post I have uninstalled all the Adobe products that use FLEXnet licensing, uninstalled Flash Builder 4, manually removed all the remaining FLEXnet files. At the end I have reinstalled Flex Builder 3, which is now working (I assume that it is using different licensing system) and Flash Builder 4 beta 2. Unfortunately it is not working, even with license repair tools I can't fix the problem. I have attached new amt.log. Can anybody see what is wrong? Thanks.

          • 2. Re: Strange launching problems on OS X 10.6
            C. Agruss (Adobe) Level 3

            Hi,

             

            Thanks for sending your amt log for analysis. According to the log, the Adobe Product Configuration Database (PCD) is missing.

             

            Sounds as if you've run into this known issue on Snow Leopard:

             

            FB-22869 - Licensing error prevents Flash Builder from launching on OSX 10.6.1 (Snow Leopard).

             

            Workaround:

            After installing on 10.6.1, run the mini-installer found in your Flash Builder installation folder:

            /install.support/builder-common-mul/Setup.app

             

             

            Let us know whether or not that resolves the problem,

             

            -Chris

            • 3. Re: Strange launching problems on OS X 10.6
              Crt Gorup Level 1

              Hi,

               

              Thanks for your help, but even if Flash Builder is located on a non-case sensitive partition I can't run Setup.app. At the moment I am having only Flash Builder on non-case sensitive partition, the OS is still on my old (case sensitive) partition. Is this a problem and I have to install a separate copy of OS or are there any special system requirements for running Setup.app that I am not aware of?

               

              System.log says:

               

              Oct 20 08:02:38 jabuk-2 [0x0-0x73073].com.adobe.Installers.Setup[1469]: Begin Adobe Setup

              Oct 20 08:02:38 jabuk-2 [0x0-0x73073].com.adobe.Installers.Setup[1469]: UI mode: Full GUI

              Oct 20 08:02:40 jabuk-2 [0x0-0x73073].com.adobe.Installers.Setup[1469]: End Adobe Setup.  Exit code: 10

              Oct 20 08:02:40 jabuk-2 com.apple.launchd.peruser.501[124] ([0x0-0x73073].com.adobe.Installers.Setup[1469]): Exited with exit code: 10

              Thanks.

               

              Crt

              • 4. Re: Strange launching problems on OS X 10.6
                C. Agruss (Adobe) Level 3

                Hi Crt,

                 

                That's right, the OS X boot volume needs to be non-case-sensitive.

                 

                -Chris