Home → Stable →

GPG Keychain: GPG_Suite-2019.2.dmg vs. GPG_Suite-2019.2.dmç

• Edit

Mokanneling

10 May, 2020 02:12 AM

Perhaps this report about the resolution of an apparently uncommon GPG Keychain installation issue might help other users who might encounter a similar or identical issue.

Platform:
Tor Browser 9.0.10
macOS Catalina Version 10.15.4
GPG Keychain > About GPG Keychain > GPG Keychain Version 1.5 (1577)

An unknown issue prevented the installation of GPG_Suite-2019.2.dmg > GPG Keychain Version 1.5.1 (1587).

Perhaps the issue stemmed in part from the difference in the spellings between the two filename extensions ".dmg" (sic) vs. ".dmç" (sic).

GPG_Suite-2019.2.dmg
vs.
GPG_Suite-2019.2.dmç

After attempting to install GPG Keychain 1.5.1 from the downloaded disk image "GPG_Suite-2019.2.dmg", the following Warning dialogue appeared:

Warning
The following disk images couldn't be opened
Image: GPG_Suite-2019.2dmç
Reason: Resource busy

In the Warning dialogue, the spelling of the filename extension, ".dmç" failed to match the spelling of the filename extension ".dmg" in the disk image "GPG_Suite-2019.2.dmg" downloaded from https://releases.gpgtools.org/GPG_Suite-2019.2.dmg

The issue was resolved by selecting Tor Browser > "i" information > New Circuit for this Site (I changed the Tor circuit 4 or 5 times) and again downloading the GPG_Suite-2019.2.dmg file. This second download of this file autosaved as GPG_Suite-2019.2(1).dmg

I deleted the first download, GPG_Suite-2019.2.dmg, and edited the name of the second download from GPG_Suite-2019.2(1).dmg to GPG_Suite-2019.2.dmg

Again, I downloaded the GPG_Suite-2019.2.dmg.sig file. This second download of this file autosaved as GPG_Suite-2019.2.dmg(1).sig

I deleted the first download of GPG_Suite-2019.2.dmg.sig and edited the name of the second download from GPG_Suite-2019.2.dmg(1).sig to GPG_Suite-2019.2.dmg.sig

The .sig file successfully verified the GPG Signature, and, after opening the saved (second download) .dmg file, no Warning dialogue appeared—the installation was successful for GPG Keychain Version 1.5.1.

Expected
I expected that the GPG_Suite-2019.2.dmg file successfully would install GPG Keychain 1.5.1, but I was surprised by the uncommon Warning dialogue:

Warning
The following disk images couldn't be opened
Image: GPG_Suite-2019.2dmç
Reason: Resource busy

macOS                   10.15.4     19E287
GPG Suite               2019.2      2670    (ac945f92b0)
GPG Mail                4.0         1515    (597c8f5250)    30 trial days remaining
GPG Keychain            1.5.1       1587    (967419866a)
GPG Services            1.12.1      1100    (2d6c8340f0)
MacGPG                  2.2.17      940     (4ba83bbeda)
GPG Suite Preferences   2.2.1       1136    (378dbebf37)
Libmacgpg               1.0.1       924     (ed76f66a8a)
pinentry                1.1.0.2     16      (9b8e20e2c0)

1. Support Staff 1 Posted by Steve on 11 May, 2020 02:44 PM

   

   HI Mokanneling,

   thanks for your report. Can you share where you downloaded GPG_Suite-2019.2.dmç from? I do not think such a file could be coming from our servers.

   Best,
   Steve

   • Edit

2. 2 Posted by Mokanneling on 11 May, 2020 11:59 PM

   

   Hi Steve,

   I did not download any content with the filename GPG_Suite-2019.2.dmç

   I never have downloaded a file with the filename GPG_Suite-2019.2dmç

   I have downloaded GPG_Suite-2019.2.dmg and GPG-Suite-2019.2.dmg.sig only from the site: https://gpgtools.org/

   I never have downloaded GPG Suite from any site other than https://gpgtools.org/

   In the first instance of downloading GPG_Suite-2019.2.dmg, each time I clicked on it, the Warning dialogue appeared, which prevented the installation of GPG Keychain 1.5.1.

   In the second instance of downloading GPG_Suite-2019.2.dmg file, no Warning dialog appeared and GPG Keychain 1.5.1 installed successfully.

   Best regards,
   Mokanneling

   ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

   • Edit

3. Support Staff 3 Posted by Steve on 13 May, 2020 07:06 PM

   

   Oh ok, then that was just a typo in your initial report.

   Maybe this was just a download glitch. If you are able to find a way to reproduce the initial error, please do let us know.

   Are you otherwise now setup and running?

   Best,
   Steve

   • Edit

4. 4 Posted by Mokanneling on 20 May, 2020 10:52 PM

   

   Hello Steve,

   I am setup and running with no issues.

   I apologize for any confusion in my initial report.

   I recognize the difference between the character "g" and the character "ç".

   In the first instance, I downloaded "GPG_Suite-2019.2.dmg". In this downloaded file, the last character appearing in the filename is the character "g". The last character in the filename ""GPG_Suite-2019.2.dmg" IS NOT the character "ç".

   In the second instance, I downloaded "GPG_Suite-2019.2.dmg". In this downloaded file, the last character appearing in the filename is the character "g". The last character in the filename IS NOT the character "ç".

   Both downloads had exactly identical filenames: "GPG_Suite-2019.2.dmg"

   When I clicked on the file "GPG_Suite-2019.2.dmg" that I had downloaded in the first instance, the following exact Warning dialogue appeared in a dialog box on my computer screen:

   ***********************************
   Warning
   The following disk images couldn't be opened
   Image: GPG_Suite-2019.2.dmç
   Reason: Resource busy
   ***********************************

   In my precise description of the spelling of each character in the Warning dialogue, the spelling exactly mirrors the spelling of all text that appeared inside the Warning dialogue itself.

   In the Warning dialogue itself, the exact filename spelling appeared as "GPG_Suite-2019.2.dmç".

   In the Warning dialogue itself, the last exact character in the filename "GPG_Suite-2019.2.dmç" was the specific character "ç".

   The last character in the filename "GPG_Suite-2019.2.dmç" appearing in the Warning dialogue WAS NOT the character "g".

   I do not know why the Warning dialog spelled the filename as "GPG_Suite-2019.2.dmç".

   The Warning dialogue appeared only when I clicked on the file "GPG_Suite-2019.2.dmg" that I had downloaded in the first instance. This downloaded "GPG_Suite-2019.2.dmg" file could not and would not install GPG Suite, and the Warning dialogue automatically and instantly appeared each time I clicked on the "GPG_Suite-2019.2.dmg"file. Each time I clicked on the file "GPG_Suite-2019.2.dmg" to install GPG Suite, the Warning dialogue automatically and instantly appeared, with the filename appearing in the Warning dialogue spelled exactly as "GPG_Suite-2019.2.dmç". Each time the Warning dialog appeared, I closed the Warning dialog window and again clicked the file "GPG_Suite-2019.2.dmg". Each time I clicked the file "GPG_Suite-2019.2.dmg", the same Warning dialogue appeared, and, each time, the exact filename spelling in the Warning dialogue box was "GPG_Suite-2019.2.dmç".

   On the other hand, when I clicked on the filename "GPG_Suite-2019.2.dmg" that I had downloaded in the second instance, no Warning dialogue appeared, and GPG Suite installed without issue.

   I do not know why the Warning dialogue appeared when I attempted to install the "GPG_Suite-2019.2.dmg" file that I had downloaded in the first instance.

   I do not know why the Warning dialogue displayed the exact filename spelling "GPG_Suite-2019.2.dmç".

   Best regards,
   Mokanneling

   ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

   • Edit

5. Support Staff 5 Posted by Steve on 25 May, 2020 12:24 PM

   

   Hi Mokanneling,

   thanks for the detailed update on this situation.

   While that may not be a satisfactory explanation, this feels as if the first download may have been corrupted.

   If you want you can share the problematic dmg file and we will take a closer look.

   All the best,
   Steve

   • Edit

6. 6 Posted by Mokanneling on 27 May, 2020 02:51 AM

   

   Hello Steve,

   I would share it with you, but I already deleted the first instance of GPG_Suite-2019.2.dmg. If it ever happens again, I will save the file and forward it to you.
   Thanks for everything,
   Mokanneling

   Sent from ProtonMail, Swiss-based encrypted email.

   ‐‐‐‐‐‐‐ Original Message ‐‐‐‐‐‐‐

   • Edit

7. Support Staff 7 Posted by Steve on 28 May, 2020 03:58 PM

   

   No problem.

   Glad this is solved for you. I'm closing this discussion. Should you need further assistance or have questions you can re-open this discussion here or open a new one any time.

   Best,
   Steve

   • Edit

8. Steve closed this discussion on 28 May, 2020 03:58 PM.