Hi
i have updated chrome 125.0.6422.61 (64bit and 32) portable under w10 64bit and w11 64bit
and i have a problem ,only with this update , save as pdf doesn't work
error print preview failed
might someone give a test?
thanks
You are here
[Fixed] Chrome Portable 125.x Print Preview + Save as PDF fail on Win 10 22H2
May 19, 2024 - 10:45am
#1
[Fixed] Chrome Portable 125.x Print Preview + Save as PDF fail on Win 10 22H2
Visit the Community page
Join our forums
Subscribe to our email newsletter
Subscribe with RSS
Follow us on Facebook
Follow us on LinkedIn
Follow us on Twitter
Follow us on Mastodon
Follow us on BlueSky
Looks like it's related to Chome, not the Portablization Process.
To be sure → Within a sandbox try running this .exe ↓↓
X:\***\PortableApps\GoogleChromePortable\App\Chrome-bin\ Chrome.exeIf related to Chromium/Chrome itself, then you should report the bug to the originalc developers!
“My brain is only a receiver, in the Universe there is a core from which we obtain knowledge, strength and inspiration. I have not penetrated into the secrets of this core, but I know that it exists.”
― Nikola Tesla ―
Hi
well ,let's wait an updated by google
thanks
I can confirm this issue on both the 32-bit and 64-bit stable channel portable builds. I am able to print preview on an installed 64-bit build on the same machine. You can add --disable-print-preview to the command line starting to get around this but this won't allow you to use the built in Save as PDF as it bypasses the whole thing in Chrome.
Sometimes, the impossible can become possible, if you're awesome!
hi
do you mean in the GoogleChromePortable.ini under AdditionalParameters= ?
have I to add AdditionalParameters=--disable-print-preview ?
but weird on some systems , the installation version works
I have searched about recent issues but i haven't found any issues reported to google
thanks
hi John
google has released 125.0.6422.77 and even the portable version
but ithey should fix the bug ,but seems to be still buggy
but is still present?
thanks John
It's still present. It's likely that Chrome is now expecting something locally like another registry key. I'll have to look into it.
Sometimes, the impossible can become possible, if you're awesome!
Yeah, I've got the same problem. I hope Google updates chrome soon.
https://issues.chromium.org/issues/339994760
So, how do I invoke portable Chrome with this startup option?
--disable-features=PrintCompositorLPAC
I have print preview working by starting Portable Chrome via this bat file.
d:\PortableApp\Portableapps\GoogleChromePortable\GoogleChromePortable.exe --disable-features=PrintCompositorLPAC
Your Portable App directory may be different...
however still with the portable version update is not working..
Google Chrome Portable 125.0.6422.113 Stable
maybe it is a problem due to the portable version
in the normal version works previews
hi
yes , I agree , i have tried the normal version and it works
i guess it's related to the portable version too
and I think John is digging to fix it
thanks
The workaround for right now is to create a GoogleChromePortable.ini file within the same directory as GoogleChromePortable.exe and put the following in it:
If you're using an existing INI for parameters, you can just adjust that setting within.
Sometimes, the impossible can become possible, if you're awesome!
But the greater issue is it sounds like hey decided to gradually block any attempt to portabilize Chrome (comment #35):
Just wanted to comment on that response from Chrome dev.
Software should help people with what they need/want to do, not restrict people within unnecessary boundaries.
Such restrictions as in comment #35 are an assault on freedom...
This is fixed in today's release. The launcher will automatically add --disable-features=PrintCompositorLPAC to the command line parameters if not already present. I added code to handle combining with other --disable-features= switches if you're using them in AdditionalParameters or passed via the command line to the launcher.
Sometimes, the impossible can become possible, if you're awesome!
This fixes the symptom but not the problem, because I don't think any of us knows what is the downside of disabling this.
I've ran a text search for both PrintCompositorLPAC and disable-features in the portableapps' folder and sub-folders and found nothing, so how did you actually do it?
Is there a way to run without it to see if maybe they just fixed it on their side?
It's built into the launcher itself. Chrome Portable's launcher source is available from the app's homepage unlike Firefox where it's included. You can run it with the v125 launcher to test if it's fixed. Or run directly in local mode.
Sometimes, the impossible can become possible, if you're awesome!
GoogleChromePortable64\App\Chrome-bin\chrome.exe does fail to print, but I ran it through Sandboxie which could have affected the test.
In the bottom of https://portableapps.com/apps/internet/google-chrome-portable-64 there's a source link to the general PortableApps.com Launcher, which was updated before the new Chrome was released.
Meanwhile, how to find previous versions in general? I've tried in SourceForge but it wasn't updated in over a decade.
Will you consider adding a custom command line parameter like --avoid-disable-print-preview?
In your copy, check the Other\Source directory. It has a file called ReadmeAndSource.txt with a link that points here: https://sourceforge.net/projects/portableapps/files/Source/Google%20Chro...
It doesn't use the PA.c Launcher. It uses a custom launcher like Firefox, etc. I'd inadvertently left the box checked to show PA.c Launcher in the source links. I've updated it and fixed the link.
I'm not planning to add a command line switch but that could change. It will likely change when I update Google Chrome Portable to use PA.c Launcher now that things like password saving no longer work.
Sometimes, the impossible can become possible, if you're awesome!
hi John
first thank you so much
but i have through it was a chrome issue and not a the portable version issue
thanks again
The base app has an issue where it won't work outside of expected install directories with specific permissions. This affects more than just portable users. The current workaround is to disable the print compositor's sandbox which is what the portable version now does. You're welcome
Sometimes, the impossible can become possible, if you're awesome!