diff --git a/user/security-in-qubes/split-gpg.md b/user/security-in-qubes/split-gpg.md
index 105c43ec..a62a9d4d 100644
--- a/user/security-in-qubes/split-gpg.md
+++ b/user/security-in-qubes/split-gpg.md
@@ -57,7 +57,8 @@ This way it would be easy to spot unexpected requests to decrypt documents.
   Doing so won't provide any extra security anyway, as explained [above][intro] and [below][using Split GPG with subkeys].
   If you are generating a new key pair, or if you have a private key that already has a passphrase, you can use `gpg2 --edit-key <key_id>` then `passwd` to set an empty passphrase.
   Note that `pinentry` might show an error when you try to set an empty passphrase, but it will still make the change.
-  (See [this StackExchange answer][se-pinentry] for more information.)
+  (See [this StackExchange answer][se-pinentry] for more information.) 
+  Note: The error shows only if you **do not** have graphical pinentry installed. 
 
 ## Configuring Split GPG ##