Skip to main content
Goofball
Aug 5, 2026 11:44 AM UTC
Solved

Recovery code creation cannot be completed on Linux Mint Debian Edition

When trying to create my 1Password recovery code in the desktop app on Linux, I cannot save or print the code and, therefore, cannot complete the process. Clicking either the “Save” or “Print” buttons simply does nothing, clicking on “Next” then leads to the attached warning and prevents me from proceeding.

Is this a known issue and is there any way to get around it?

Needless to say, I manually noted my recovery code and would be able to re-enter it in the next step.

 

I’m using 1Password for Linux 8.12.30 (81230021) on Linux Mint Debian Edition (LMDE 7 ‘gigi’, kernel 6.12.100+deb13-amd64) via the .deb package.

1P_Dave
1P_DaveAnswer
1Password Employee
Aug 12, 2026 6:39 PM UTC

Hello ​@Goofball! 👋

I’m sorry that you’re getting stuck when trying to save your recovery code on Linux. As a first step can you try the steps in this article to see if your Yama/ptrace_scope settings might be preventing the save option from working: If you see “update your settings to export data” or you can’t upload or download files in 1Password for Linux

Let me know how that goes. 

-Dave

3 replies

1P_Dave
1Password Employee
1P_DaveAnswer
1Password Employee
Aug 12, 2026 6:39 PM UTC

Hello ​@Goofball! 👋

I’m sorry that you’re getting stuck when trying to save your recovery code on Linux. As a first step can you try the steps in this article to see if your Yama/ptrace_scope settings might be preventing the save option from working: If you see “update your settings to export data” or you can’t upload or download files in 1Password for Linux

Let me know how that goes. 

-Dave

Goofball
GoofballAuthor
Aug 15, 2026 9:01 PM UTC

​@1P_Dave 
Awesome, that did indeed solve the issue.

In my case Yama was loaded but not active, so I set the value to 1, as per the article. I was then able to save the code and complete the process.

Many thanks for your assistance! 

1P_Dave
1Password Employee
1Password Employee
Aug 17, 2026 1:23 PM UTC

I’m glad that the steps in the article resolved the issue! 

-Dave