Fix: Adobe AIR Apps Crash After Upgrading to Fedora 12

adobe_airAfter upgrading your system to Fedora 12, you may notice that some of your Adobe AIR applications no longer load properly.  The problem may persist even after you have reinstalled both Adobe AIR and the individual Adobe AIR applications.

An error you may receive when installing the AIR applications is shown below:

Application crashed with an unhandled SIGSEGV

The above problem is caused by an invalid certificate file.  Simply deleting the certificate file as shown below will cause your Adobe AIR applications to begin working again.

Run the following command from terminal to fix the problem:

sudo rm -rf /etc/opt/Adobe/certificates/crypt/


Posted

in

,

by

Comments

6 responses to “Fix: Adobe AIR Apps Crash After Upgrading to Fedora 12”

  1. Kevin Avatar
    Kevin

    awesome – thanks for the tip.

  2. Kevin Avatar
    Kevin

    awesome – thanks for the tip.

  3. Brian Avatar
    Brian

    Awesome, Pandora One desktop on Fedora 12, finally!

  4. Brian Avatar
    Brian

    Awesome, Pandora One desktop on Fedora 12, finally!

  5. omega7 Avatar
    omega7

    After playing with aucm, I noticed that adding new certs added the <UserPreferences> tags when adding a new cert. The config.xml from the adobe-certs package did not have this tag. I added it to each certificate object in config.xml, for example:

    <certificate trustAnchor="true" trusted="true" sslServerAuth="true" codeSign="true" >
    <UserPreferences/>
    <LastUpdatedBy trustAnchor="adobe" codeSign="adobe" sslServerAuth="adobe" trusted="adobe"/>
    <subjectHash>2afc57aa.0</subjectHash>
    <publicKeyHash>46tUTICh21ZDt5FKy/OCehNcCKt=</publicKeyHash>
    </certificate>

    That fixed all the SIGSEGV dumps. (And keeps you from getting all the unknown/unverified cert messages during application installation you get when you just rename the crypt directory.)

  6. omega7 Avatar
    omega7

    After playing with aucm, I noticed that adding new certs added the <UserPreferences> tags when adding a new cert. The config.xml from the adobe-certs package did not have this tag. I added it to each certificate object in config.xml, for example:

    <certificate trustAnchor="true" trusted="true" sslServerAuth="true" codeSign="true" >
    <UserPreferences/>
    <LastUpdatedBy trustAnchor="adobe" codeSign="adobe" sslServerAuth="adobe" trusted="adobe"/>
    <subjectHash>2afc57aa.0</subjectHash>
    <publicKeyHash>46tUTICh21ZDt5FKy/OCehNcCKt=</publicKeyHash>
    </certificate>

    That fixed all the SIGSEGV dumps. (And keeps you from getting all the unknown/unverified cert messages during application installation you get when you just rename the crypt directory.)

Leave a Reply

Your email address will not be published. Required fields are marked *