https://bugs.kde.org/show_bug.cgi?id=376739
--- Comment #5 from Jan Grulich <jgrul...@redhat.com> --- With settingChanged() signal it's a bit tricky, because some connection types (e.g. wireless) asynchronously loads passwords and once those are received then we fill the UI with them which emits settingChanged() signal. For that reason I use isInitialized() to see whether secrets have been already fetched and I don't propose any change to KCM (enable apply button). -- You are receiving this mail because: You are watching all bug changes.
