Capture Full Page don't work after update
-
@Pathduck Thank you very much for your help, the video is very helpful!
How do you make the video? Do you need a special software (commercial/freeware) to record this video? I know, it's not the purpose of this forum to help for creating videos, but it could help me in some situations to better explain the problem. Is there a tutorial you could recommend me?When I installed it on any folder in
D:\Apps\
orE:\Apps\
, then everything was working, except the Full Page captures. I will try to share a ProcMon capture file, I don't know how to do it, because it will be a quite big file I guess. -
@cpuheater said in Capture Full Page don't work after update:
How do you make the video? Do you need a special software (commercial/freeware) to record this video?
I use ShareX, it's free, easy to use and creates small but great-looking videos.
https://getsharex.comthen everything was working, except the Full Page captures.
I have no idea why Full Page won't work for you.
Sometimes it might have trouble for very long pages, especially if they load images on-demand (while scrolling) - you might need to scroll the whole way down before taking the image. But that's not the case for the page I tested with.I will try to share a ProcMon capture file, I don't know how to do it, because it will be a quite big file I guess.
OK, make sure you try to capture only while actually reproducing the issue to get a small file. You can toggle capture with
Ctrl+E
, just toggle it on, go to Vivaldi and reproduce, go back and toggle it off.Make sure when you save All Events in PML format.
Then zip the file, and share it somewhere. I like this service for quick sharing:
https://wormhole.app -
@DoctorG Thank you for your help.
I installed the version 6.9.3447.48 on 2 identical PCs multiple times in different empty folders on driveC:
,D:
andE:
, but only the installation that I made in folderC:\Apps\
was working correctly with the Full Page capture. I did the installations always with the same settings during installation, then when Vivaldi started the first time, I left the default settings and skipped the bookmark import.Could be some update broke your installation, you could try to re-install 6.9.3447.48.
I did always a fresh installation in an empty folder as standalone like this:
The folderE:\Apps\
already existed and the folderVivaldi.6.9.3447.48.x64
was created by the installer. -
@cpuheater Can you please check in Settings → Webpages → Image Capture → Capture Storage Folder which path is in the field?
Has the folder correct access/write rights for the user who runs Vivaldi? -
@DoctorG The Capture Storage Folder is
C:\Users\<profilename>\Pictures\Vivaldi Captures
. In this folder I have Full Control. Vivaldi is not even trying to access this folder, I checked with Sysinternals Process Monitor, I will repeat the step and record the Process Monitor log and post the log file. Yesterday I tried also to capture Full Page to clipboard, but it was also not working. -
@Pathduck Thank you for your help.
I use ShareX, it's free, easy to use and creates small but great-looking videos.
https://getsharex.comI downloaded ShareX almost 2 years ago, but I was using it only a few times for capturing windows and annotate them, it's much easier than with other screen capturing tools. I didn't know about this fantastic functionality to easily record great-looking videos, thanks for that!
In the meantime I downloaded the new version of Vivaldi 6.9.3447.51, but the behavior is the same. Once I tried to install it in a new folder in
D:\Apps\
, the Full Page capture didn't work, then I re-installed again in the same folder, then the capture was working. Then I tried to do the same steps onE:\Apps\
, but without success, I tried to re-install it at least 4 times on this drive.Now I'm just wondering, if it's the drive E: that makes a difference for the installation of Vivaldi 6.8.x or 6.9.x. Till now I never had problems with this drive, but it's the only drive that is encrypted using VeraCrypt. I updated VeraCrypt to the latest stable version 1.26.15 and checked the drive, but everything is OK.
To isolate the problem, I did the following tests:
- I created a temporary VeraCrypt container file located on drive
D:
, formatted it using NTFS with default cluster size, mounted it as driveH:
, installed Vivaldi in folderH:\Apps\Vivaldi.6.9.3447.51.x64
and tried the Full Page capture -> Not working! - I dismounted the VeraCrypt drive. Created a drive
H:
usingsubst H: D:\Apps
, this drive is not accessible in Explorer, but I could successfully install Vivaldi in folderH:\Apps\Vivaldi.6.9.3447.51.x64
. Then from the Command Prompt I could start Vivaldi in the folderH:\Apps\Vivaldi.6.9.3447.51.x64\Application
and try the Full Page capture -> Working!
Conclusion:
It seems the Full Page capture problem is not related with the installation path, but the installation drive type. I tested to mount the VeraCrypt encrypted container as removable medium or fixed medium, this makes no difference.Maybe somebody have a VeraCrypt encrypted drive and could try to install Vivaldi as Standalone on this drive to test the Full Page capture?
- I created a temporary VeraCrypt container file located on drive
-
@cpuheater said in Capture Full Page don't work after update:
Maybe somebody have a VeraCrypt encrypted drive and could try to install Vivaldi as Standalone on this drive to test the Full Page capture?
Sadly i do not have such encrypted drive/partition, i do not want to change my Windows office PC.
But i try it later on my Linux PC with Veracrypt. -
@cpuheater said in Capture Full Page don't work after update:
Till now I never had problems with this drive, but it's the only drive that is encrypted using VeraCrypt. I updated VeraCrypt to the latest stable version 1.26.15 and checked the drive, but everything is OK.
There's always that one small thing that you think would not affect anything and you forget to inform about
I tested:
- Installed VeraCrypt as portable
- Created a new 10GB
f:\temp\VeraCrypt
and mounted it asI:
- Installed Vivaldi 6.9 Stable in
i:\Apps\Vivaldi-test1\
- Ran Vivaldi and tried Page Capture, it failed.
- No output in ProcMon as well, no file activity to the
Vivaldi Captures
folder on C: - Tried the same with
i:\Vivaldi-Captures\
in case the location or the space made a difference - it didn't. - Tried installing/copying over older releases to the same folder and tried the same to find a possible regression point.
Seems to have started back in 6.8 - it works in 6.0, 6.6 and 6.7 when doing the same.
The really strange thing is also that when I try copying the
Vivaldi-test1
folder over to another drive - it still fails - I have no idea why.We have at least one regular forumer who I know uses Vivaldi on a VeraCrypt drive but I believe they don't use Vivaldi Capture but FastStone.
Maybe @Pesala could do a quick capture test?I have no idea why capture would fail when running Vivaldi from an encrypted drive - a process is a process and I see zero difference in the binaries Application folder.
I guess you should report a bug.
Maybe @DoctorG could do a verify as well.Please read:
carefully and report the bug to Vivaldi bugtracker.
Please also post the bug-number (VB-#) here after reporting -
@Pathduck said in Capture Full Page don't work after update:
Maybe @Pesala could do a quick capture test?
I can confirm on Vivaldi Snapshot 6.10.3483.4.
11 Gigabyte Veracrypt drive mounted as drive V:
-
@Pesala said in Capture Full Page don't work after update:
I can confirm on Vivaldi Snapshot 6.10.3483.4.
Please create a bug report for Vivaldi bug tracker.
-
@DoctorG Done:
VB-110128 Capture Full Page Fails if Vivaldi installed on Veracrypt drive
-
@Pesala Thanks for your test!
I confirmed bug tracker entry now. -
@TyrionLannister
I try to ask internally in dev team chat.Ah, @Pathduck already is in discussion with dev team. -
@Pathduck Thank you very much for your great support, I really appreciate this!
I have an update to this problem:
I did some more tests to try to understand this behavior. I repeated the test to install the new version of Vivaldi 6.9.3447.51 as Standalone, the exact same way as before, but I tested the following situations on a new 32GB USB-stick:- I formatted the USB-stick using NTFS with default cluster size, installed Vivaldi -> Capture works!
- I encrypted this drive using BitLocker -> Capture works!
- I then formatted the USB-stick using exFAT, installed Vivaldi -> Capture failed!
- I then formatted the USB-stick using FAT32, installed Vivaldi -> Capture failed!
Probably the problem is not exclusively related to VeraCrypt encrypted drive, but I still don't understand why the filesystem should make a difference.
-
@cpuheater said in Capture Full Page don't work after update:
I still don't understand why the filesystem should make a difference.
NTFS has user Access Rights. exFAT/FAT32 do not have such security features.
-
@DoctorG Just mention that exFAT/FAT32 aren't case sensitive either. Not sure if NTFS is nowadays or not. Took me awhile to get use to this (case sensitive) when I moved to Linux years ago...
-
-
@cpuheater said in Capture Full Page don't work after update:
@Pathduck Thank you very much for your great support, I really appreciate this!
You're very welcome
Probably the problem is not exclusively related to VeraCrypt encrypted drive, but I still don't understand why the filesystem should make a difference.
I think you're correct in that it's not exclusive to VeraCrypt.
I got digging into this and this rabbit hole goes deepVivaldi is a Chromium browser, and Chromium processes run "sandboxed" for security. One thing the installer does is add special user SIDs to the Application folder that plays a role in this sandboxing.
If these special SIDs are removed, the full-page capture fails, reasons unknown. If the SIDs are added back, full-page capture works. This seems to have started in Vivaldi 6.8/Chr128 and is independent of VeraCrypt.
As long as the file system is NTFS, the installer will apply these SIDs to the Application folder where the exe resides. This also applies on VeraCrypt drives, so it doesn't fully explain the issue, but the symptoms are related and probably caused by the sandboxing.
VeraCrypt drives seem to have default "Everyone=Full Control" permissions, with inheritance. But this does not seem to matter, what matters is the SIDs + the sandboxing. Possibly VeraCrypt's driver is involved as well.
There's a bug report now, and a dev will take a look over the weekend I hope. No idea how easy it is to solve though.
If you're interested in some more technical details I wrote up a doc including some links to Chromium source:
https://docs.google.com/document/d/1ovRymEhJwMCg2CkFQDUqHEMBLGit7hwE5-Y0j0a2FBk/edit?usp=sharingUnfortunately I have not found any workaround to make it work on VeraCrypt, even adding the exact same standard permission an application folder should have on Windows and the capture still fails.
-
@Pathduck Thank you for continuing to investigate on this problem and for digging!
I try to help dig, but my knowledge is limited.The information you provided is very interesting for me, even I don't understand everything, I learned a few things.
Unfortunately I have not found any workaround to make it work on VeraCrypt, even adding the exact same standard permission an application folder should have on Windows and the capture still fails.
I tried also to apply the same permissions to the Vivaldi folder including subfolders on the VeraCrypt drive as on the working Vivaldi Standalone installation folder. -> It's not working (as you mentioned)
I tried to copy the working Standalone installation to the VeraCrypt drive with
robocopy.exe
, using the following arguments:robocopy "D:\Apps\Vivaldi.6.9.3447.51.x64(D)" "E:\Apps\Vivaldi.6.9.3447.51.x64(D)" /COPY:DATSOU /DCOPY:DATE /MIR
I was expecting it copies ALL attributes, security settings, etc., but this test failed too.
-
@cpuheater I found a possible "workaround" but probably not recommended.
A command line argument:
--no-sandbox
Disables the sandbox for all process types that are normally sandboxed. Meant to be used as a browser-level switch for testing purposes only
https://peter.sh/experiments/chromium-command-line-switches/#no-sandboxNot sure about what sandboxing does or how important it is, but it's to do with process security that's all I know.
At least it's more proof that this is related to sandboxing.