Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Can't open anymore .gpg files in Nemo #511

Open
InfoLibre opened this issue Jan 13, 2024 · 13 comments
Open

Can't open anymore .gpg files in Nemo #511

InfoLibre opened this issue Jan 13, 2024 · 13 comments

Comments

@InfoLibre
Copy link

Distribution

Linux Mint 21.3 Cinnamon

Package version

6.0.2

Frequency

Always

Bug description

After upgrading to Linux Mint Cinnamon 21.3, I can’t open anymore my .gpg files in Nemo. Unencrypt menu doesn’t appear anymore after a right click on the .gpg files. Must I reconfigure something or is it a bug?

Steps to reproduce

Right click on a .gpg file.

Expected behavior

Unencrypt menu should appear.

Additional information

No response

@InfoLibre InfoLibre changed the title I can't open anymore .gpg files in Nemo Can't open anymore .gpg files in Nemo Jan 13, 2024
@leigh123linux leigh123linux transferred this issue from linuxmint/nemo Jan 13, 2024
@vajdao
Copy link

vajdao commented Jan 27, 2024

same here!

@WolfMunroe
Copy link

I'm also unable to decrypt/verify .pgp or .gpg files on the context menu of Nemo now with nemo-seahorse plug-in.
It is still possible for me to encrypt and sign files of other types via the Nemo context menu, but there's no decryption-related options on existing encrypted files.

@vajdao
Copy link

vajdao commented Feb 24, 2024

I resolved temporary fixed it on my end, by right clicking on any .pgp or .gpg file, then I went into properties, and associated it with gpg by typing 'gpg' (without quotes) in the search box at the bottom, then pressed on the "set as default" button (the middle button).

@WolfMunroe
Copy link

I used gpg in the terminal to decrypt when I ran into the problem but it is much more convenient to have gpg associated with the file type, and I've done as your instructions now.

However, that's doesn't do anything to fix the problem with nemo-seahorse not working, it's just bypassing nemo-seahorse entirely.

@vajdao
Copy link

vajdao commented Feb 25, 2024

Okay well thats interesting. So to clarify we are talking about the same issue: when I double clicked on the encrypted file, it used to pop up a little window (nemo seahorse) to input my password and decrypted it.

Then after upgrading mint to 21.3 this double clicking method stopped working and instead opened gpg/pgp file within xed with all the encrypted text in it.

Then I was like, okay lets tell nemo not to use xed, and instead use gpg. Then it was again working on double click, the seahorse window popped up to input my password. I entered my password to decrypt, and the decrypted file perfectly appeared within nemo, using GUI elements only. Nothing is bypassing nemo seahorse I dont know where do u get this from...

@WolfMunroe
Copy link

Nemo-seahorse is a plug-in for Nemo that adds Encrypt and Sign options to the Context Menu in Nemo for files that are not encrypted and adds Decrypt and Verify as Context Menu options in Nemo for encrypted files.

Seahorse is a front-end for gpg, so by associating the encrypted files with gpg as the default action, you're just bypassing the problem with nemo-seahorse plug-in by directly sending the file to gpg to decrypt.

Even when I used gpg from the terminal it popped up a separate GUI window to input my passphrase, just as it does now that I've associated the files with gpg. (I found that a little odd to be honest.) I don't know why it did it that way.

Point is though that the context menu options for nemo-seahorse plug-in are still not appearing on encrypted files.

Your ability to decrypt is resolved, it's just not resolved by nemo-seahorse being fixed.

@vajdao
Copy link

vajdao commented Feb 25, 2024

Nemo-seahorse is a plug-in for Nemo that adds Encrypt and Sign options to the Context Menu in Nemo for files that are not encrypted and adds Decrypt and Verify as Context Menu options in Nemo for encrypted files.

Yes, we know that. I don't recall seeing entries for decrypting an already encrypted file in the right-click context menu. All I remember is there were options for Encryption and Sign when I right-clicked on a non-encrypted file. I remember being surprised by this initially when I first started using this plugin. It seemed odd at first, but then I realized that double-clicking triggered the decryption process, and I accepted that.


Seahorse is a front-end for gpg, so by associating the encrypted files with gpg as the default action, you're just bypassing the problem with nemo-seahorse plug-in by directly sending the file to gpg to decrypt.
Even when I used gpg from the terminal it popped up a separate GUI window to input my passphrase, just as it does now that I've associated the files with gpg. (I found that a little odd to be honest.) I don't know why it did it that way.

I delved into the source code and discovered that Nemo-Seahorse leverages the GPGME library, an API designed to facilitate high-level interactions with GnuPG, enabling seamless integration of cryptographic functionalities into the application.

Point is though that the context menu options for nemo-seahorse plug-in are still not appearing on encrypted files.
Your ability to decrypt is resolved, it's just not resolved by nemo-seahorse being fixed.

Yeah, I understand your perspective. From a quick duct-tape fix context, until it officially gets resolved, it may not matter whether the file association or the plugin itself triggers the gpg's decryption process, as long as the encryption and signing functionalities work as intended. This could serve as a temporary solution until the issue is debugged.

However, it's important to confirm with the development team whether there was ever a "decrypt/verify" entry in the right-click menu when right-clicking on *.gpg or *.pgp files.

@InfoLibre
Copy link
Author

Yes, there was a decrypt entry in the right-click menu when right-clicking on *.gpg or *.pgp files, but there isn't anymore one since upgrading to Linux Mint Cinnamon 21.3.

@InfoLibre
Copy link
Author

InfoLibre commented Jun 15, 2024

This bug is critical! One can't anymore decrypt files with our passwords... It should be solved with high priority.

@WolfMunroe
Copy link

This bug is critical! One can't anymore decrypt files with our passwords... It should be solved with high priority.

While the Nemo extension isn't offering a decrypt option so this is still an ongoing bug, you can still decrypt your *.pgp and *.gpg files with gpg within Nemo.

You can right-click on one of the *.pgp files, go to Properties, go to Open With tab in Properties, and tell it to open with gpg. Then the default action will be to Open with gpg. gpg's default behavior on *.pgp or *.gpg is to decrypt. This is the solution that Vajdao mentioned up-thread, quoted below.

I resolved temporary fixed it on my end, by right clicking on any .pgp or .gpg file, then I went into properties, and associated it with gpg by typing 'gpg' (without quotes) in the search box at the bottom, then pressed on the "set as default" button (the middle button).

@InfoLibre
Copy link
Author

InfoLibre commented Jun 16, 2024

It's more convenient than choosing decrypt in the menu. Could someone add this default association in the next version of Nemo, or could this default association be added when installing nemo-seahorse package?

@Speretta
Copy link

Above it is said to enter gpg as default action. Instead of using gpg in the default action, you can also use nemo-seahorse-tool -d. When overwriting file, the gpg command it doesn't produce any GUI so it can't continue. This may also fix the problem a bit.

@Atalanttore
Copy link

Atalanttore commented Sep 8, 2024

After opening an encrypted *.pgp file with the pgp program in Nemo and entering the correct password, nothing happens. That is very, very bad.

Tested with Linux Mint 22.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

5 participants