[svn:fx-trunk] 10224: Fix for seemingly invalid use of 'tar', fixes AIR integration extraction on Snow Leopard.

Revision: 10224
Author:   [email protected]
Date:     2009-09-14 05:35:41 -0700 (Mon, 14 Sep 2009)
Log Message:
Fix for seemingly invalid use of 'tar', fixes AIR integration extraction on Snow Leopard.
QE notes: None
Doc notes: None
Bugs: N/A
Reviewer: Gaurav
Tests run: Tested build on Windows.
Is noteworthy for integration: No
Modified Paths:
    flex/sdk/trunk/frameworks/build.xml

Similar Messages

[svn:fx-trunk] 14729: Fix merge 14728 which I didn't do from root.

Revision: 14729
Revision: 14729
Author:   [email protected]
Date:     2010-03-12 07:07:33 -0800 (Fri, 12 Mar 2010)
Log Message:
Fix merge 14728 which I didn't do from root.
Property Changed:
    flex/sdk/trunk/

Still struggling to understand why copying the entire root dir to a disk image and then restoring from that image did not, as expected, yield an identical system, and why I even had to reinstall after doing this.
Because there is a lot more going on under the hood than merely copying files.
The only way to do what you want is to use cloning software like Carbon Copy Cloner.
My advice is to rescue your personal files to a regular non-TimeMachine external drive, Zero erase the ENTIRE drive and install OS X fresh and update, then your programs from original sources and files from backup.
Then, make a bootable clone and you can copy that as many times as you want and each one is bootable.
Most commonly used backup methods
How to erase and install Snow Leopard 10.6

I can't seem to install flash player on iPhone or MacBook after snow leopard update...why??

I can't seem to install flash player on iPhone or MacBook after snow leopard update...why?? How can I fix this?

Flash Player doesn't work on IOS devices.
On Macbook, try un-installing and then re-installing.
Adobe Flash Uninstaller
Adobe Flash Player

[svn:fx-trunk] 5408: Fix for - Compiler error using Reparent in a Halo Navigator.

Revision: 5408
Author: [email protected]
Date: 2009-03-18 20:57:19 -0700 (Wed, 18 Mar 2009)
Log Message:
Fix for - Compiler error using Reparent in a Halo Navigator.
QE Notes: None.
Doc Notes: None.
Reviewer: Paul, please review.
Bugs: SDK-20099
tests: checkintests
Ticket Links:
http://bugs.adobe.com/jira/browse/SDK-20099
Modified Paths:
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/builder/ComponentBuilder.jav a

[svn:fx-trunk] 8474: * Fixed the AST generation code path of Vector typed variables and

Revision: 8474
Author:   [email protected]
Date:     2009-07-09 07:20:32 -0700 (Thu, 09 Jul 2009)
Log Message:
Fixed the AST generation code path of Vector typed variables and
properties with Bindable.
tests Passed: checkintests
Needs QA: YES
Needs DOC: NO
Bug fixes: SDK-21587
API Change: NO
Reviewer: Peter D.
Code-level description of changes:
   AbstractSyntaxTreeUtil.java
     Modified generateParameter(*) to use generateTypeExpression().
   binding/BindableSecondPassEvaluator.java
     Modified generateGetter() to use AbstractSyntaxTreeUtil.generateTypeExpression().
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21587
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/AbstractSyntaxTreeUtil.java
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/binding/BindableSecondPassEva luator.java

I got again a total system freeze today when I wanted to launch firefox using only the openbox menu, without wbar running.
So I decided to try now the 'nouveau.noaccel=1' kernel command line parameter, and to use again wbar for my frequently used applis.
In the Xorg log, the differences are:
without 'nouveau.noaccel=1'
[ 30.761] (II) UnloadModule: "nv"
[ 30.761] (II) Unloading nv
[ 30.761] (--) Depth 24 pixmap format is 32 bpp
[ 30.762] (II) NOUVEAU(0): Opened GPU channel 0
[ 30.765] (II) NOUVEAU(0): [DRI2] Setup complete
[ 30.765] (II) NOUVEAU(0): [DRI2] DRI driver: nouveau
[ 30.765] (II) NOUVEAU(0): [DRI2] VDPAU driver: nouveau
[ 30.776] (II) EXA(0): Driver allocated offscreen pixmaps
[ 30.777] (II) EXA(0): Driver registered support for the following operations:
[ 30.777] (II) Solid
[ 30.777] (II) Copy
[ 30.777] (II) Composite (RENDER acceleration)
[ 30.777] (II) UploadToScreen
[ 30.777] (II) DownloadFromScreen
[ 30.777] (==) NOUVEAU(0): Backing store disabled
[ 30.777] (==) NOUVEAU(0): Silken mouse enabled
with 'nouveau.noaccel=1'
[ 1191.621] (II) UnloadModule: "nv"
[ 1191.621] (II) Unloading nv
[ 1191.621] (--) Depth 24 pixmap format is 32 bpp
[ 1191.621] (EE) NOUVEAU(0): Error creating GPU channel: -19
[ 1191.621] (EE) NOUVEAU(0): Error initialising acceleration. Falling back to NoAccel
[ 1191.621] (==) NOUVEAU(0): Backing store disabled
[ 1191.621] (==) NOUVEAU(0): Silken mouse enabled
[ 1191.621] (==) NOUVEAU(0): DPMS enabled
So now 3D acceleration is disabled.
I will see now if the system is stable enough for my daily usage and gives satisfactory performances.
I am almost sure that the mesa nouveau dri driver is the cause of the freezes.
Last edited by berbae (2013-03-27 10:07:42)

[svn] 1307: modules: added support for automatically adding " use namespace X", depending on the -target-player value

Revision: 1307
Author: [email protected]
Date: 2008-04-18 16:28:33 -0700 (Fri, 18 Apr 2008)
Log Message:
modules: added support for automatically adding "use namespace X", depending on the -target-player value
* similar to how we add "use namespace AS3"
* symmetric with ASC's -use feature, however we don't have equivalent commandline support yet
Bugs: n/a
QA: Nothing in particular, except for testing the new functionality of -target-player (email me about this)
Doc: Maybe: If we doc about "use namespace AS3" being added to all Flex compiles, we may want to talk about this.
Reviewers: Pete and Erik
Modified Paths:
flex/sdk/trunk/frameworks/flex-config.xml
flex/sdk/trunk/lib/asc.jar
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/embedding/BatchCompiler.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/embedding/Compiler.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/embedding/ScriptCompiler.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/Parser.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/util/Context.java
flex/sdk/trunk/modules/asc/src/java/macromedia/asc/util/ContextStatics.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/SymbolTable.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/as3/MetaDataParser.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/Configuration.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/common/DefaultsConfigurator.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StyleDef.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StyleModule.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/css/StylesContainer.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/InterfaceCompiler.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/reflect/TypeTable.java
flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/mxml/rep/AtEmbed.java
flex/sdk/trunk/modules/swfutils/src/java/flash/swf/tools/SwfxPrinter.java

Thanks for your attention.
In the above logs, higher resolutions seems to be detected on both screens, hence my surprise :
[ 391.631] (II) intel(0): Printing probed modes for output LVDS1
[ 391.631] (II) intel(0): Modeline "1600x900"x60.0 110.00 1600 1664 1706 2010 900 903 906 912 -hsync -vsync (54.7 kHz eP)
[ 391.897] (II) intel(0): Printing probed modes for output HDMI1
[ 391.897] (II) intel(0): Modeline "1680x1050"x59.9 119.00 1680 1728 1760 1840 1050 1053 1059 1080 +hsync -vsync (64.7 kHz eP)
If it can help here is also my current xrandr output (after having called it manually to use the preferred resolution of each screen)
itanguy ~ $ xrandr
Screen 0: minimum 320 x 200, current 1680 x 1050, maximum 8192 x 8192
LVDS1 connected 1600x900+0+0 (normal left inverted right x axis y axis) 309mm x 174mm
1600x900 60.0*+ 40.0
1024x768 60.0
800x600 60.3 56.2
640x480 59.9
VGA1 disconnected (normal left inverted right x axis y axis)
HDMI1 connected 1680x1050+0+0 (normal left inverted right x axis y axis) 434mm x 270mm
1680x1050 59.9*+
1280x1024 75.0 60.0
1152x864 75.0
1024x768 75.1 60.0
800x600 75.0 60.3
640x480 75.0 60.0
720x400 70.1
DP1 disconnected (normal left inverted right x axis y axis)
HDMI2 disconnected (normal left inverted right x axis y axis)
HDMI3 disconnected (normal left inverted right x axis y axis)
DP2 disconnected (normal left inverted right x axis y axis)
DP3 disconnected (normal left inverted right x axis y axis)
If needed, I may reboot and provide xrandr output after boot (it will be 1024x768), or could other logs help you ? Please ask...

