Firestorm
  1. Firestorm
  2. FIRE-6327

[STORM-1854] Linux Viewer crashes on startup after update to Fontconfig 2.9.0: Assertion `result != ((void *)0)' failed

    Details

    • Type: Bug Bug
    • Status: Passed QA
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: Phoenix Firestorm 4.0.1, Phoenix Firestorm 4.1.1
    • Fix Version/s: Phoenix Firestorm 4.3.0
    • Component/s: None
    • Labels:
      None
    • Environment:
      Firestorm-4-1-1-27433 (cannot run to copy&paste)
    • SL Avatar Name:
      Altair Memo
    • Reported In:
      Firestorm Beta 4.0.1.27000

      Description

      do-not-directly-run-firestorm-bin: fcmatch.c:850: IA__FcFontSort: Assertion `result != ((void *)0)' failed.

      EDIT (Whirly): https://jira.secondlife.com/browse/STORM-1854

        Issue Links

          Activity

          Sythos created issue -
          Hide
          Mysty Saunders added a comment - - edited

          Altair this is a known issue from LL. Please see the following Jira for more information on this bug

          https://jira.secondlife.com/browse/STORM-1854

          Mysty

          Show
          Mysty Saunders added a comment - - edited Altair this is a known issue from LL. Please see the following Jira for more information on this bug https://jira.secondlife.com/browse/STORM-1854 Mysty
          Whirly Fizzle made changes -
          Field Original Value New Value
          Summary Cannot start on linux [STORM-1854] Linux Viewer crashes on startup after update to Fontconfig 2.9.0: Assertion `result != ((void *)0)' failed
          Fix Version/s Phoenix Firestorm - Future [ 10036 ]
          Affects Version/s Phoenix Firestorm 4.0.1 [ 10103 ]
          Description do-not-directly-run-firestorm-bin: fcmatch.c:850: IA__FcFontSort: Assertion `result != ((void *)0)' failed. do-not-directly-run-firestorm-bin: fcmatch.c:850: IA__FcFontSort: Assertion `result != ((void *)0)' failed.

          EDIT (Whirly): https://jira.secondlife.com/browse/STORM-1854
          Hide
          thickbrick.sleaford added a comment -

          I'm not sure if this applies to the Linden viewer, but Firestorm 4.1 already comes with the right library, it's just missing a libfontconfig.so.1 symlink. This solves the problem:

          cd <where you put your firestorm>/lib/
          ln -si libfontconfig.so.1.4.4 libfontconfig.so.1
          
          Show
          thickbrick.sleaford added a comment - I'm not sure if this applies to the Linden viewer, but Firestorm 4.1 already comes with the right library, it's just missing a libfontconfig.so.1 symlink. This solves the problem: cd <where you put your firestorm>/lib/ ln -si libfontconfig.so.1.4.4 libfontconfig.so.1
          Whirly Fizzle made changes -
          Link This issue is related to FIRE-7632 [ FIRE-7632 ]
          Whirly Fizzle made changes -
          Link This issue is duplicated by FIRE-7746 [ FIRE-7746 ]
          Whirly Fizzle made changes -
          Link This issue is related to FIRE-7632 [ FIRE-7632 ]
          Whirly Fizzle made changes -
          Link This issue is duplicated by FIRE-7632 [ FIRE-7632 ]
          Hide
          Whirly Fizzle added a comment -
          Show
          Whirly Fizzle added a comment - Fixed rev 30526 ( http://hg.phoenixviewer.com/phoenix-firestorm-lgpl/rev/15cd21627d17 )
          Whirly Fizzle made changes -
          Assignee Nicky [ nickyd ]
          Whirly Fizzle made changes -
          Fix Version/s Phoenix Firestorm 4.3.0 [ 10327 ]
          Fix Version/s Phoenix Firestorm - Future [ 10036 ]
          Whirly Fizzle made changes -
          Status Open [ 1 ] Resolved [ 5 ]
          Resolution Fixed [ 1 ]
          Whirly Fizzle made changes -
          Link This issue is duplicated by FIRE-7915 [ FIRE-7915 ]
          Hide
          silky mesmeriser added a comment -

          Just wanted to add a short note firstly to confirm that workaround still works with the present state of Ubuntu development which is approaching the final freeze point.

          The other part I wanted to mention is there in that same statement, the ubuntu release schedule is coming up quickly final release on 25th October, no idea where things stand for you or whether it would be an option for you in the development cycle to slip a patched version with the fix out prior to the release or just try and work around it for a time. Either way I wanted to give you a heads up on the status with ubuntu's popularity as a distro I suspect that you are likely to receive a number of support requests on this one come release day.

          Heh, either that or somebody's hardware and software config will throw a fit at the upgrade for unknown reasons, I've been working on testing most of the betas though and the only other issue I've had affect second life was with the netfilter/iptables upgrades not too surprising given SL's reliance on a complex combination of protocols and dependence on multiple services, content providers and distribution systems to have everything working 100% what with the sims, caps/web services, voice, s3/cloudfront for maps not to mention arbitrary third party content providers for media SL tends to be very reliable at finding and highlighting any weakness in the local network stack or routing/reachability issues for sure.

          Anyway, I guess you may already have been tracking the release schedule yourselves but in case you wern't just wanted to update you, link bellow has the complete timetable if it is of any use to you.
          https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule

          Show
          silky mesmeriser added a comment - Just wanted to add a short note firstly to confirm that workaround still works with the present state of Ubuntu development which is approaching the final freeze point. The other part I wanted to mention is there in that same statement, the ubuntu release schedule is coming up quickly final release on 25th October, no idea where things stand for you or whether it would be an option for you in the development cycle to slip a patched version with the fix out prior to the release or just try and work around it for a time. Either way I wanted to give you a heads up on the status with ubuntu's popularity as a distro I suspect that you are likely to receive a number of support requests on this one come release day. Heh, either that or somebody's hardware and software config will throw a fit at the upgrade for unknown reasons, I've been working on testing most of the betas though and the only other issue I've had affect second life was with the netfilter/iptables upgrades not too surprising given SL's reliance on a complex combination of protocols and dependence on multiple services, content providers and distribution systems to have everything working 100% what with the sims, caps/web services, voice, s3/cloudfront for maps not to mention arbitrary third party content providers for media SL tends to be very reliable at finding and highlighting any weakness in the local network stack or routing/reachability issues for sure. Anyway, I guess you may already have been tracking the release schedule yourselves but in case you wern't just wanted to update you, link bellow has the complete timetable if it is of any use to you. https://wiki.ubuntu.com/QuantalQuetzal/ReleaseSchedule
          Hide
          Whirly Fizzle added a comment -

          Thanks Silky!

          Show
          Whirly Fizzle added a comment - Thanks Silky!
          Whirly Fizzle made changes -
          Link This issue is related to FIRE-8002 [ FIRE-8002 ]
          Whirly Fizzle made changes -
          Link This issue is duplicated by FIRE-8002 [ FIRE-8002 ]
          Hide
          Whirly Fizzle added a comment -

          Mister found on FIRE-8002 that Ubuntu 12.10 is also affected on the 4.2.2 release but runs fine on the 4.3.0 builds containing the fontconfig fix.

          On Ubuntu 12.10 however, there is no "Assertion `result != ((void *)0)' failed " error message in logs when it crashes.

          Show
          Whirly Fizzle added a comment - Mister found on FIRE-8002 that Ubuntu 12.10 is also affected on the 4.2.2 release but runs fine on the 4.3.0 builds containing the fontconfig fix. On Ubuntu 12.10 however, there is no "Assertion `result != ((void *)0)' failed " error message in logs when it crashes.
          Mister Acacia made changes -
          Link This issue is related to FIRE-8132 [ FIRE-8132 ]
          Whirly Fizzle made changes -
          Link This issue is duplicated by FIRE-8132 [ FIRE-8132 ]
          Whirly Fizzle made changes -
          Link This issue is related to FIRE-8132 [ FIRE-8132 ]
          Whirly Fizzle made changes -
          Status Resolved [ 5 ] Ready for QA [ 10001 ]
          Whirly Fizzle made changes -
          Status Ready for QA [ 10001 ] In QA [ 10002 ]
          Whirly Fizzle made changes -
          Status In QA [ 10002 ] Passed QA [ 10003 ]
          Whirly Fizzle made changes -
          Link This issue is related to SUP-11082 [ SUP-11082 ]
          Whirly Fizzle made changes -
          Link This issue is related to SUP-11090 [ SUP-11090 ]
          Hide
          Maika Alice Dragon added a comment -

          I'm still a new to using Ubuntu (12.04 or 12.10), so I may not have done everything/or right, but I followed the terminal commands given by hickbrick.sleaford to add the libs, well it fixes the no settings, and throws me some new ones. Also on a new install sometimes it will run out of the box no errors, but this makes no since to me.

          Show
          Maika Alice Dragon added a comment - I'm still a new to using Ubuntu (12.04 or 12.10), so I may not have done everything/or right, but I followed the terminal commands given by hickbrick.sleaford to add the libs, well it fixes the no settings, and throws me some new ones. Also on a new install sometimes it will run out of the box no errors, but this makes no since to me.
          Hide
          Whirly Fizzle added a comment -

          Maika, Please can you give more details of whats going wrong? You are probably best to file a new JIRA issue for this as this bug is now fixed.
          See http://wiki.phoenixviewer.com/file_a_jira

          Show
          Whirly Fizzle added a comment - Maika, Please can you give more details of whats going wrong? You are probably best to file a new JIRA issue for this as this bug is now fixed. See http://wiki.phoenixviewer.com/file_a_jira
          Hide
          Maika Alice Dragon added a comment -

          I really don't understand how to explain it, but this is what I get in the terminal wehrn I run the shell script 'firestorm' in terminal.

          Show
          Maika Alice Dragon added a comment - I really don't understand how to explain it, but this is what I get in the terminal wehrn I run the shell script 'firestorm' in terminal.
          Maika Alice Dragon made changes -
          Hide
          Whirly Fizzle added a comment -

          Maika, please can you file a new JIRA issue following the link above and include your log files after trying to launch the viewer. Instructions on where to find your logs folder are also on the above link.

          Show
          Whirly Fizzle added a comment - Maika, please can you file a new JIRA issue following the link above and include your log files after trying to launch the viewer. Instructions on where to find your logs folder are also on the above link.
          Whirly Fizzle made changes -
          Link This issue is related to FIRE-11513 [ FIRE-11513 ]

            People

            • Assignee:
              Nicky
              Reporter:
              Sythos
            • Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: