-
Notifications
You must be signed in to change notification settings - Fork 327
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
Support multiple theme directories. #1739
base: develop
Are you sure you want to change the base?
Conversation
LGTM, but I wonder whether this is really useful without using this functionality by default. Currently if something touches the configuration to set |
If ~ is filtered out anyway this can just be hardcoded to |
A reasonable value could be something that resolves into
There's a small but important difference: |
Depends on
The issue with that is that following |
Hello, what's the status of this PR? |
Waiting for my comment to be addressed mostly. What's your specific usecase for this? Might help in finding a proper default value. |
d699e00
to
decdce8
Compare
Interpret `ThemeDir` option as a comma-separated list of directories. Similar to the recent change in `SessionDir` handling, the option name is preserved for compatibility. The default list of theme directories can be modified via `-DTHEME_DIRS:STRING=a,b,c` cmake option.
decdce8
to
1bee41f
Compare
I just wanted to try out Global Themes on Fedora Kinoite (Immutable/Atomic KDE). With Fedora 40 and Plasma 6 nearing, I was wondering whether or not a fix was already done for the issue where you can't install Global Themes on Immutable/Atomic Desktops. It's not urgent as I've been comfortably using Breeze but wanted to see if there was anyone actively working on the issue. |
To add, the immutability of |
That's an issue with kcm_sddm, it cannot be addressed in sddm. |
@Vogtinator regarding Global Themes, true. The main thing is that I'd like to have a way to add sddm themes without relying on making a package and layering that package due to I'd say either Once this is done, we can then move to |
You can already do that. Just put the theme into ,
|
|
It's not You should put the theme somewhere outside of your home directory for security reasons. |
In relation to security, do themes really have the power to cause such danger while being on the user's home? Has this already been discussed here or elsewhere? |
The concern here is that the theme code is executed as the sddm user but another unprivileged user has write permissions. |
I see, thanks for the clarification |
Interpret
ThemeDir
option as a comma-separated list of directories. Similar to the recent change inSessionDir
handling, the option name is preserved for compatibility.Fixes #1561
This probably should default to
QStandardPaths::locateAll(QStandardPaths::AppDataLocation, QLatin1String("themes"), QStandardPaths::LocateDirectory);
(filtering out~/*
), but it seems a bit too much of a change when sddm is close to release.