Mac Pro seems to be missing 0.5 GB of ram after Snow Leopard install

I just installed Snow Leopard on my Mac Pro (2 x 2.8 GHz Quad-Core Intel Xeon). The computer has only ever had the default 2 GB of RAM that comes with it from Apple. I know I need more, it's on order. The odd thing that I noticed after installing Snow Leopard is that the computer now only reports 1.5 GB or RAM in the "About This Mac" box. Specifically it says: "1.5 GB 800 MHz DDR2 FB-DIMM". Odd.
Second if I click "More Info..." below is what I see in the memory slots.
Does anyone know what might have caused this, or if its possible to get that 0.5 GB back?
Second I just ordered 8 GB of RAM (MACMEM 4Gx2|KST KTA-MP800K2/8G R). If the above issue doesn't get resolved what do you suggest I do when the new RAM arrives? Should I just add in the new stuff for a total of 9.5 GB, or should I also take out the existing RAM that's reporting odd values? I'm wondering if the missing 0.5 GB is a symptom of other issues, and maybe that RAM is "sick" and could slow things down somehow.
Thanks for any ideas.
Jesse
Memory Slots:
ECC: Enabled
DIMM Riser B/DIMM 1:
Size: 1 GB
Type: DDR2 FB-DIMM
Speed: 800 MHz
Status: OK
Manufacturer: 0x802C
Part Number: 0x3138484631323837324A4438304544364434
Serial Number: 0xD834438C
DIMM Riser B/DIMM 2:
Size: Empty
Type: Empty
Speed: Empty
Status: Empty
Manufacturer: Empty
Part Number: Empty
Serial Number: Empty
DIMM Riser A/DIMM 1:
Size: 512 MB
Type: DDR2 FB-DIMM
Speed: 800 MHz
Status: OK
Manufacturer: 0x802C
Part Number: 0x3138484631323837324A4438304544364434
Serial Number: 0xD8344473
DIMM Riser A/DIMM 2:
Size: Empty
Type: Empty
Speed: Empty
Status: Empty
Manufacturer: Empty
Part Number: Empty
Serial Number: Empty
DIMM Riser B/DIMM 3:
Size: Empty
Type: Empty
Speed: Empty
Status: Empty
Manufacturer: Empty
Part Number: Empty
Serial Number: Empty
DIMM Riser B/DIMM 4:
Size: Empty
Type: Empty
Speed: Empty
Status: Empty
Manufacturer: Empty
Part Number: Empty
Serial Number: Empty
DIMM Riser A/DIMM 3:
Size: Empty
Type: Empty
Speed: Empty
Status: Empty
Manufacturer: Empty
Part Number: Empty
Serial Number: Empty
DIMM Riser A/DIMM 4:
Size: Empty
Type: Empty
Speed: Empty
Status: Empty
Manufacturer: Empty
Part Number: Empty
Serial Number: Empty

I am running a '07 Mac Pro that has had 7GB RAM since I bought it almost 3 years ago - the original 2x512MB + 6x1GB purchased from Crucial.com. Suddenly, after installing Snow Leopard, only 6GB are being recognized; two of the 1GB DIMM's now read as 512MB in System Profiler, and the Part Number and Serial Number listed for those modules are incorrect.
After searching these forums for ideas, I have tried:
• Resetting the PRAM -- no change
• Running Apple Hardware Test -- no problems found
• Running TechTool Deluxe 3.1.3 (updated for Snow Leopard) -- no problems found
• Running TechTool Pro 5.1.6 (updated for Snow Leopard) -- no problems found
• Running system scanner (beta) from Crucial.com - cannot read installed RAM
The only thing I haven't tried is physically reinstalling the modules, but since the computer hasn't moved in months that seems pretty doubtful. If I make any progress I'll post again, otherwise, I'll be contacting Crucial for replacements.

