Cannot open my encrypted folders: v2 microarchitecture support

[medmedin2014]

In the same machine, I created last year mutiple encrypted vaults via KDE Plasma Vault, but now it seems it cannot open those folders and gives the following error:

This program can only be run on AMD64 processors with v2 microarchitecture support.

gocryptfs: 2.5.3
Operating System: Manjaro Linux 
KDE Plasma Version: 6.3.4
KDE Frameworks Version: 6.12.0
Qt Version: 6.9.0
Kernel Version: 6.14.2-1-MANJARO (64-bit)
Graphics Platform: Wayland

[rfjakob]

Wow, what cpu is this? (/proc/cpuinfo)

…

On Sun, 13 Apr 2025, 00:08 Medin, ***@***.***> wrote: In the same machine, I created last year mutiple encrypted vaults via KDE Plasma Vault, but now it seems it cannot open those folders and gives the following error: This program can only be run on AMD64 processors with v2 microarchitecture support. gocryptfs: 2.5.3 Operating System: Manjaro Linux KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.9.0 Kernel Version: 6.14.2-1-MANJARO (64-bit) Graphics Platform: Wayland — Reply to this email directly, view it on GitHub <#908>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACGA7ZSVU5CKL6ZMHXEBVT2ZGFFPAVCNFSM6AAAAAB3ANVNOKVHI2DSMVQWIX3LMV43ASLTON2WKOZSHE4TANZUGQYDKNI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***> *medmedin2014* created an issue (rfjakob/gocryptfs#908) <#908> In the same machine, I created last year mutiple encrypted vaults via KDE Plasma Vault, but now it seems it cannot open those folders and gives the following error: This program can only be run on AMD64 processors with v2 microarchitecture support. gocryptfs: 2.5.3 Operating System: Manjaro Linux KDE Plasma Version: 6.3.4 KDE Frameworks Version: 6.12.0 Qt Version: 6.9.0 Kernel Version: 6.14.2-1-MANJARO (64-bit) Graphics Platform: Wayland — Reply to this email directly, view it on GitHub <#908>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AACGA7ZSVU5CKL6ZMHXEBVT2ZGFFPAVCNFSM6AAAAAB3ANVNOKVHI2DSMVQWIX3LMV43ASLTON2WKOZSHE4TANZUGQYDKNI> . You are receiving this because you are subscribed to this thread.Message ID: ***@***.***>

[rfjakob]

Caused by #828 / PR #833 / commit f5007b2

[rfjakob]

Fixed in gocryptfs v2.5.4, you can download a binary here until your distro upgrades: https://github.com/rfjakob/gocryptfs/releases/tag/v2.5.4

Sorry about that!

[medmedin2014]

OMG that was really fast, thanks really for your quick fix.

I tested the new executable version 2.5.4 and it succeded to open all my folders.

You saved me from attempting any random solution which I was afraid it will destroy my personnal scanned documents.

Really thanks.

[rfjakob]

You are welcome, but could you still post cat /proc/cpuinfo ?

[medmedin2014]

Sorry for the wait, it's an old laptop running Manjaro KDE to save some personal data and do basic writing on LibreOffice and Geogebra

cat /proc/cpuinfo                                                                                                                                                              
processor       : 0
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Pentium(R) Dual-Core CPU       T4400  @ 2.20GHz
stepping        : 10
microcode       : 0xa0b
cpu MHz         : 1911.951
cache size      : 1024 KB
physical id     : 0
siblings        : 2
core id         : 0
cpu cores       : 2
apicid          : 0
initial apicid  : 0
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm pti dtherm
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown
bogomips        : 4389.00
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

processor       : 1
vendor_id       : GenuineIntel
cpu family      : 6
model           : 23
model name      : Pentium(R) Dual-Core CPU       T4400  @ 2.20GHz
stepping        : 10
microcode       : 0xa0b
cpu MHz         : 2090.929
cache size      : 1024 KB
physical id     : 0
siblings        : 2
core id         : 1
cpu cores       : 2
apicid          : 1
initial apicid  : 1
fpu             : yes
fpu_exception   : yes
cpuid level     : 13
wp              : yes
flags           : fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ht tm pbe syscall nx lm constant_tsc arch_perfmon pebs bts rep_good nopl cpuid aperfmperf pni dtes64 monitor ds_cpl est tm2 ssse3 cx16 xtpr pdcm xsave lahf_lm pti dtherm
bugs            : cpu_meltdown spectre_v1 spectre_v2 spec_store_bypass l1tf mds swapgs itlb_multihit mmio_unknown
bogomips        : 4389.00
clflush size    : 64
cache_alignment : 64
address sizes   : 36 bits physical, 48 bits virtual
power management:

[Fierelier]

@rfjakob
x86-64-v2 was supported only 2013 and up with some weaker AMD/Intel offerings. See: https://en.wikipedia.org/wiki/X86-64#Microarchitecture_levels
I would assume that there are also some CPUs from lesser-known manufacturers, which also do not support this set to this very day. There are still X86 chips in production that do not support SSE, for example.

I also want to make it known that Core 2 Duo CPUs, especially the desktop ones, are actually still pretty comfortable to use in a lot of cases. Given the right GPU and enough RAM, even intensive tasks like YouTube work well in Firefox. On lesser chips, tasks like office and banking, as well as anything that isn't browsing overly heavy sites, still work fantastic.

I understand that the prospect of performance is attractive, but this isn't a commercial product that needs to please some investor. Said investor would have the resources to compile it specifically for their platform anyways.

I very much respect that you were willing to undo this change for medmedin2014, without them needing to show their cpuinfo first.