if no one has the the same problem, maybe someone does already have a working thinapp of Firefox 51.0.1;
is it possible to offer me a downloadlink for that entire thinapp project of the working entrypoints?
There are some known issues with recent versions of Firefox that automatically downloads the latest update when launching for the first time. Due to this change in functionality, launching the ThinApp also starts downloading the updates into sandbox that causes issues. The automatic download must be disabled to fix the issue.
We have a working version of Firefox 50.1, please download the ThinApp project folders here:
Please execute the build.bat to generate the bin folder with ThinApp executables. Also, make sure to delete any existing sandbox before testing it out.
thanks for your reply.
The thinapp of the download you offered, does indeed work.
The steps we normally take with making a new thinapp, which did produce a working thinapp of Firefox until version 50, are:
- Install Firefox (without Maintenance Service)
- Launch Firefox
- Don't import bookmarks
- Uncheck Default browser-check
- Uncheck Update Addons automatically
- Make the homepage the intranetpage
- Uncheck Enable Firefox Health Report
- Uncheck Enable Crash Reporter
- Select Never check for updates
- Uncheck Automatically update search engines
- Show the menu bar
- Some adjustments to userChrome.css and prefs.js
- Remove sandbox
- Start thinapp (on a clean machine)
But with a completely standard install of 51.0.1 (and 50.1), without starting firefox before the postscan, and without any other adjustments, we encounter the same issue in the thinapp-build, the white screen (after shortly seeing the Checking Compatibility Addons screen).
Is modification of ini-files and/or txt-files necessary before building?
There are some known issues with the other latest versions of Firefox. As a workaround/for time being, please use the 50.1 version that i shared.
OK, thanks Lakshman.
No adjustments are possible now. Even just starting up and closing Firefox (with RemoveSandboxOnStart=1) results in a white screen after sbmerge & build.
We'll wait for better versions and keep using 49.
If there are any ideas about solving the issues, please let us know in this thread.
Any development on this?
We are on the Firefox ESR releases, and this month marks the release of ESR 52.0, which now we're faced with the exact same issue.
You can have my project, please contact me privately.
It's nothing really exciting though, but maybe you can extract some details from it you can use.
Which version of Firefox is your project based on?
For me, 52.0.2 is the last version which works. 53.x doesn't work for me anymore, neither does beta (54.x). Oddly enough, a Nightly (55.x) works again. Maybe I'll try ESR too, see how that goes.
The symptoms are that the browser starts and shows its GUI. I can also open the preferences and all that, but closing tabs is flakey at best. Trying to load URLs doesn't work either. Closing the application sometimes works, usually I have to kill it. Weird stuff.
My captures are nothing exciting. Just a pre and post, some cleanup and ExternalDLLs=ucrtbase.dll in package.ini. And then it basically works. I do some other stuff too, but that's pretty much implementation details to make it usable in our corporate environment. They're not needed to get the base package to work: I include a set of mandatory settings, I add a VBS script to copy a default profile, install (and if required, remove) some standard extensions into that profile, and install a couple of certificates into the mozilla certificate store (which is also in that profile). I redirect the mozilla profile to the user home directory instead of leaving it take up space in the roaming profile.
[Edit]Sadly, ESR (52.1.1) doesn't work (anymore?) either.
Same problem. White Screen.
I am also having the same issue with Firefox versions upwards of 49.0. I did disable automatic updates during installation but still got the error mentioned above.
Please could you re-provide your working Thinapp project folders?
Still the same issue with 55.0.3 (and every previous version up to 47) here.
Tried everything, installing and/or building on base image and/or full image, with no or some adjustments during install and/or building,
(ExternalDLLs=ucrtbase.dll is necessary, tried it with comctl32.dll because that one came up in a trace file), and so on and so on...
Nothing works. Not even a white screen now but even a processkill after startup.
I'm giving up.
If anyone solves it, please contact me at firstname.lastname@example.org
I've also moved on from this.
I suspect the issue might have something to do with how later versions of Firefox sandbox child processes. I recently got a Chrome Thinapp package working by disabling the sandbox with a launch parameter. The users receive an annoying message but at least the package is stable. I've not looked into whether this is possible with Firefox but I imagine it could be.
One of VMware's USPs of Thinapp is that it can supposedly virtualise any browser. So running into these issues without any vendor support is very disappointing.
aah the --no sandbox message in Chrome is annoying indeed! but a necessary parameter to get the thinapp working.
tried a couple of Opera thinapps as well. the latest, 48, does not work. 43 is really really fast but is not stable, crashes once in a while.
so i'll probably will put Chrome in production as well in our organization. that is, if the organization OK's the annoying message.
and yes, disappointing results from browser thinapps and support on it.
if you'll ever find a solution to the sandbox (and network location) message in Chrome...