So the crash on startup seems to be related to setting permissions. Can you remove your permissions code from your cck2.cfg and see if Firefox starts?
The ""Failed to read the configuration file." usually means something changed internal to Firefox that broke CCK2. Best way to debug is to put a try/catch around CCK2 init and output the error to the console. I'm going to make that the default behavior in the next version. It means Firefox will start without customizations, but at least it will start... Mike On Wed, Mar 14, 2018 at 12:56 PM, James M. Pulver <[email protected]> wrote: > I've tried on Windows as well, and get a "Failed to read the configuration > file." I went through my CCK2 and generated a new version per the web page. > However, now I get "Firefox colsed unexpectedly while starting." > > Any idea how I ought to debug this? > > Thanks, > > -- > James Pulver > CLASSE Computer Group > Cornell University > > On 03/01/2018 03:20 PM, James M. Pulver wrote: > >> I'm trying to use an appimage of Firefox Quantum on EL7. I understand the >> additional complications here. However, is anyone using CCK2 stuff with >> 58.0.2 RR? What directory should I put what CCK2 output files in normally? >> >> Also any hints if you've used the "portable packaging" of appimage where >> I might put them would be appreciated: >> https://bintray.com/probono/AppImages/Firefox >> >> but of course I mostly just want to know with a standalone install where >> I might be expecting to put these files. >> >> Thanks, >> > _______________________________________________ > Enterprise mailing list > [email protected] > https://mail.mozilla.org/listinfo/enterprise > > To unsubscribe from this list, please visit https://mail.mozilla.org/listi > nfo/enterprise or send an email to [email protected] with a > subject of "unsubscribe" >
_______________________________________________ Enterprise mailing list [email protected] https://mail.mozilla.org/listinfo/enterprise To unsubscribe from this list, please visit https://mail.mozilla.org/listinfo/enterprise or send an email to [email protected] with a subject of "unsubscribe"
