-
Notifications
You must be signed in to change notification settings - Fork 2.4k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Brave opening in light mode despite dark mode specified in settings #30729
Comments
I also confirm this bug in Linux. I think it is a problem of the latest version, testen on arch and mint so far. |
I also have this issue, I did report it on the reddit page, a few other people had the same problem: |
I have also experienced the GTK theme issue you described. |
Add another one to the count. Worst bug ever! :-P My system config is the same as the OP. |
Same issue here. I'm on debian bookworm. |
I'm experiencing the same issue here. I'm using Arch Linux (kernel 6.1.29) and the stable verison of Brave Browser. |
Same here on Mint 21.1 |
I am also facing this issue in Manjaro. I am using |
Same issue here on Linux Mint 21.1. |
Also affected. Arch with Cinnamon. |
I'm also having this issue. Both on flatpak and system package. Linux mint 21.1 Cinnamon |
I have the same issue with Mint 21.1, in 2 distinct machines |
yep, the same happening here (arch linux btw) Version 1.52.117 Chromium: 114.0.5735.90 (Official Build) (64-bit) EDIT: workaround found on reddit: |
The workaround seems to have worked for me, still don't know why this issue happened |
the workaround worked but i hope this gets fixed in a newer release. |
Issue still occurs on 1.52.122 (just updated the apt package) |
Just updated to 1.52.122 and still having this issue. Anybody know what has caused the issue and why they can't seem to fix it? |
On Chromium 113.0.5672.126~linuxmint1+vera I have this same issue, complete with GTK... except the workaround doesn't work |
Probably related to #14685 |
Still occurs on 1.52.126 |
Same. I thought it was a flatpak issue so i installed the regular version and it still does it. Fix it please. |
I have switched to Arco Linux and seems to be work fine on |
I have the same issue on linux mint 21. My browser version:
|
same issue here in Mint 21.1 Vera |
Just updated to 1.52.129, still happening |
Does anyone even read these messages? Seems like an internet black hole. This is an annoying bug. |
It (apparently) got fixed in some commit, but it's not coming until 1.54 |
Should I close the issue then? |
Yes, the issue was fixed with this PR |
I'm having this problem on MacOS v1.60.114. It happened all of a sudden out of nowhere. |
Description
I am using Linux Mint 21.1 "Vera" with Brave Version 1.52.117 Chromium: 114.0.5735.90 (Official Build) (64-bit)
The problem started after updating to 1.52.117 using Mint's update manager, I am using the apt package.
I have Brave set to dark mode, but every time I open the browser it opens in light mode.
The settings page, however, still shows that it is dark mode but the entire UI (including the settings page) is in light mode.
I have to manually set it to light mode and then back to dark mode for dark mode to work properly.
Steps to Reproduce
Actual result:
It shows up in light mode, despite saying it is in dark mode.
Expected result:
It should open in dark mode.
Reproduces how often:
I have managed to consistently have this issue every time I launch the browser.
Brave version (brave://version info)
1.52.117 Chromium: 114.0.5735.90 (Official Build) (64-bit)
Revision 386bc09e8f4f2e025eddae123f36f6263096ae49-refs/branch-heads/5735@{#1052}
Apt package for GNU/Linux
Version/Channel Information:
I have only experienced this on the latest apt package (1.52.117), the previous version of the apt package (1.51.118) did not have this issue.
Other Additional Information:
Does the issue resolve itself when disabling Brave Shields?
Does the issue resolve itself when disabling Brave Rewards?
No, it is not related to Shields or Rewards.
Is the issue reproducible on the latest version of Chrome?
I have not tested it on Chrome
Miscellaneous Information:
The text was updated successfully, but these errors were encountered: