On the master, for what it's worth: ls /usr/lib64/qt5/plugins/kmymoney/
budgetview.so checkprinting.so credittransfer_sepa_storageplugin.so csvexporter.so csvimporter.so forecastview.so gncimporter.so icalendarexporter.so kbanking.so kcm_checkprinting.so kcm_csvimporter.so kcm_forecastview.so kcm_icalendarexporter.so kcm_qif.so kcm_reportsview.so kcm_xmlstorage.so konlinetasks_sepa.so ofximporter.so onlinejoboutboxview.so payeeidentifier_iban_bic_delegates.so payeeidentifier_ibanbic_storageplugin.so payeeidentifier_nationalaccount_storageplugin.so payeeidentifier_nationalAccount_ui.so qifexporter.so qifimporter.so reconciliationreport.so reportsview.so sqlstorage.so xmlstorage.so ---- Brendan Coupe On Sat, Jul 21, 2018 at 4:09 PM, Brendan Coupe <bren...@coupeware.com> wrote: > I only have one key. > > I created a new file, saved it with encryption and when I tried to > open it I got an error that does not mention decryption. I'm on the > master right now, I'm sure if I switch back it will fail and mention > decryption in the error. > > ---- > Brendan Coupe > > > On Sat, Jul 21, 2018 at 4:04 PM, Brendan Coupe <bren...@coupeware.com> wrote: >> /usr/lib64/qt5/plugins/kmymoney/qifexporter.so >> /usr/lib64/qt5/plugins/kmymoney/xmlstorage.so >> >> ---- >> Brendan Coupe >> >> >> On Sat, Jul 21, 2018 at 3:56 PM, Jack <ostrof...@users.sourceforge.net> >> wrote: >>> I just recompiled from git master head, set encryption to be on, created a >>> new .kmy file, saved it, restarted KMM, and it opened and read the encrypted >>> file with no problem. >>> >>> Have you tried creating a new file with encryption, just in case what >>> changed is which gpg key is being used? (I only offer that since when >>> saving encrypted for the first time, it offered a number of keys I didn't >>> even realize had been created.) >>> >>> Have you also confirmed that you don't have a stray plugin or plugin >>> directory left over from an earlier install? Per Thomas' suggestion, do >>> "find /usr -name qifexporter.so" or maybe even look for xmlstorage.so. >>> >>> Jack >>> >>> >>> On 2018.07.21 17:37, Brendan Coupe wrote: >>>> >>>> I switched back to the master, found the encryption settings in the >>>> new location, turned it on and it still does not recognize my >>>> encrypted file. The error does not mention a decryption error which is >>>> does mention when I run the 5.0 branch version. >>>> >>>> Something other than the location of the encryption setting seems to >>>> have changed. >>>> >>>> ---- >>>> Brendan Coupe