[svn:fx-trunk] 7765: Fixing up some copyrights, adding copyrights, and fixing up some legal-eese for the Flash Component Kit For Flex.

Revision: 7765
Author:   [email protected]
Date:     2009-06-11 15:58:18 -0700 (Thu, 11 Jun 2009)
Log Message:
Fixing up some copyrights, adding copyrights, and fixing up some legal-eese for the Flash Component Kit For Flex.
Also, updating the MXP to get latest changes to base classes.
QE Notes: -
Doc Notes: -
Bugs: SDK-21670
Reviewer: No one (just header updates)
tests: checkintest (seem to fail due to local changes to ScrollBar, which I'm not checking in here)
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-21670
Modified Paths:
    flex/sdk/trunk/frameworks/flash-integration/FlexComponentKit.mxp
    flex/sdk/trunk/frameworks/flash-integration/readme.txt
    flex/sdk/trunk/frameworks/projects/flash-integration/FlexComponentKit.mxi
    flex/sdk/trunk/frameworks/projects/flash-integration/JSFL/Convert Symbol to Flex Component.jsfl
    flex/sdk/trunk/frameworks/projects/flash-integration/JSFL/Convert Symbol to Flex Container.jsfl
    flex/sdk/trunk/frameworks/projects/flash-integration/JSFL/MakeFlexComponent.jsfl
    flex/sdk/trunk/frameworks/projects/flash-integration/readme.txt
    flex/sdk/trunk/frameworks/projects/flash-integration/src/mx/flash/ContainerMovieClip.as
    flex/sdk/trunk/frameworks/projects/flash-integration/src/mx/flash/UIMovieClip.as

[svn:fx-trunk] 13257: Fix for @inheritDoc not working on a setter, but works on a getter

Revision: 13257
Revision: 13257
Author:   [email protected]
Date:     2010-01-04 10:49:13 -0800 (Mon, 04 Jan 2010)
Log Message:
Fix for @inheritDoc not working on a setter, but works on a getter
QE notes: None.
Doc notes: None
Bugs: SDK-24727
Reviewed By: Paul
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24727
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/ClassTable.java

steabert wrote:
Hi,
I had a similar problem with my Dell Latitude E4310, and apparently also the E6410, E6510.
The solution for me was to add the following line to /etc/modprobe.d/modprobe.conf:
options snd-hda-intel model=dell-s14
I tried that, unfortunately it does not work with this chipset. I do get a different set of channels though but it still cannot record anything. Maybe this chipset is too "new" for alsa. The latest release dates back from the end of January. Support for it is explicitly stated in the changelog to 1.0.24 but perhaps the recording part of it slipped through the cracks. ALSA bug tracking system seems quite closed.

[svn:fx-trunk] 12962: Fix for ASDoc not saving event type for [Bindable] metadata tag

Revision: 12962
Revision: 12962
Author:   [email protected]
Date:     2009-12-15 10:32:23 -0800 (Tue, 15 Dec 2009)
Log Message:
Fix for ASDoc not saving event type for metadata tag
QE notes: None.
Doc notes: None
Bugs: SDK-24706
Reviewed By:Corey
Tests run: checkintests
Is noteworthy for integration: No
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-24706
Modified Paths:
    flex/sdk/trunk/modules/compiler/src/java/flex2/compiler/asdoc/TopLevelClassesGenerator.ja va

aplay -l
**** List of PLAYBACK Hardware Devices ****
card 0: NVidia [HDA NVidia], device 3: NVIDIA HDMI [NVIDIA HDMI]
Subdevices: 1/1
Subdevice #0: subdevice #0
Which correspondents fine with the
device "hw:0,3"
in my mpd.conf alsa section.
Also sound worked fine withh this config before I started installing ffmpeg-svn and alikes
hokasch:
I tried changing the mixer to "Master" but that did not change much.

[svn:fx-trunk] 12978: Fix for possible null deref in Effect. captureMoreStartValues().

Revision: 12978
Revision: 12978
Author:   [email protected]
Date:     2009-12-15 17:12:29 -0800 (Tue, 15 Dec 2009)
Log Message:
Fix for possible null deref in Effect.captureMoreStartValues(). Seems unlikely to ever occur since the function is not really there for random calling outside of data effects, but the fix was simple.
QE notes: none
Doc notes: none
Bugs: sdk-16451
Reviewer: Jason
Tests run: checkintests, Mustella mx/effects, mx/ListDataEffects
Is noteworthy for integration: no
Ticket Links:
    http://bugs.adobe.com/jira/browse/sdk-16451
Modified Paths:
    flex/sdk/trunk/frameworks/projects/framework/src/mx/effects/Effect.as

[svn:fx-trunk] 7473: Fix for 'ant asdoc' does not work.

Revision: 7473
Author:   [email protected]
Date:     2009-06-01 12:09:26 -0700 (Mon, 01 Jun 2009)
Log Message:
Fix for 'ant asdoc' does not work.
It should now work from both svn and package zip.
Bugs: SDK-15306
QE Notes: None.
Doc Notes: None.
tests: checkintests
Ticket Links:
    http://bugs.adobe.com/jira/browse/SDK-15306
Modified Paths:
    flex/sdk/trunk/asdoc/build.xml
    flex/sdk/trunk/build.xml

[svn:fx-trunk] 13136: Fix for FLEXENT-1196 ( Replay of click on NavigatorContent does not close the combobox)

Revision: 13136
Revision: 13136
Author:   [email protected]
Date:     2009-12-21 17:40:28 -0800 (Mon, 21 Dec 2009)
Log Message:
Fix for FLEXENT-1196 (Replay of click on NavigatorContent does not close the combobox)
We need not record OPEN event when it is triggered from a KeyBoard event that types a character. Replaying the type event would automatically open the drop down.
Ticket Links:
    http://bugs.adobe.com/jira/browse/FLEXENT-1196
Modified Paths:
    flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/SparkComboBoxAutomationImpl.as
    flex/sdk/trunk/frameworks/projects/automation_spark/src/spark/automation/delegates/compon ents/supportClasses/SparkDropDownListBaseAutomationImpl.as

[svn:fx-trunk] 11999: Fixed: ASC-3889 - Using setting in a for loop causes Verify error

Revision: 11999
Revision: 11999
Author:   [email protected]
Date:     2009-11-19 11:37:09 -0800 (Thu, 19 Nov 2009)
Log Message:
Fixed: ASC-3889 - Using setting in a for loop causes Verify error
Notes: emit pop after callstatic to a void function to balance the stack.
Reviewer: jodyer+
Testing: asc,tamarin,flex checkin tests
Ticket Links:
    http://bugs.adobe.com/jira/browse/ASC-3889
Modified Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/semantics/CodeGenerator.java

Blacklisting the ahci module does indeed get rid of the error. Would be nice to figure out why it was conflicting with the ahci module though.
I have not yet tried the 173xx drivers, but the latest drivers for the Quadro FX 580 are the 256.53 drivers according to nvidia.
Posted at the nV forums (http://www.nvnews.net/vbulletin/showthread.php?t=155282), so we'll see what they suggest.

[svn:fx-trunk] 11530: Fix ASC-3790 ( conditional expression in for loop causes verifier error) r=jodyer

Revision: 11530
Author:   [email protected]
Date:     2009-11-06 13:23:05 -0800 (Fri, 06 Nov 2009)
Log Message:
Fix ASC-3790 (conditional expression in for loop causes verifier error) r=jodyer
Ticket Links:
    http://bugs.adobe.com/jira/browse/ASC-3790
Modified Paths:
    flex/sdk/trunk/modules/asc/src/java/macromedia/asc/parser/ConditionalExpressionNode.java

[svn:fx-trunk] 10224: Fix for seemingly invalid use of 'tar', fixes AIR integration extraction on Snow Leopard.

Similar Messages

Maybe you are looking for