Mount crash GetType:48 with macFUSE 5.3.3, not FUSE-T
メンテナーはふだん 1 日以内に返信
まだ誰も着手していません。
評価
- 難易度
- 4/5
- 見積もり時間
- 3〜5日
- 初心者へのやさしさ
- 40/100
- issue の種類
- バグ
- 明瞭さ
- おおむね明確
- 活発さ
- 静か
- 技術スタック
- c, macos
調査の方向性
Start by reviewing the macOS mount and FUSE helper paths, especially where VeraCrypt reads the auxiliary mount control file; the report identifies FilesystemPath::GetType at line 48 but names no source file or test. Compare the failing macFUSE 5.3.3 setup with the working 5.1.3 setup and inspect the attached logs and crash report. Done means mounting succeeds with macFUSE 5.3.3 without the crash.
索引モデルが issue の本文から書いたものです。
説明
[macOS] VeraCrypt crashes on mount with macFUSE 5.3.3 — "control" file missing, FilesystemPath::GetType:48
Expected behavior
After upgrading macFUSE from 5.1.3 to 5.3.3 and rebooting to approve the system extension, mounting an existing VeraCrypt volume should succeed as it did previously on 5.1.3.
Observed behavior
VeraCrypt quits unexpectedly (crash dialog with "Report…" option) during mount. The underlying error reported is:
Device not configured:
/var/folders/rs/5_xs70_17ws709gdytqhy8900000gn/T//.veracrypt_aux_mnt2/control
VeraCrypt::FilesystemPath::GetType:48
This indicates the auxiliary FUSE mount helper never created the expected control file/socket before VeraCrypt tried to read it. sudo kmutil showloaded | grep -i fuse shows nothing during a mount attempt, and a filtered log stream/log show capture across io.macfuse, com.apple.FSKit, and free-text "fuse"/"mount"/"veracrypt" predicates shows no relevant macFUSE mount activity at the time of the crash — only unrelated FSKit background events (Launch Services database changes). This suggests the kext is not engaging at all, rather than a version-mismatch handshake issue.
I'm running the macFUSE-compatible build, not the FUSE-T build. All existing issues I could find matching this exact error string (#1438 , #1667 ) are filed against the FUSE-T build, so I wanted to flag that this is happening with macFUSE proper as well, in case it's a distinct cause.
Why macFUSE rather than FUSE-T
For reference/context: I deliberately use the macFUSE build rather than FUSE-T. My reasoning is that macFUSE's maintainer (Benjamin Fleischer) has been publicly transparent about why the kernel extension component is closed-source, has stated openness to independent security review, and the project has a long, active maintenance history. FUSE-T remains closed-source with less public detail from its author, so on balance I've preferred macFUSE despite the kext's drawbacks. Given that macFUSE 5.1.0+ now offers an FSKit backend that avoids the kext entirely, I'd also be interested in using -obackend=fskit with VeraCrypt once/if that's viable — is FSKit backend support (which requires linking libfuse3 rather than the current libfuse2) something on the roadmap? Happy to help test if so.
Steps to reproduce
- Starting state: macOS 26.6 (Tahoe, build 25G72), Apple Silicon M2, VeraCrypt working normally with macFUSE 5.1.3.
- Run
brew reinstall --cask macfuseto upgrade to macFUSE 5.3.3. - Reboot and approve the system extension prompt in System Settings → Privacy & Security.
- Open VeraCrypt from Launchpad, select an existing volume, enter password, click Mount.
- VeraCrypt crashes with the error above instead of mounting.
- Reboot a second time for good measure
- Retried as 4-5, same results
Workaround: when I reinstall macFUSE 5.1.3 it works fine once again
Screenshots
Your Environment
VeraCrypt version: 1.26.24
macFUSE version: 5.3.3 (upgraded via Homebrew from 5.1.3, which worked correctly)
Operating system and version: macOS 26.6 Tahoe (build 25G72)
System type: Apple Silicon (M2), 64-bit
Attachments
- 主要言語
- C
- スター
- 11.7k
- フォーク
- 1.4k
- 平均マージ
- 1日 1時間
- マージ済み PR（30日）
- 28
環境構築
このプロジェクトには開発コンテナ、Dockerfile、コントリビューションガイドがありません。まず README を読み、一般的な手順ははじめてのコントリビューションガイドを参照してください。
はじめの一歩
- issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
- 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
- リポジトリをフォークし、ブランチを切って変更します。
- issue 番号を参照したプルリクエストを送ります。
veracrypt/VeraCrypt のほかの issue
-
bug
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 65/100
メンテナーはふだん 1 日以内に返信
-
bug
難易度 5/5 1週間以上 初心者へのやさしさ 32/100
veracrypt/VeraCrypt#1995 · コメント 1 件 · リアクション 1 件 ·
メンテナーはふだん 1 日以内に返信
-
難易度 4/5 3〜5日 初心者へのやさしさ 42/100
veracrypt/VeraCrypt#1993 · コメント 2 件 ·
メンテナーはふだん 1 日以内に返信
-
bug
難易度 3/5 1〜2日 初心者へのやさしさ 55/100
veracrypt/VeraCrypt#1991 · コメント 1 件 ·
メンテナーはふだん 1 日以内に返信
veracrypt/VeraCrypt の issue をすべて見る
似ている issue
-
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
-
bug game: 01008BA02525A000 ios
難易度 2/5 1〜3時間 初心者へのやさしさ 76/100
メンテナーはふだん 1 日以内に返信
-
area/ysql kind/bug priority/medium status/awaiting-triage
難易度 2/5 1〜3時間 初心者へのやさしさ 78/100
yugabyte/yugabyte-db#37523 ·
メンテナーはふだん 1 日以内に返信
-
難易度 2/5 1〜3時間 初心者へのやさしさ 77/100
メンテナーはふだん 3 日以内に返信
-
難易度 1/5 1時間未満 初心者へのやさしさ 65/100
ly05010419/MacNativeGames#2079 ·
メンテナーはふだん 1 日以内に返信