I have reverted the changes (also for VSD 3.3). I'll set this to open again and lower priority to low because the legacy file watching seems to work on Windows. We can revisit enabling the DeviceInfoWatcher on Windows when we have time to look into the root cause of T6688.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
May 16 2024
Hopefully fixed by disabling the DeviceInfoWatcher on Windows again.
Pretty outdated, but I add it nevertheless to 2.4
s/gnupg-2.4/po/nl.po: 1320 translated messages, 625 fuzzy translations, 268 untranslated messages.
Pushed the fix: rGbb57c808b2ad: scd:openpgp: Fix PIN pin2hash_if_kdf.
Thank you. Applied by : rM87061c0260bb: gpgme.m4: Set $host correctly always.
May 15 2024
Ditto for ksba and assuan.
I don't think we need a fallback. For the group configuration we can manually look in the old location. And for everything else it's okay to lose the configuration.
Problem is that this approach doesn't work for settings that are read/written by KF, e.g. the language settings if people change the application language. I also don't particular like the Krita approach of forking everything. n the other hand, patching Qt is also suboptimal and doesn't even work for builds we don't control.
Done for gpg. Needs to be done for gpgsm.
May 14 2024
The gcrypt change works for me. Thanks!
Problem is that this approach doesn't work for settings that are read/written by KF, e.g. the language settings if people change the application language. I also don't particular like the Krita approach of forking everything. On the other hand, patching Qt is also suboptimal and doesn't even work for builds we don't control. Maybe KConfig needs a way to override the default config location retrieved from Qt.
I have a proof of concept for the second part, for reading config from ~/.gnupg/kleopatra/kleopatrarc (while still supporting the legacy ~/.config/kleopatrarc) at https://invent.kde.org/pim/kleopatra/-/merge_requests/199
I note that @DemiMarie offered a patch for this over a year ago. It doesn't appear to have had any review. If it's good, maybe apply it? If it's problematic, can we identify the problem?
Thanks, I confirm that this new commit is fixing the issue.