Bug 357746

Summary: The document could not been saved, as the selected codec is not supported.
Product: [Applications] kgpg Reporter: Emma Atkinson <emma.atkinson2>
Component: generalAssignee: Rolf Eike Beer <kde>
Status: RESOLVED FIXED    
Severity: minor    
Priority: NOR    
Version First Reported In: 2.14.0   
Target Milestone: ---   
Platform: openSUSE   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description Emma Atkinson 2016-01-09 16:29:53 UTC 
Using symmetric encryption/decryption on a file on local drive.
I opened the file which used ASCII armour format.
Decrypted the file and edited the contents using the KGpg editing screen.
I successfully encrypted using symmetric encryption and a very long pass-phrase.
When I used the Save function I get the error:
"The document could not been saved, as the selected codec is not supported."

If I use Save As and overwrite the original file I get no error message.
This looks like an unreported bug to me.

I am using 64 bit OpenSUSE 13.2 with latest package updates as of 7 Jan 2016.  
Linux (x86_64) release 3.16.7-29-desktop




Reproducible: Always

Steps to Reproduce:
1.  Create an ASCII encrypted text file (mine is about 10 KiB) on a local drive, using a long pass-phrase.  It should have a filename something like Testfile.asc   (I did not use Unicode, although I may have done so in the past at some point in the past)
2.  Open the file using the KGpg Editor's Open function.
3.  Decrypt the file using KGpg using the
4.  Change the contents using the KGpg editor
5.  Encrypt the contents using symmetric encryption and the same long pass-phrase as before.
6.  Click the Save button or use Ctrl-S or the save function from File >> Save.
7.  You should get an error message.
8.  Now try using the File >> Save As... function to overwrite the original encrypted file.
9.  You should be successful this time. 

Actual Results:  
Step 7: a dialog box containing the following message, "The document could not been saved, as the selected codec is not supported."

Step 9: no error and the encrypted contents displayed in the editor window as normal.

Expected Results:  
Step 7: a dialog box asking if I want to overwrite the original encrypted file.  Clicking yes to overwrite  should function correctly leaving the encrypted contents displayed in the editor window as normal.

I will use the Save As.. function until the problem is resolved.  So a minor severity bug.
Comment 1 Rolf Eike Beer 2016-01-09 16:36:10 UTC 
The problem is not limited to symmetric encryption, I see it every now and then but have not been able to nail it down.
Comment 2 Emma Atkinson 2016-01-18 19:24:31 UTC 
Once I have used Save As... once, the Save button works as expected. 

Here are the steps I used:
1.  I did not close the window after using the Save As... function.  
2.  I decrypted the file using the saved credentials (I was not asked to re-enter the pass-phrase).
3.  I edited the decrypted file in the editor window.
4.  I used symmetric encryption again to encrypt the text using the same pass-phrase as before.
5.  I then pressed the Save button.
6.  There was no error dialog box and the save appeared to work correctly  

This behaviour is reminiscent of a variable not being initialised.  If this diagnosis turns out to be correct, something in the Save As... function appears to gather information from the file-system or the file that fixes the problem.
Comment 3 Justin Zobel 2021-03-09 23:51:17 UTC 
Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.
Comment 4 Emma Atkinson 2021-03-10 08:47:57 UTC 
Will raise new case if I get it again.