Solved "Please wait for Vivaldi to close" message showing up on startup
-
@dhruva023
Hi, I will try to reproduce it with Vivaldi 6.1.3035.111, Vivaldi 6.2.3070.3 (Chromium 116).
My main system is Linux but I will test this on Windows 11.Cheers, mib
-
@mib2berlin
OK, I can reproduce it with 6.1 but cant test with 6.2, I cant install any PWA with 6.2.
I will make some more tests and then report it to the Vivaldi bug tracker.@all
Can anybody test install a PWA with Vivaldi 6.2.3077.3 on Windows 11?
Crash to desktop!Cheers, mib
-
@mib2berlin
Bug reported VB-98860 Please wait popup.
I cant confirm my own reports, we have to wait for a tester/developer to test this report.Cheers, mib
-
@mib2berlin Perhaps dupe of VB-98831 + VB-98505
But i do not have joy to test PWA now. -
@DoctorG
Ah thanks, I glue them together with my own report.
No worries, if you find the time it would be nice.
The popup appears at 6. for me with a Youtube PWA, I tested this with Chromium and there is no popup.
Anyway, have a nice weekend.Cheers, mib
EDIT: New master bug is VB-98505 -
@mib2berlin I confirmed in tracker.
Ugly bug! -
@DoctorG
Yep. I saw it, thanks for testing.Cheers, mib
-
🪲🪲So sad, PWAs not running with enough stability on Vivaldi 6.1 and 6.2.
-
@mib2berlin thanks for opening the bug report and @DoctorG for corroborating and testing.
I have a few Progressive Web Apps. This popup happens constantly when opening a PWA or Vivaldi and one or the other is already launched. Confirmed reproducible with this build:
6.1.3035.204 (Stable channel) (64-bit)
Revision 51ca1a850596be92317db01803f7fee2eed2a324
OS Windows 11 Version 22H2 (Build 22621.1992)I suspect this is something to prevent multiple Vivaldi browser processes from being able to open at the same time, and Vivaldi can't tell the difference between a PWA and a vanilla Vivaldi session. Considering the Vivaldi philosophy on maximum customization one would think this would just be an option to allow for multiple Vivaldi sessions / main processes and that would workaround this issue.
Strange that this seems to be a Vivaldi specific dialog and issue as well, it would seem unless there was any functionality added to Vivaldi (as I just mentioned) Vivaldi should just use the standard Chromium way of doing this, which has no such issue.
But there may be a lot of considerations I'm glossing over, it's not like we can look at the source code so, such speculation is not a choice --it's a necessity lol. Fortunately the developers seem to have great communication and community engagement.
-
@landon
Hi again, Vivaldi only add a user interface layer on top of Chromium but other browser don´t use pure Chromium.
If you start Vivaldi with--disable-vivaldi
you get Chromium.
Can you test this?This is a PWA created in Vivaldi with
--disable-vivaldi
.You can edit your desktop shortcut to make it so, but with
--disable-vivaldi
: -
@mib2berlin Okay, thanks for the suggestion. interesting results when i add
--disable-vivaldi
to a PWA shortcut made with Vivaldi:-
if, and only if Vivaldi or another Vivaldi PWA is already running, then the PWA will launch normally without any "Please wait for Vivaldi to close" dialog.
-
if Vivaldi or another Vivaldi PWA is not already running, then the PWA will not launch, it will fail silently as if the PWA shortcut was not opened.
-
-
@landon
Hm, I can open the PWA anytime, Vivaldi or other PWA running or not.
I have to test this on Windows again, I am on Linuy at moment. -
Hmmm.
Is anyone else here using any flags in (chrome:flags)?
I solved this issue by resetting the following flag to default: #enable-isolated-sandboxed-iframes
-
@pafflick
I've experienced the same issue and tried all the suggestions in this thread and opened a new thread with videos and screenshots and step by steps of this issue.https://forum.vivaldi.net/topic/90892/please-wait-for-vivaldi-to-close-popup-force-startup-issue
Hope this gets addressed soon
-
@joaocastilho
Hi, can you check the flag @glowingfirefly mention?vivaldi://flags/#enable-isolated-sandboxed-iframes
-
@mib2berlin
I explain in my first post that I did try that- it's the default value that comes with a brand new installation even so I never had to change it.