Vivaldi has stopped respecting theme preference

DoctorG

@yairmohr Which Mint with Cinnamon is this?

yairmohr

@DoctorG That's not "older" mint. I'm running the latest stable release (Mint 21.2, Cinnamon 5.8.4, Linux Kernel 6.2 which is WAY newer than the one Mint is officially on). And how the heck is such a major bug not fixed for over 13 months??

DoctorG

@yairmohr said in Vivaldi has stopped respecting theme preference:

And how the heck is such a major bug not fixed for over 13 months??

Chromium dev team does not tale it serious enough.

@yairmohr said in Vivaldi has stopped respecting theme preference:

Mint 21.2, Cinnamon 5.8.4, Linux Kernel 6.2

I will try in a few hours to test in.

yairmohr

@DoctorG Thank you for all your help anyway. It's so frustrating such a bug can even happen 2 weeks before 2024, when EVERYTHING's about dark mode hehe.

DoctorG

@yairmohr said in Vivaldi has stopped respecting theme preference:

It's so frustrating such a bug can even happen

Yes, something is strange, but i had this with Debian 11 some month ago and after a Linux upgrade all was nice in Debian 12. Chrome and Vivaldi had same troubles.

yairmohr

@DoctorG I think the strangest part for me is up until the 6.5 update, I didn't have this problem at all. How can a newer version be worse than all the previous ones?

DoctorG

@DoctorG said in Vivaldi has stopped respecting theme preference:

@yairmohr said in Vivaldi has stopped respecting theme preference:

Mint 21.2, Cinnamon 5.8.4, Linux Kernel 6.2

I will try in a few hours to test in.

Mint 21 freezes at boot with my hardware. Can not test. Sorry.

//EDIT:
Please, wait until a Mint 21 user comes and can test more.

DoctorG

@yairmohr In which Vivaldi version did it work before?

yairmohr

@DoctorG Every single one since I moved to Linux in May, until this morning.

DoctorG

@yairmohr Stable 6.4.3160.47 had Chromium 118 core, this 6.5.3206.39 has 120.0.6099.121.
Perhaps a new bug in Chromium core was causing this in Vivaldi or some libraries of Mint.

Just for a test, is the issue existing in Chromium 120 (not a Flatpak version!) and Chrome 120 on Mint after you had enabled GTK in chrome://settings?
Only if you like and you have time for tests.
I always have Chromium and Chrome installed on my Debian to check while testing if it is a Vivaldi-only of Chrome/Chromium issue.

yairmohr

@DoctorG I checked Chromium 120 with GTK theme enabled and it's the same - the browser itself follows the dark theme, but websites don't. I'm not even going to install Chrome to test it - the whole idea with moving to Linux for me was to stop M&A's spyware collecting my data.

(Just to make it clear: M&A = Microsoft and Alphabet)

DoctorG

@yairmohr Ah, same on Cbhromium; then it is a issue with interaction of Chromium core and Mint 21 libraries.
You should write a bugreport for Chromium to Mint 21 developers.

//EDIT: Strange, that it works for me on Debian 12 & ubuntu 22 LTS GNOME & Ubuntu 23 GNOME

edwardp

@yairmohr said in Vivaldi has stopped respecting theme preference:

@DoctorG I checked Chromium 120 with GTK theme enabled and it's the same - the browser itself follows the dark theme, but websites don't. I'm not even going to install Chrome to test it - the whole idea with moving to Linux for me was to stop M&A's spyware collecting my data.

(Just to make it clear: M&A = Microsoft and Alphabet)

See this post. Perhaps it's what you are looking for.

yairmohr

@edwardp Thank you, but despite using 6.5.3206, which should be counted as "6.5 final" which was mentioned on that thread, I don't have that setting at all.

DoctorG

@yairmohr That Setting is in the current 6.5 Snapshot.

yairmohr

@DoctorG I understand "snapshots" are Vivaldi's equivalent of developer builds. I can't try it, since I don't want to install it on my system instead of the steady build, and they have no way of running it separately (AppImage or just ".tar.gz" that you can uncompress and run as a "portable app").

DoctorG

@yairmohr Yes, it is a tester build, but it can not harm your Vivaldi Stable version as it get a separate configuration folder and installation folder.
But i understand that you only want Stable (final version) on your PC.

Ruarí

@yairmohr said in Vivaldi has stopped respecting theme preference:

I understand "snapshots" are Vivaldi's equivalent of developer builds. I can't try it, since I don't want to install it on my system instead of the steady build, and they have no way of running it separately (AppImage or just ".tar.gz" that you can uncompress and run as a "portable app").

If you want something else and your distro does not repackage, you can use try these at a pinch.

FWIW you can also test snapshot builds by way of the install-vivaldi.sh script linked from the snapshot posts. This offers a bunch of options:

$ install-vivaldi.sh --help

Usage:

    install-vivaldi.sh [OPTIONS(S)]

If no options are provided, then the script will install the most recent
Vivaldi snapshot for the detected system architecture (x86_64). It will
install, system-wide into "/usr/local/share" if possible, otherwise it will
default to "~/.local/share".

This script handles the fetching of a Vivaldi install file for repackaging but
will use a local copy, if it is already present in the working directory.


Options:

  -h, --help                          (Show this help text and exit)

  -t, --test                          (Test run Vivaldi with a clean profile
                                      before install. You will be asked if you
                                      want to proceed with the install
                                      NOTE: Does not work when run as root)

  -u, --uninstall                     (Uninstall the previous version)


Advanced Options:

  -a, --architecture [ARCHITECTURE]   (Use the supplied architecture instead
                                      of the one detected)

  -d, --directory [DIRECTORY]         (Install to the supplied directory. An
                                      "absolute" path must be given)

  -f, --final                         (Install the latest final instead)

  --insecure                          (Do not check package signature)

  -nl, --no-launch                    (Do not attempt to automatically Launch
                                      Vivaldi after first install)

  -r, --retrieve                      (Fetch package but do not install it)

  -v, --version [VERSION]             (Install the user supplied version
                                      number, rather than the latest detected
                                      in the APT repository)