Just got my new work laptop and whacked 4.1 GNOME Edition on.

Everything is working amaazing including the rotation of the screen when in tablet mode (with installation of one piece of repo software).

When I launch Vivaldi I get this screen and can't do anything with it.

When I launch Chrome I get this window and can't do anything either.

Firefox works fine, everything else is perfect.

Inxi output for reference:

System:
  Host: justin-laptop Kernel: 5.4.12-144.current x86_64 bits: 64 
  Desktop: Gnome 3.34.3 Distro: Solus 4.1 
Machine:
  Type: Convertible System: Dell product: Inspiron 7391 2n1 v: N/A 
  serial: <filter> 
  Mobo: Dell model: 0HCF7W v: A00 serial: <filter> UEFI: Dell v: 1.3.1 
  date: 11/28/2019 
Battery:
  ID-1: BAT0 charge: 14.7 Wh condition: 43.0/45.0 Wh (96%) 
CPU:
  Topology: Quad Core model: Intel Core i5-10210U bits: 64 type: MT MCP 
  L2 cache: 6144 KiB 
  Speed: 800 MHz min/max: 400/4200 MHz Core speeds (MHz): 1: 800 2: 800 
  3: 800 4: 800 5: 800 6: 800 7: 800 8: 800 
Graphics:
  Device-1: Intel UHD Graphics driver: i915 v: kernel 
  Display: x11 server: X.Org 1.20.6 driver: intel 
  unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz 
  OpenGL: renderer: Mesa DRI Intel UHD Graphics (Comet Lake 3x8 GT2) 
  v: 4.6 Mesa 19.3.2 
Audio:
  Device-1: Intel driver: snd_hda_intel 
  Sound Server: ALSA v: k5.4.12-144.current 
Network:
  Device-1: Intel Wireless-AC 9462 driver: iwlwifi 
  IF: wlp0s20f3 state: up mac: <filter> 
Drives:
  Local Storage: total: 476.94 GiB used: 8.68 GiB (1.8%) 
  ID-1: /dev/nvme0n1 model: PC SN520 NVMe WDC 512GB size: 476.94 GiB 
Partition:
  ID-1: / size: 464.31 GiB used: 8.68 GiB (1.9%) fs: ext4 
  dev: /dev/nvme0n1p3 
  ID-2: swap-1 size: 3.73 GiB used: 0 KiB (0.0%) fs: swap 
  dev: /dev/nvme0n1p2 
Sensors:
  System Temperatures: cpu: 38.0 C mobo: N/A 
  Fan Speeds (RPM): cpu: 0 
Info:
  Processes: 271 Uptime: 1d 7h 33m Memory: 7.57 GiB used: 1.49 GiB (19.7%) 
  Shell: bash inxi: 3.0.37

Anyone got any ideas? It's obviously limited to Chromium based browsers but I'm lost.

    What does launching thru the terminal tell you? I would expect to see some red lettering there.
    Basic clean caches/history/cookies?
    You are not even getting a 'cannot connect' page...like it's aborting upon launch. Strange one.

      I'm not a Vivaldi user. Installed it trying to help somehow.

      Judging from the first screenshot (with Vivaldi), you have vivaldi-stable installed. The grey full-screen window with Vivaldi logo is briefly displayed here too, - exactly as on your screenshot, - and immediately gets covered by the regular Vivaldi window, with default red theme.

      1. I do autologin and use Firefox, so login keyring remains locked. Vivaldi, like Chromium, wants to have login keyring unlocked. So the regular red window is immediately greyed out, and the dialog requesting the password to unlock login keyring is presented.

        Briefly: Grey window with V logo --> Regular red window --> Password request dialog.

        If I unlock login keyring before launching vivaldi-stable, the password is not requested. The launch sequence reduces to: grey window with V logo --> regular red window. vivaldi-stable is operational.

        So you could try to unlock the login keyring before starting Vivaldi. seahorse is a handy tool for doing it. Moreover, with seahorse login keyring password may be removed, so it will never be requested. Neither by Vivaldi, nor by Chromium. Less secure, more convenient.

      2. Another thing. Differently from vivaldi-stable, vivaldi-snapshot does NOT present the initial grey full-screen window with V logo, and does NOT require to unlock the login keyring. It immediately opens a regular, working, red-themed Vivaldi window.

        Maybe vivaldi-snapshot will work better than vivaldi-stable.

      Just a shot in a dark.

        just hell of a great reply. I read it a couple times.
        I've installed and effortlessly used vivaldi-stable many times. With none of Justin's problems.
        I do NOT autologin and I do use FF. But once I give my login password the keyring becomes unlocked? I find this fascinating if true, which I'm sure it is.
        Great memory for the colors/screens here...I customize that orange/red & grey into the trashbin as soon as it launches the first time.
        I didn't know keyrings had that control, but I know nothing about keyrings.

            Justin
            Could you report any error messages?

            Run in the terminal:

            /usr/bin/google-chrome-stable %U

            /usr/bin/vivaldi-stable --new-window

                brent These are first runs, not used at all so no cookies/etc to clean.

                Vivalid:

                → $ vivaldi-stable 
[7596:7596:0208/145344.645983:ERROR:chrome_content_client.cc(345)] Failed to locate and load the component updated flash plugin.
[7628:7628:0208/145344.717621:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process.
[7628:7628:0208/145344.741551:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
[7630:7643:0208/145344.776314:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018
[7596:7596:0208/145345.561528:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: The message port closed before a response was received.", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)
[7596:7596:0208/145345.561654:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: The message port closed before a response was received.", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)
[7596:7596:0208/145345.563046:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: The message port closed before a response was received.", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)

                Chrome:

                 → $ google-chrome-stable 
[1:1:0208/145441.219117:ERROR:chrome_content_client.cc(323)] Failed to locate and load the component updated flash plugin.
[8108:8108:0208/145441.396264:ERROR:chrome_content_client.cc(323)] Failed to locate and load the component updated flash plugin.
[8141:8141:0208/145441.459617:ERROR:sandbox_linux.cc(374)] InitializeSandbox() called with multiple threads in process gpu-process.
[8145:8154:0208/145441.775423:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018
[8348] Unable to check extensions updates: 403 Client Error: Forbidden for url: https://extensions.gnome.org/update-info/?shell_version=3.34.3

                Any clues on what to clear?

                just I'm not using auto login so gdm unlocks my keyring when I login. I'll try vivaldi-snapshot and report back.

                brent I've used Vivladi and Chrome on many other devices on Solus without issue, only this laptop seems to be having the issue. It's very odd and makes me think it's to do with hardware. Or GNOME desktop as I don't use it on other devices, usually Budgie or Plasma.

                cantalupo555 See above.

                PS Thanks for all the replies.

                          Justin These are first runs, not used at all so no cookies/etc to clean.

                          Vivalid:...

                          Starting vivaldi-stable from terminal, I can see only one difference between your and mine startups.

                          • messages marked with --OK--> are identical for both startups
                          • messages marked with --++--> are present for me only
                          • the message marked with --??--> is present for you only

                          Vivaldi-stable Gnome @Justin (yours):

                           $ vivaldi-stable
--OK-->  [7596:7596:0208/145344.645983:ERROR:chrome_content_client.cc(345)] Failed to locate and load the component updated flash plugin.
--OK-->  [7628:7628:0208/145344.717621:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process.
--OK-->  [7628:7628:0208/145344.741551:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
--??-->  [7630:7643:0208/145344.776314:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018
--OK-->  [7596:7596:0208/145345.561528:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: The message port closed before a response was received.", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)
--OK-->  [7596:7596:0208/145345.561654:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: The message port closed before a response was received.", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)
--OK-->  [7596:7596:0208/145345.563046:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: The message port closed before a response was received.", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)

                          Vivaldi-stable Gnome @just (mine):

                          $ vivaldi-stable
--++-->  Proprietary media' support is not installed. Fix this by running:
    /usr/share/vivaldi-stable/update-ffmpeg
--++-->  The Widevine CDM is not installed. Fix this by running:
    /usr/share/vivaldi-stable/update-widevine
--OK-->  [1917:1917:0208/111127.940372:ERROR:chrome_content_client.cc(345)] Failed to locate and load the component updated flash plugin.
--OK-->  [1948:1948:0208/111128.617231:ERROR:sandbox_linux.cc(372)] InitializeSandbox() called with multiple threads in process gpu-process.
--OK-->  [1948:1948:0208/111129.043234:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command
--OK-->  [1917:1917:0208/111131.178858:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: The message port closed before a response was received.", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)
--OK-->  [1917:1917:0208/111131.178952:ERROR:CONSOLE(0)] "Unchecked runtime.lastError: The message port closed before a response was received.", source: chrome-extension://mpognobbkildjkofajifpdfhcoklimli/browser.html (0)
--++-->  [2083] Unable to check extensions updates: 403 Client Error: Forbidden for url: https://extensions.gnome.org/update-info/?shell_version=3.34.3
$

                          This error is returned for you only, and not for me:

                          --??-->  [7630:7643:0208/145344.776314:ERROR:nss_util.cc(283)] After loading Root Certs, loaded==false: NSS error code: -8018

                          It says nothing for me.

                          Though I can't reproduce the error, try to launch vivaldi-stable with --disable-test-root-certs startup switch:

                          vivaldi-stable --disable-test-root-certs

                          Not sure that it could be useful and will help, but it seems to be the only Chromium startup switch, somehow related to "Root Certs". Adding --disable-test-root-certs doesn't make any difference here - vivaldi-stable starts normally.

                          The description of --disable-test-root-certs may be found at List of Chromium Command Line Switches page. There are other certificates-related switches, but they seem to be unrelated to "Root Certs". The amount of available startup switches is huge, probably some hundreds. It makes hard to find a useful info.

                              just Thanks for the thorough research. I ran vivaldi-stable --disable-test-root-certs but still got the same error.

                              I did an eopkg check but got no issues that would relate.

                              I even did a re-install of ca-certs but no luck. I've noticed that the issue also happens in Spotify which I'm assuming is the same issue.

                                watch it be something so magnificently simple we didn't think of🙂

                                • just replied to this.

                                  brent ...something so magnificently simple...

                                  That's for sure!

                                    DuckDuckGo-ing the web for "vivaldi won't open" and "vivaldi won't start" shows that some people were able to start Vivaldi on Linux:

                                    • either by deleting some specific folders from user's Vivaldi profile
                                    • or by deleting profile completely

                                    Cautious "removal":

                                    mv ~/.config/vivaldi ~/.config/vivaldi-deleted

                                    Real removal:

                                    rm -r ~/.config/vivaldi

                                    And a really stupid thing. Is it possible that Vivaldi doesn't start because on first run it opens in a maximized window? Run it for the first time from terminal in a normal, not maximized window:

                                    vivaldi-stable --window-size=800,600

                                      just I love a good mystery too (sometimes they drive you crazy), and have search engined--like most here---quite a bit on people's behalf. I know they sure have for me.
                                      Still, good research,
                                      maybe dump all of config?
                                      firefox ALWAYS launches for me on minimal screen...maybe there is something to that.
                                      the blank is still like ip address blocked (I know it's not, but similar) or some weird dns thing or rogue extension or odd setting....if he is using a VM that's another vivaldi wrinke maybe.
                                      or the simplest trick in the book: sudo eopkg rm vivaldi-stable? reboot? install again? reboot?
                                      Of course maybe @Justin is right and it's hardware since all his other devices run vivavldi without error. so an incompatibility to something in the inxi above? or something physically on the way out on the board?
                                      I'll be happy when this one gets the solved tag🙂because my brain hurts

                                          just I've tried removing the config directory for Vivaldi as well as the cache directory several times but tried again with the 800x600 window command but the result is the same.

                                          It's odd as I can click on spaces where I know window items are and get the menu, but it's always blank.

                                          Any time I click on an item within Vivaldi this repeats [3611:3611:0209/160430.254181:ERROR:buffer_manager.cc(488)] [.DisplayCompositor]GL ERROR :GL_INVALID_OPERATION : glBufferData: <- error from previous GL command

                                          So it's got something to do maybe with mesalib which I believe provides GL. Let me know if I'm incorrect on this anyone.

                                            brent or something physically on the way out on the board

                                            I hope not it's a brand new laptop.

                                              OK, after looking into this more, running these works..

                                              vivaldi-stable --disable-gpu --disable-software-rasterizer

                                              google-chrome-stable --disable-gpu --disable-software-rasterizer

                                              I'd be interested to see if anyone knows why it only works with these. I noticed issues with playback in GNOME MPV too so I'm assuming it's GPU acceleration related.

                                              I'm off to find a workaround for MPV.

                                              This is partially solved by a workaround but a permanent solution is desired. Thanks for everyone's help.

                                              Edit: Spotify works with spotify --disable-gpu.

                                                EbonJaeger I highly doubt it's been blacklisted, I'd say it's an issue with an updated GL or something and Intel UHD Graphics chips, perhaps as mine is so new it's not properly supported yet.

                                                  The 'too-new-to-support' theory is sound.And the 'blacklisted' theory seems that way, too. In just cursory reading (which I'm sure you've done) clues allegedly exist in about:gpu and chrome://gpu.