WetGeek It looks like Caja is only set to show up on GTK-based desktops in its .desktop file. I'm not even sure how that key works with KDE.
10/14 update
[deleted]
I think vanilla dark Adwaita looks fine. I understand that the issue is underlying incompatibilities with libadwaita etc but the theme itself is fine to me. If I could just use that all over it'd be good don't need fancy themes, as long as it looks coherent and functions.
Isn't there a way to just "use whatever GNOME is using" for theme related stuff, to eliminate theming woes going forward?
- Edited
[deleted] Well, there is the adw-gtk3 project which aims to, as much as possible, follow the libadwaita style, so you can have a unified theme for your gtk3 and gtk4/libadwaita apps.
I've been thinking about packaging that, together with Gradience, to make it easier to get a coherent experience, if you so choose.
- Edited
Can somebody check if copyq respects the dark theme, because no matter what on my system it is WHITE after the last update.
@presianbg @sangheeta could you please install this Qt6 plugin:
sudo eopkg it https://packages.getsol.us/unstable/q/qt6gtk2/qt6gtk2-0.2-1-1-x86_64.eopkg
This will resolve your theme issue with copyq and with all other qt6 apps too.
WetGeek I did give Caja a try just now. It installed just fine, but did not show up in the menu. That's happened to me before, and rebooting fixed it, but not this time. I'm curious enough to try it but not curious enough to learn how to use a menu editor to add it.
The Plasma menu editor is very very easy to use, believe me. I don't know if it would be possible to add Caja, but you can try.
joluveba The Plasma menu editor is very very easy to use, believe me
I believe you. I went through all the right motions, I'm pretty sure, but Caja didn't show up in my System sub-menu, or in the Applications sub-menu. I even rebooted, just to make sure I hadn't left out a step. I suspect that kmenueditor must limit itself to installing KDE applications. Thanks for the suggestion, though. I learned something about my favorite DE, and it was well worth a try.
rjuarezp
I have the same issue with nautilus, calculator and calendar. Very much dislike it and that themes aren't followed by apps any more is, sorry Solus (which I love), a no-go.
- Edited
SOLUSfiddler I have the same issue with nautilus, calculator and calendar.
So does just about everyone else using a DE that is tied to the Gnome stack. The changes have been coming for months and months, and have been well documented, but app developers did not adjust in a timely manner. Nothing new. Linux has experienced disruptions of this type for as long a I have been using it. It will work its way out, eventually.
tomscharbach It will work its way out, eventually.
I get what you are saying, it happens, it takes a little time to repair. especially stack stuff. I just keep thinking "a fresh install will make all this better again" but I'm just lying to myself. O Solus, if loving you is wrong I don't want to be right.
- Edited
brent Theme problems with Gnome 43, on the one hand, and Nautilis and other apps, on the other, have been reported on the web recently.
As Staudley explained, "The GNOME project keeps moving more and more apps to libadwaita theming, the latest being, among others, the file manager Nautilus. This means that it no longer respects the system GTK widget theme (as set in e.g. Budgie Desktop Settings), and also might not adjust to dark themes correctly."
While the problem surfaces in Solus DE's that are Gnome-based, as reported in this thread, the problems do not appear to be confined to Solus. That doesn't surprise me. Upstream/downstream problems are common in Linux, and take a while to resolve, given the large number of interlocking pieces and the lack of coordination between the developers of the various pieces.
It is almost inevitable that when a major upstream component changes, problems will need to ironed out downstream. No magic wand.
tomscharbach many gnome-linked web sources I'm reading are distinctly advocating for magic and/or a magic wand to be employed in this stack update, but I'm more inclined to believe your version.
- Edited
brent Many gnome-linked web sources I'm reading are distinctly advocating for magic and/or a magic wand to be employed in this stack update, but I'm more inclined to believe your version.
Gnome is forcing a change in the direction of libadwaita, and that is a given that all Gnome downstream distros and apps are going to have to work out.
It is too bad that Solus Budgie got caught in the mess, but other Budgie-based distros are also caught, as I know from other forums relating to those distros. I haven't been following BuddiesOfBudgie lately, but I expect that Budgie 11 will have adjusted one way or another. In the long run, Budge might be best served by moving away from Gnome. Along with my magic wand, my crystal ball has disappeared, so I have no idea whether that is going to happen, in whole or in part.
I've been aware of the potential issues for several months from another forum, and I was worried about how Budgie would have to change in order to make the adjustment. I involuntarily dodged the bullet because hardware changes in my Solus setup (the fractional scaling issue) forced me to move from Solus Budgie to Solus Plasma a few months ago, so I'm not directly affected.
I've seen dislocations like this happen over and over again. It is a consequence of the way in which the Linux community works -- with the exception of a small number of enterprise-focused desktops (where upstream/downstream planning is more centralized and tighter standards enforced), dislocations like this happen because upstream/downstream coordination is spotty, at best.