summary says by itself. reproducible on Arch Linux and neon dev unstable.
Can you take a video or something? It would help understand.
Created attachment 109480 [details] demonstration ok, watch the screencast recorded on neon.
That's how it works. If you close the gtk/style window after you've done any change that dialog box will pop asking you if you want to apply the changes or discard them. Is the same all around systemsettings. Your gtk theme is downloaded but not applied unless you confirm to do so in the prompt.
(In reply to Tony from comment #3) > Your gtk theme is downloaded but not applied unless you confirm to do so in > the prompt. So we have another bug because the just installed gtk theme is not applied when I click "Apply" button. On Arch Linux at least.
Git commit 54d8e029422e30e7197fe40e35ff4c6345f6962c by Aleix Pol. Committed on 08/02/2018 at 17:29. Pushed by apol into branch 'Plasma/5.12'. Make sure there are less unnecessary changed() emissions M +64 -8 src/gtkconfigkcmodule.cpp M +1 -0 src/gtkconfigkcmodule.h https://commits.kde.org/kde-gtk-config/54d8e029422e30e7197fe40e35ff4c6345f6962c
plasma 5.12.1 changelog says that this bug is fixed, but it's still reproducible on Arch Linux.
Reproducible with plasma 5.13 on Arch Linux.
it's not necessary to install a gtk 2/3 theme. Just click "Get new themes" button, click "Download gtk2 themes" or "Download gtk3 themes", so "Get hot new stuff" (GHNS) window shows up. Close GHNS window, close system settings, so Apply/discard prompt appears.
I really cannot reproduce. On that video, the apply button is already enabled when the video starts playing, I can't see which event triggers the changed signal.
Created attachment 118554 [details] video recorded on Plasma 5.15.2 hum, really my first video is total crap. Sorry. Here is another screen recording.
That crash is something different though. It's actually 398112 which as I just fixed as of 1bdaa7db43f2645ff1e4607545048f4eb395e26d. Can you please confirm?
Hum, really the issue shown in my second video looks the same as bug 398112 just fixed by you. Probably I got confused and the original problem reported here was fixed by your commit from comment 5. Sorry. I'm closing this report as fixed. Thanks Aleix.