Vivaldi no longer usable on Linux Mint
-
I'm posting this from Firefox as the latest Vivaldi update has rendered it unusable on my Linux Mint installation. After a few minutes of loading sites and switching tabs, the UI for the most part stops working - toolbar buttons don't respond, pages won't load and the only resource is to kill the vivalvdi process. When I restart it, the same thing happens. I can switch tabs, and any that had loaded appear, but won't reload, scroll, respond to clicks or even close. The Vivaldi menu doesn't appear when clicked.
There are no crash logs to submit, not sure what else I can provide.
Really disappointing, but Vivaldi is now useless for me.
-
@knightlie Please check Troubleshooting issues.
-
I'm using Linux Mint and have no issues. So there must be some issue specific to your setup.
Are you able to run a clean profile?
-
For me in the past freezes could happen with problem of GPU mesa drivers and wayland, same with Chromium; coudl never solve it.
-
Yep. Same here. Previous versions of Vivaldi were fabulous but since early December they inevitably hang. Am running Linux Mint 21.2
-
Vivaldi seems to have a problem with the Wayland environment (status experimentally in Linux Mint and LMDE 6) . I can't even install Vivaldi on Wayland, but only in the standard environment (X11).
-
That's why I avoid using Wayland up to now.
-
I use X11 because i have trouble with my other Virtualbox guests when other virtual Linuxes run Wayland.
My experiences: Vivaldi on Mint with Wayland and its drivers is broken, on Ubuntu 22 or 23 it works with Wayland.
-
There are pros and cons to using Wayland. Although I have no issues using Wayland with Vivaldi on openSUSE Tumbleweed and openSUSE Slowroll, I prefer to use X11.
-
In Linux Mint forum there is a thread about Wayland written by power user xenopeek. Also with a link to github page with known issues.
He wrote:Wayland support is experimental. It is in alpha stage. That means you should expect lots of parts to not work.
-
I hit the same (or similar) on Debian Bookworm. I solved it quite by accident by installing a newer (backported) kernel. Gory details are at https://lists.debian.org/debian-user/2024/01/msg00527.html and in particular the reply marked SOLVED.
-
@ccurley Good to read that you solved your issue.
The 6.5 kernel reached EOL (end of life) back in November. I'm not sure how long Debian or the packager may make that available for its users.
6.1 and 6.6 are the current long-term support kernels.
