I retested the cpu load with snapshot 4.2.2406.23-1:
Situation seems mostly unchanged. Only thing to note is, that after closing the last window of Vivaldi, all processes of Vivaldi are terminating after a while (in earlier days I had to manually terminate the processes as their shutdown lasted too long).
=> I can use the Calendar function for my own calendar in Google Workspace but not together with those of my co-workers - as in this case Vivaldi becomes too sluggish/unresponsive.
During my first sync of theses additional calendars my cpu load looks like this:
Ah, my fault - somehow I wasn't aware it uses GTK, but assumed it would be Qt - that's why I was surprised system menus are fine, Vivaldi not.
So the upshot then is to not use the UI scale, but instead something like
in ~/.bashrc, which seems to adjust both the dropdown menu and the tab title size (I first tried those with UI zoom still active, and got a HUGE UI that I could easily read from several meters away 😃 )
@DoctorG This would explain half the problem.
But what remains, is another instance when the desktop environment installs the same printer via USB driverless (independent of HPLIP), why both Vivaldi browsers and Chromium can't find the printer, yet Firefox and Thunderbird can. 🤔
@yandaxx I give you a counter question. Wouldn’t it be completely meaningless which browser you choose, if all had the same features and behaved in the exact same way with the exact same shortcuts? Vivaldi’s UI is different, slower but gives far more freedom than other browser. With customisation comes complexity, that’s why some things might seem a little odd.
I'd like to extend on this and inquire if the old malware protection functionality has been stripped out in favor of google's new malware database that spies on everyone...
has chromium become less secure??
(time to switch to librewolf?)
I have had exactly the same problem after using Vivaldi for less than a week. I uninstalled Vivaldi, reinstalled Vivaldi brand new, and then encountered exactly the same problem in another few days.
After hopping around in Vivaldi forums, I think I finally figured out what the problem was, and... it's kind of hilarious how simple it ends up being.
The thing about the address bar's bookmark button is that it automatically creates the new bookmark in the most recently-used bookmark folder. The problem is that attempts to do this EVEN IF YOU HAVE DELETED THE LAST BOOKMARK FOLDER YOU USED. When it can't find that recently-deleted folder, clicking the bookmark button brings up an "Added Bookmark" dialog box that looks frozen and unresponsive.
Try opening the Bookmarks page (Ctrl+B) and going to the Bookmarks Trash. Do you have a recently-deleted folder in there? If you're having the same problem as I did, you can actually expand that folder you had trashed and find ALL THE ATTEMPTED BOOKMARKS YOU HAD BEEN TRYING TO MAKE THIS WHOLE TIME. The "Added Bookmark" dialog never showed it, but all those unresponsive dialog boxes from all those bookmark-button attempts were actually sending those bookmarks straight to that trashed folder.
Therefore, the way I fixed the bookmark button was to:
Restore the Bookmark folder I had most recently deleted, so that the bookmark button can "officially" find that folder again;
use now-working bookmark button to save a new bookmark, making sure to select that new bookmark into a different folder, a common folder that I didn't plan on deleting; and
now I can safely delete the folder I had just restored, and my bookmark button is back in working order, saving to that common folder from Step 2.
(There is also the small possibility that emptying the Bookmark Trash could also work. But I'm too scared to try that. Unless a Vivaldi expert confirms that option, deffo use the previous paragraph just to be safe.)
Hoping this helped you out!
That site seems problematic. Each time i try it in Vivaldi 4.1.2369.21 / Chrome 92.0.4515.159, it drives laptop cpu for vivaldi-bin to [up to] 48%. Each time i change to any other tab, it falls back again to a more normal 1% - 10%... then back up to 40% - 48% if i return to the tab for that site. Furthermore, uBO does not even let the page load.
If i retry it in a clean profile, no extensions, but V's native Content Blocker on for ads & trackers, i see this [accompanied by laptop's roaring fan]:
Have you tried alternative Themes in V?
Have you tried alternative Themes in your Nix's DE?
@pesala OK. Thank you. Sorry about the bold type. Did not know it made it harder. Thank you for letting me know. Is 4.2 out already? I am on MX Linux so not sure when I'll be upgraded to latest version. Thought it was something I had done. Love Vivaldi browser.
@pepe2020 I have no idea why.
But it's a good theory. You could test it by creating such an entry, exporting it into a clean profile, then first recreating the issue, then deleting the suspected entry, restarting the browser, and seeing if first export of passwords work as expected without the entry.
If you can prove this is is the cause, you should update your bug report with the new information by replying to the confirmation email you got when reporting 👍
I'm having the same (I think) problem on Mac, but without different desktops/spaces. Things like closing tabs, switching tabs, etc. go to the wrong window until I click on the frontmost window. Sometimes even then it doesn't work and I have to click back and forth between windows to get it right. Is there any update on the bug?
@gabito Thanks for supporting. However, I want to ask you to remove "the problem dissapearing" part from your response because it doesn't quite solve the problem; it rather bypasses/avoids it, which is different, but the viewers might get detracted by it thinking the problem really has a solution.
@pointed-stick Fun for some, a useful source of information for others.
Check the Forum. Well-known bugs, updates and temporary workarounds are often discussed there.
In case no one has mentioned the issue you’re having on the Forum, please start a new topic. Then our Community members can either suggest solutions for a fix or confirm the bug. When others can confirm the bug, please report the bug following the instructions below.