I took the plunge and updated my desktop to Fedora 28. KMM 4 can not open my encrypted file so this appears to be a Fedora 27 vs. 28 problem.
What should I be looking for? ---- Brendan Coupe On Thu, Jul 19, 2018 at 1:55 PM, Brendan Coupe <bren...@coupeware.com> wrote: > I compiled and installed the master on my main computer without the > patch. I was able to open my encrypted file. > > I am not able to open encrypted files on my laptop which is running Fedora 28. > > I am able to open encrypted files on my desktop which is running Fedora 27. > > I switched my desktop back to the 4.8 branch. I'm thinking about > making the switch to the master but I'm worried about upgrading my > desktop to Fedora 28 and having the encryption break in KMM5. I would > prefer to figure this out before making the move to KMM5 and Fedora > 28. > > I installed KMM 5 on my laptop from the repos and it has the same > problem decrypting my KMM file. > > ---- > Brendan Coupe > > > On Thu, Jul 19, 2018 at 11:25 AM, Brendan Coupe <bren...@coupeware.com> wrote: >> Thomas, >> >> I just got around to trying the patch that you sent. I have not been >> able to get the patch to work. I run the command "git apply PatchName" >> as part of the scripts that I run to compile and install KMM. The >> scripts have worked in the past. >> >> The first time I ran it the error was: >> >> error: libkgpgfile/kgpgfile.cpp: No such file or directory >> error: libkgpgfile/kgpgfile.h: No such file or directory >> >> So I modified the patch file with the full path to the files that it >> patches. That changed the error to this: >> >> error: patch failed: kmymoney/plugins/xml/libkgpgfile/kgpgfile.cpp:33 >> error: kmymoney/plugins/xml/libkgpgfile/kgpgfile.cpp: patch does not apply >> error: patch failed: kmymoney/plugins/xml/libkgpgfile/kgpgfile.h:73 >> error: kmymoney/plugins/xml/libkgpgfile/kgpgfile.h: patch does not apply >> >> I'm not an expert but the files seem to match the patch files based on >> the line numbers so I'm not sure why it's not working. >> >> ---- >> Brendan Coupe >> >> >> On Sat, Jun 16, 2018 at 3:34 AM, Thomas Baumgart <t...@net-bembel.de> wrote: >>> Brendan, >>> >>> sorry for the delay in answering, but I just spotted this mail today. More >>> inline. >>> >>> On Mittwoch, 13. Juni 2018 19:59:05 CEST Brendan Coupe wrote: >>> >>>> I'm running KMM built from 5 master on Fedora 28. >>>> >>>> I cannot open my encrypted KMM file. It works fine on my Fedora 27 computer >>>> running KMM compiled from the 4.8 branch. >>>> >>>> When I try to open my file I get the following error message: >>>> >>>> Cannot open file as requested. Error was: Cannot read the file: >>>> /home/bcoupe/KMM/xxxxx.kmy >>> >>> >>> That is strange. My main datafile is encrypted ever since I developed the >>> encryption support and I don't see this kind of problem her on my openSUSE >>> system. >>> >>> >>>> I created a new file and encrypted it. When I try to open it I get the same >>>> error message. >>>> >>>> I then created another file without encrypting it and it opens without a >>>> problem. >>> >>> This reduces the problem to the encrypted path. >>> >>>> Both my normal KMM file and the test file can be decrypted manually (gpg >>>> -d). >>>> >>>> I just recompiled and got a more detailed error message: >>>> >>>> Cannot open file as requested. Error was: Cannot read the file: >>>> /home/bcoupe/KMM/TestKMM5.kmy >>>> /usr/local/src/kmm/kmymoney-MASTER-2018.06.13-11.36.36/kmymoney/plugins/xml/xmlstorage.cpp:141 >>> >>> Ok, it tries to open the file for reading which fails. Since it uses a >>> pointer to the object and works if it points to a regular (unencrypted) >>> file, this leaves the conclusion that it has something to do with the >>> KGPGFile object it points to. >>> >>> The last change was in that area was to remove the virtual keyword from the >>> KGPGFile::open() declaration. This should not be a problem, but one never >>> knows. >>> >>> Since you compile from source, can you apply the attached patch which will >>> add the virtual keyword again and give some more trace output for those >>> cases when KGPGFile::open() fails and report back? >>> >>> Thanks in advance. >>> >>> -- >>> >>> Regards >>> >>> Thomas Baumgart >>> >>> https://www.telegram.org/ Telegram, the better WhatsApp >>> ------------------------------------------------------------- >>> "Hey! I could use Tex!" and I've only gotten to use it a little >>> so far but it's so far superiour to MS Words "be everywhere do >>> everything"-ness it's not even funny... (lordSauron) >>> -------------------------------------------------------------
