Try New Technology

I was getting some blocker errors when running “pamac update chirp-next” (“pamac checkupdates” didn’t show signs of issues) and then I saw “Error: sublime-text.db: sublime-text: signature from “Sublime HQ Pty Ltd support@sublimetext.com” is invalid” near the start of “sudo pacman -Syyu” was ran. A very quick search online found the fix posted on the Sublime Text forums (source linked at the bottom). Below is the fix for this when it happens for anyone:

cd /var/lib/pacman/sync && sudo rm sublime-text.db.sig

NOTE: “sudo flatpak upgrade” obviously isn’t impacted by this.

Source: Sublime-text: signature from “Sublime HQ Pty Ltd is invalid – Sublime Forum

Needing to get details and support for a Solidigm (and Intel) SSD on Manjaro Linux? Install the Solidigm Storage Tool (“…supports firmware upgrades and 4Kn sector size changes for Intel and Solidigm PCIe/NVMe/SATA NAND SSDs”):

1. Enable AUR (Arch User Repository): Add/Remove Software > (three dots/hamburger menu) > Preferences > Third Party (tab) > “Enable AUR support” and “Check for updates” > Close the Add/Remove Software
2. From CLI: pamac build solidigm-sst-storage-tool-cli

Now you have access to commands such as “sudo sst show -all -ssd” to get all the information about your Solidigm or Intel SSD.

Extras:
AUR (en) – solidigm-sst-storage-tool-cli
Solidigm Storage Tool User Guide – CLI Public – sst-cli-user-guide-public-727329-006us.pdf

I have found the snapd version of CHIRP (free, open-source tool for programming your radio) was problematic when trying to set permissions for it to access the physical interface when the radio is plugged into the computer. Further research found that this can be installed from the AUR repo’s. Below are the steps I used and at he bottom of the post will be links to the source materials I used:

1. Enable AUR (Arch User Repository): Add/Remove Software > (three dots/hamburger menu) > Preferences > Third Party (tab) > “Enable AUR support” and “Check for updates” > Close the Add/Remove Software
2. From CLI: pamac build chirp-next

Sources:
Enable Arch User Repository (AUR) in Manjaro – Linux for Devices
Chirp Radio Software – Support / Third-party Applications – Manjaro Linux Forum

For a while now (since a kernel update back when I was still on an LTS) I will randomly have apps “hang” when opening or the icon show it’s open on the taskbar while it has closed from the screen. Sometimes it happened a lot, and other times not at all. I couldn’t find any solution and all the hardware tested good.

Recently I found about out about the issue with Kernels after 6.1 experiencing stutter because of the AMD Ryzen fTPM (Bug 216989).

After turning off the fTPM in my BIOS I so far have not had any of these issues anymore!

In many causes this can be found under Security > Trusted Computing: “Security Device Support” set to Disabled will completely disable TPM. There are other options if you just want to turn of fTPM but support a hardware TPM.

Many articles will point to the issue being caused by not updating for a while; I update daily if not weekly and this has happened to me twice even with recently updating a day or two previously. My system is Manjaro KDE. The solution I have come up with is pulled together from many forum posts and lots of testing to figure out what worked.

Below are examples of the error messages I saw while running sudo pacman -Syuu:

error: libadwaita: key "06687A1D9D4FAB08B50FD92B3B94A80E50A477C7" is unknown
:: Import PGP key 06687A1D9D4FAB08B50FD92B3B94A80E50A477C7? [Y/n]
:: File /var/cache/pacman/pkg/libadwaita-1:1.3.3-1-x86_64.pkg.tar.zst is corrupted (invalid or corrupted package (PGP signature)).
Do you want to delete it? [Y/n]
...
...
error: failed to commit transaction (invalid or corrupted package (PGP signature))
Errors occurred, no packages were upgraded.


While trying different fixes I had some of the below steps missing and was getting errors like the following, but once I did everything in order they cleared up:

==> ERROR: Trust database could not be updated.
error: command failed to execute correctly

1. Terminal: kate /etc/pacman.conf
2. Edit line 45, which should read SigLevel = Required DatabaseOptional to instead read SigLevel = Optional TrustAll
3. Save
4. Terminal: sudo rm -rf /etc/pacman.d/gnupg/*
5. Terminal: sudo pacman-key --init
6. Terminal: sudo pacman-key --populate
7. Terminal: sudo pacman -Sy archlinux-keyrin
8. Terminal: sudo pacman -Syyu
9. Reboot
10. Change Line 45 of /etc/pacman.conf back to the default value (shown in Step 2)

NOTE: I tried a lot of different things before coming up with these exact steps. There is always a chance that something I did in the middle, which isn’t listed in the above steps was also part of the resolution and was omitted think it just “didn’t work.” If I run into this problem again in the future I will update this if I find anything else is needed.

This allowed me to update an individual package as well as an entire OS update.