Vivaldi browser doesn't start after 4/10/24 update

I run tumbleweed libvirt vm in leap 15.5 host. After today’s tumbleweed update (500+ packages), vivaldi does not start in mate desktop. It gives error below. Ir ran for months before updates. On the same vm, vivaldi does start in kde plasma desktop. Main upgrade was to mate new 1.28 version. For reference, firefox continues to run in the new mate desktop on this vm.

So I thought problem was the new 1.28 mate. BUT, in my arch linux vm, with mate 1.28, vivaldi runs fine. So now I think issue is with tumbleweed. Any ideas?

(base) tom@localhost:~> vivaldi
libva error: /usr/lib64/dri/virtio_gpu_drv_video.so init failed
[2328:2328:0410/151822.032295:ERROR:viz_main_impl.cc(196)] Exiting GPU process due to errors during initialization
[2285:2365:0410/151822.122170:ERROR:login_database.cc(1046)] Password decryption failed, encryption_result is 2
[2285:2285:0410/151822.258235:ERROR:browser_main_loop.cc(278)] GLib-GObject: cannot register existing type 'GtkWidget'
[2285:2285:0410/151822.258288:ERROR:browser_main_loop.cc(278)] GLib-GObject: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
[2285:2285:0410/151822.258310:ERROR:browser_main_loop.cc(278)] GLib-GObject: cannot register existing type 'GtkBuildable'
[2285:2285:0410/151822.258320:ERROR:browser_main_loop.cc(278)] GLib-GObject: g_type_interface_add_prerequisite: assertion 'G_TYPE_IS_INTERFACE (interface_type)' failed
[2285:2285:0410/151822.258328:ERROR:browser_main_loop.cc(278)] GLib: g_once_init_leave_pointer: assertion 'result != 0' failed
[2285:2285:0410/151822.258334:ERROR:browser_main_loop.cc(278)] GLib-GObject: g_type_add_interface_static: assertion 'G_TYPE_IS_INSTANTIATABLE (instance_type)' failed
[2285:2285:0410/151822.258341:ERROR:browser_main_loop.cc(278)] GLib-GObject: g_type_register_static: assertion 'parent_type > 0' failed

I found that deleting the vivaldi directory in ~/.cache and restarting (creating a new config) allowed vivaldi to start. No idea how vivaldi cache got affected by updates.

Looks like problem is solved until it happens again. No real solution.

tom kosvic

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.