Dark theme not works on "Files"

WetGeek

brent I have to bow out of that part of troubleshooting, apologies.

No apologies needed. I doubt this thread is going anywhere beyond this.

wingman-4

I was able to get the 3rd party palta colors themes from gnome look to respond normally.
https://www.gnome-look.org/p/1342612

WetGeek

wingman-4 I was able to get the 3rd party palta colors themes from gnome look to respond

Excellent! Did you need to log out/in in order to make that work? Perhaps @sangheeta would be happy with that theme instead of Materia-dark.

wingman-4

WetGeek

No , I installed to usr/share/themes. You have to close desktop settings if open while installing to see the newly installed themes.
Edit: I also got an older version of Materia to work that I downloaded from an Ubuntu PPA . I renamed the package Materia-Dark-Old.

WetGeek

wingman-4 I also got an older version of Materia to work that I downloaded from an Ubuntu PPA

The common attribute of these successes is that you did not get them from the recent update. That's what @sangheeta assumed was the cause of his problem. And the machine I tested on was also fully updated, including the most recent one. It does appear that the most recent version of Files has a problem. And not just with Materia-dark. As I mentioned in my original post, I tried to reproduce it with all three of the dark themes in Budgie.

wingman-4

WetGeek
I had just updated before I read this thread and was curious what would happen with older versions of the themes. Not sure what changed , but I'm not a theme developer and don't know where to begin that quest. 😅

hdansin

Could this be related to the libadwaita update thing? You can try to launch gnome-control-center from a terminal and navigate to appearance settings to enable a global dark theme. It effects gnome applications, which includes Nautilus (files).

EbonJaeger

hdansin Nautilus doesn't use libadwaita (yet. It will in GNOME 43, assuming their port is done this time), just libhandy.

I tried looking into this earlier, with the help of people on Ubuntu/UbuntuBudgie and Fedora, with no results. Nautilus uses the set GTK theme as expected on those other distros, and I can't figure out why it is stuck on Adwaita on Solus. The only relevant package that was updated this cycle that might be related (to my knowledge) is libhandy, but the other distros also have the same version, and it works there. So I'm stumped so far.

The really strange thing is that (sometimes) I can get the header bar to change themes, but not the rest of the application. I don't know how that's even possible.

palto42

hdansin Thanks, on my Solus Budgie the trick with gnome-control-center worked 🙂

xonus

hdansin Thanks, really works

brent

EbonJaeger The really strange thing is that (sometimes) I can get the header bar to change themes, but not the rest of the application. I don't know how that's even possible.

this one is a head-scratcher

WetGeek

EbonJaeger and it works there. So I'm stumped so far.

We know two things for sure ... (1) something's changed, and (2) the change happened in the last update. Maybe a diff that shows just what was changed would help?

Staudey

EbonJaeger Sorry, I completely missed this thread before. So this really only started happening after the last sync? In that case I guess we can just roll back libhandy. It's not like the update contained any terribly important changes (IMO). The funny thing is that it even had a changelog item that suggested it would improve the handling of dark themes.

AdwStyleManager: Make color-scheme work with GTK themes ending in -dark

AlucardNoir2

Staudey I had some trouble after the previous update as well. Part was on my end but the other part seems to coincide with the dark theme problems in this thread. At the recommendation of another forum user - hdansin - I was able to solve the problem by launching the gnome-control-center via terminal and changing the theme from the appearance settings. The problem might be on the Budgie end.

EbonJaeger

Staudey the thing is the problem only appears on Solus. So it would be nice in the long run to figure out why.

WetGeek

AlucardNoir2 problem by launching the gnome-control-center via terminal and changing the theme from the appearance settings

That may not work universally. I tried doing that after it was mentioned here, but the process hung up, and it required a Ctrl+C to continue. Nothing about the theme changed for me, and the experience was the same on a VM and on a Budgie desktop machine.

@Staudey , good luck with rolling that back. Please let us know when and how to implement it after the roll-back.

WetGeek

This is now fixed in the very small update that I just installed. Thanks again, @Staudey.

brent

EbonJaeger This still doesn't work for me**. I auditioned a lot of new themes after this update last night.

This is current^^. I just did this. You ready for the weird part? See my asterisks above? You can see by the picture Dark in Nautilus does not work but******it does eventually. Maybe 10 minutes? 15 minutes? Something somewhere in the code thinks its way thru to self-repair.
I know this sounds insane but I saw it in one hour of auditioning themes last night. The old login/logout was ineffective. Leaving it the he## alone has been effective.
To quote my favorite pundit: "I hate the weird ones."
Oh yes, this is now: Qogir-dark is the only one that sticks:

Qogir changes right away. The other dark themes to do not.
How bizarre how bizzare

xonus

of course thanks all who finds patterns and solutions to the problem 🙃

WetGeek

brent This still doesn't work for me

I'm both amazed and embarrassed. When I installed the small update and concluded that this had been fixed, it was at 2-something AM, and I now realize I was barely awake at the time. I updated my laptop and fired up Nautilus, and everything looked just fine..

What I neglected to consider is that my laptop DE is Plasma. It's always worked fine. If I misled anyone this morning, my apologies. I just checked again on a Budgie machine, and it's clearly working as it did before the update:

brent

WetGeek you didn't mislead anyone. the update clearly worked for some.

« Previous Page Next Page »