Vivaldi 3.8 doesn't show UI - Ubuntu 21.04
-
I am having trouble with opening and closing vivaldi browser after the upgrade to Ubuntu 21.04 from 20.04. When I open the browser, the window is blank or completely black with no graphics or text. I am not sure what happened during the upgrade process. It is possible that there's some errors in software packages, however, I am not sure exactly what it is.
Any guidance on new APT line to repair the broken vivaldi package or Ubuntu dependencies?
-
Vivaldi 3.8 doesn't work on Ubuntu 21.04
I don't believe it.
-
@gwen-dragon thank you for connecting. The computer is based on linux (debian) amd64.The The RAM is not the issue. I think the GPU graphics is based on NDVIA. I think it is more of Ubuntu OS upgrade to 21.04 is being not compatible with Vivaldi browser. I didn't have a problem with vivaldi when using Ubuntu 20.04. The upgrade problem removed some things needed for vivaldi and other browsers to work. I tried Brave browser to test it on the new upgraded version (21.04). It didn't work either. So far, Firefox is the only browser that works on 21.04. Based on your suggestions, I am unable to open vivaldi window because it is a black screen.
Other than that, I am unable to answer most of your questions. Hope some additional information helps. I will see if Ubuntu offers feedback on this. -
@cdn2020 Let's start with the basics, did you try to reinstall Vivaldi?
-
@npro yes, I did. For some reasons, it didn't work
-
@cdn2020 Allright, if you have
inxi
installed you may post your system info. To do that open a terminal and enter this commandinxi -Fmxxy --no-host && vivaldi-stable --version
then copy the contents and paste it here using the </> button.
-
This post is deleted! -
@cdn2020
Good, but you haven't used the </> button. To do so, edit your post by clicking the 3-dot menu to the rightselect the inxi output and click the </> button
Then click on Submit to finish editing your message.
-
System: Kernel: 5.11.0-17-generic x86_64 bits: 64 compiler: gcc v: 10.2.1 Desktop: GNOME 3.38.4 tk: GTK 3.24.25 wm: gnome-shell dm: GDM3 Distro: Ubuntu 21.04 (Hirsute Hippo) Machine: Type: Unknown System: powerspec product: B616 v: ps serial: <superuser required> Chassis: ps type: 2 v: ps serial: <superuser required> Mobo: Intel model: D945GCNL v: AAD97184-106 serial: <superuser required> BIOS: Intel v: N/A date: N/A Battery: Device-1: hidpp_battery_0 model: Logitech Wireless Mouse M215 2nd Gen serial: 401b-14-85-92-d9 charge: 100% (should be ignored) status: Discharging Device-2: hidpp_battery_1 model: Logitech Wireless Keyboard K330 serial: 4016-b1-53-af-1e charge: 55% (should be ignored) status: Discharging Memory: RAM: total: 1.92 GiB used: 1.46 GiB (75.7%) RAM Report: permissions: Unable to run dmidecode. Root privileges required. CPU: Info: Dual Core model: Intel Core2 Duo E7400 bits: 64 type: MCP arch: Penryn rev: A L2 cache: 3 MiB flags: lm nx pae sse sse2 sse3 ssse3 bogomips: 11170 Speed: 1596 MHz min/max: 1596/2660 MHz Core speeds (MHz): 1: 1596 2: 1596 Graphics: Device-1: Intel 82945G/GZ Integrated Graphics driver: i915 v: kernel bus ID: 00:02.0 chip ID: 8086:2772 Display: wayland server: X.Org 1.21.1.1 compositor: gnome-shell driver: loaded: intel unloaded: fbdev,modesetting,vesa resolution: 1920x1080~60Hz s-dpi: 96 OpenGL: renderer: llvmpipe (LLVM 11.0.1 128 bits) v: 4.5 Mesa 21.0.1 compat-v: 3.1 direct render: Yes Audio: Device-1: Intel NM10/ICH7 Family High Definition Audio driver: snd_hda_intel v: kernel bus ID: 00:1b.0 chip ID: 8086:27d8 Device-2: Ruision UVC Camera type: USB driver: snd-usb-audio,uvcvideo bus ID: 1-1:2 chip ID: fefe:4321 Sound Server: ALSA v: k5.11.0-17-generic Network: Device-1: Realtek RTL8111/8168/8411 PCI Express Gigabit Ethernet vendor: Intel driver: r8169 v: kernel port: 1000 bus ID: 02:00.0 chip ID: 10ec:8168 IF: enp2s0 state: up speed: 1000 Mbps duplex: full mac: 00:1c:c0:81:29:10 Drives: Local Storage: total: 298.09 GiB used: 62.76 GiB (21.1%) ID-1: /dev/sda vendor: Western Digital model: WD3200AAKS-00L9A0 size: 298.09 GiB speed: <unknown> serial: WD-WCAV20792844 temp: 37 C Partition: ID-1: / size: 291.92 GiB used: 62.76 GiB (21.5%) fs: ext4 dev: /dev/sda5 ID-2: /boot/efi size: 511 MiB used: 4 KiB (0.0%) fs: vfat dev: /dev/sda1 Swap: ID-1: swap-1 type: file size: 2 GiB used: 271.1 MiB (13.2%) priority: -2 file: /swapfile Sensors: System Temperatures: cpu: 41.0 C mobo: N/A Fan Speeds (RPM): N/A Info: Processes: 212 Uptime: 2h 41m Init: systemd v: 247 runlevel: 5 Compilers: gcc: N/A Packages: 1801 apt: 1785 snap: 16 Shell: Bash v: 5.1.4 running in: gnome-terminal inxi: 3.3.01 Vivaldi 3.8.2259.42
-
@cdn2020 Excellent, that's a good base for troubleshooting. Can you also post the contents of Vivaldi's installation directory?
ls -l /opt/vivaldi/* -I*??.pak
/edit: But before doing that what messages do you get if you start Vivaldi from inside the terminal?
-
To answer your question: I don't know honestly
-rwxr-xr-x 1 root root 2037688 May 10 20:14 /opt/vivaldi/crashpad_handler -rw-r--r-- 1 root root 1178 May 10 20:14 /opt/vivaldi/features.json -rw-r--r-- 1 root root 10413488 May 10 20:14 /opt/vivaldi/icudtl.dat -rw-r--r-- 1 root root 247760 May 10 20:14 /opt/vivaldi/libEGL.so -rw-r--r-- 1 root root 7117032 May 10 20:14 /opt/vivaldi/libGLESv2.so -rw-r--r-- 1 root root 6460 May 10 20:14 /opt/vivaldi/LICENSE.html -rw-r--r-- 1 root root 4672 May 10 20:14 /opt/vivaldi/product_logo_128.png -rw-r--r-- 1 root root 520 May 10 20:14 /opt/vivaldi/product_logo_16.png -rw-r--r-- 1 root root 527 May 10 20:14 /opt/vivaldi/product_logo_22.png -rw-r--r-- 1 root root 573 May 10 20:14 /opt/vivaldi/product_logo_24.png -rw-r--r-- 1 root root 9421 May 10 20:14 /opt/vivaldi/product_logo_256.png -rw-r--r-- 1 root root 1165 May 10 20:14 /opt/vivaldi/product_logo_32.png -rw-r--r-- 1 root root 1602 May 10 20:14 /opt/vivaldi/product_logo_32.xpm -rw-r--r-- 1 root root 1690 May 10 20:14 /opt/vivaldi/product_logo_48.png -rw-r--r-- 1 root root 2274 May 10 20:14 /opt/vivaldi/product_logo_64.png -rw-r--r-- 1 root root 9519938 May 10 20:14 /opt/vivaldi/resources.pak -rwxr-xr-x 1 root root 3909 May 10 20:14 /opt/vivaldi/update-ffmpeg -rwxr-xr-x 1 root root 4974 May 10 20:14 /opt/vivaldi/update-widevine -rw-r--r-- 1 root root 165519 May 10 20:14 /opt/vivaldi/v8_context_snapshot.bin -rwxr-xr-x 1 root root 3209 May 10 20:14 /opt/vivaldi/vivaldi -rw-r--r-- 1 root root 1786282 May 10 20:14 /opt/vivaldi/vivaldi_100_percent.pak -rw-r--r-- 1 root root 2379184 May 10 20:14 /opt/vivaldi/vivaldi_200_percent.pak -rwxr-xr-x 1 root root 186100488 May 10 20:14 /opt/vivaldi/vivaldi-bin -rwsr-xr-x 1 root root 240008 May 10 20:14 /opt/vivaldi/vivaldi-sandbox lrwxrwxrwx 1 root root 30 May 10 20:14 /opt/vivaldi/WidevineCdm -> /opt/google/chrome/WidevineCdm /opt/vivaldi/cron: total 16 -rwxr-xr-x 1 root root 13269 May 10 20:14 vivaldi /opt/vivaldi/lib: total 1808 -rw-r--r-- 1 root root 1850696 May 10 20:14 libffmpeg.so /opt/vivaldi/locales: total 0 /opt/vivaldi/MEIPreload: total 12 -rw-r--r-- 1 root root 228 May 10 20:14 manifest.json -rw-r--r-- 1 root root 7022 May 10 20:14 preloaded_data.pb /opt/vivaldi/resources: total 4 drwxr-xr-x 12 root root 4096 May 13 21:03 vivaldi /opt/vivaldi/swiftshader: total 2772 -rw-r--r-- 1 root root 272320 May 10 20:14 libEGL.so -rw-r--r-- 1 root root 2563936 May 10 20:14 libGLESv2.so
-
@cdn2020 Type
vivaldi
in the terminal, then post the output -
@npro I couldn't post the ouput because it was flagged as spam by someone. Not sure why
-
libGL error: Version 4 or later of flush extension not found libGL error: failed to load driver: i915
modedit correction of block-code
-
@cdn2020 Allright since we got no output yet I can tell you the following:
You don't have an Nvidia card but an integrated Intel chipset for a GPU and a system that is pretty old, around 2006-2008. The problem to me looks like it could be an AND/OR combination of many factors listed below and related to your upgrade because,
- you 've jumped from a LTS version to a non-LTS one, with all problems that could be related to such a jump. Why did you have to do that especially for such an old system? 20.04 LTS is supported 'til 2025, while 21.04 only for 8 months more, you have to upgrade again.
- for some reason you are using a software renderer,
llvmpipe
and I wouldn't know (nor you I assume) what you were using before the upgrade and it worked, or if it is a change due to the upgrade. This could be related to your problem. - you are now using "new" Wayland as your display server protocol instead of previous X11 and I don't know how that particular software renderer relates to that and Vivaldi. Wayland is a pretty new "technology" not without its own teething problems and I'm not sure if Vivaldi supports it "officially" for GNOME without the use of some extra flags anyway.
- all the above on top of a new kernel that you are on right now.
So, due to the above, you could try some switches in the wild to try to start Vivaldi, from the terminal try each time:
vivaldi --ignore-gpu-blocklist
vivaldi --use-gl=desktop
vivaldi --use-gl=swiftshader
If those don't do anything and since it affects both Vivaldi and Brave I'd suggest -as you also said you would do- to post your issue in the Ubuntu forums with all that system info attached, because a) they know better about their OS b) you would need to be advised on how to
- revert your kernel to 5.4 and see if it works (if you get a different renderer, that would be my first try)
- upgrade/install more appropriate drivers AND/OR packages related to Mesa.
- possilbly return to X11 or use XWayland.
-