Repository navigation
Conversation
`voxtype status --extended` runs nvidia-smi at startup, which loads the NVIDIA driver and wakes the dGPU on hybrid laptops. The bar only reads alt/class. Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
Independent community review
Tested: Result: The fix operates as intended without regressions:
Testing details
|
|
Triage (not posted): LGTM.
|
|
Reviewed at 9a54c8f, nothing found to change. Reproduced on a worker (Omarchy ISO VM, the packaged Tests on the worker: Second opinion: Codex Medium reviewed the diff and the repository for other consumers of the extended fields and other Related: #8734 rewrites the same comment block in this file (and keeps Waiting on the maintainer. This is labelled |
|
Re-checked because this no longer merges into c248890 (#14552, "Add selectable Voxtype and Superwhisper dictation") deleted Checked by reading Waiting on the maintainer, with the recommendation that this be closed as fixed by #14552. Thanks for the careful diagnosis, Alex — the root-cause write-up here was precise. |
Keep the status helper deleted by omacom#14552. Upstream removed its bar consumer and the GPU-probing path, so the original fix is superseded.
Problem
On hybrid laptops with the dGPU off, the bar's dictation indicator wakes the NVIDIA GPU and loads the NVIDIA driver every time the bar is built: at login, on shell restart, and on every resume. It runs twice each time, because
Indicators.qmlcreatesDictationfor both the horizontal and the vertical bar.On an ASUS G14 (GA403WR) with supergfxd in Integrated mode, the NVIDIA driver deadlocked during supergfxd's post-resume teardown. The next suspend then hung and froze the laptop.
Root cause
bin/omarchy-voxtype-statusrunsvoxtype status --follow --extended --format json. With--extended, voxtype 1.1.0 runsnvidia-smi --query-gpu=name --format=csv,noheaderonce at process start (detect_nvidia_gpu, reached viaExtendedStatusInfo::from_config->inventory()).The real
nvidia-smigoes through libnvidia-ml, which runs the setuidnvidia-modprobe. That loadsnvidia.koby name, so supergfxd'sblacklist nvidiadoesn't stop it. The load wakes the dGPU.Nothing uses the extended fields.
Dictation.qmlonly readsdata.alt || data.classand builds its own tooltip.omarchy-voxtype-statusis only called fromDictation.qml, so there are no other consumers.The flag came in with the original voxtype commit (0d42f1b). Its message doesn't say why. My assumption, not confirmed by the history, is that it was for the Waybar tooltip:
--extendedaddsModel:,Device:andBackend:lines to thetooltipfield, and Waybar displayed that field. Waybar has since been removed, and the shell'sDictation.qmldoesn't readtooltip, so nothing visible is lost.Fix
Drop
--extendedfrom thevoxtype statuscall, with a comment saying why.altandclassare still emitted. No migration is needed: this is a shippedbin/script that the bar re-executes on its next start, and there is no user state to repair.Testing
Ran with a logging fake
nvidia-smifirst onPATH, so the real binary was never touched:omarchy-voxtype-status(4s): 0nvidia-smicalls. Output was{"text": "", "alt": "idle", "class": "idle", "tooltip": "Voxtype ready - hold hotkey to record"}.voxtype status --follow --extended --format json(4s): 1 call,nvidia-smi --query-gpu=name --format=csv,noheader.The full test suites are left to CI. In a local run of
./test/clibefore that decision, the only failure wasvscode generated theme references current theme file, which is unrelated to this change.🤖 Generated with Claude Code