Not working on Fedora 42 Workstation (Gnome) Thinkpad X13 Gen1

[densi]

Hey!
Voxd seems to be exactly what I am searching for. However, I cannot get it to work. I can install it, reboot, set the hotkey. But when I exectue it in the terminal, it doesnt start the inital setup. Also no transcription in the varoius modes. Any Idea for me?

[jakovius]

Can you run 'voxd --setup' in your terminal?
Please share here the copy of the whole terminal output that it gives to you.

Also did you download the correct .rpm package for your processor? I assume on the Thinkpad you have a x86_64.

[densi]

setup:v] ydotool on PATH: /home/dennis/.local/bin/ydotool
[setup:v] ydotoold on PATH: /home/dennis/.local/bin/ydotoold
[setup:v] voxd-managed ydotoold: /home/dennis/.local/share/voxd/bin/ydotoold
active
[setup:v] packaged unit present: True
[setup:v] user unit path: /home/dennis/.config/systemd/user/ydotoold.service
● ydotoold.service - ydotool user daemon
Loaded: loaded (/usr/lib/systemd/user/ydotoold.service; enabled; preset: disabled)
Drop-In: /usr/lib/systemd/user/service.d
└─10-timeout-abort.conf
Active: active (running) since Thu 2025-10-16 11:29:12 CEST; 23h ago
Invocation: eca7f8388ef043b29801fb2cc3ea78d3
Main PID: 2960 (ydotoold)
Tasks: 1 (limit: 18573)
Memory: 340K (peak: 2M)
CPU: 25ms
CGroup: /user.slice/user-1000.slice/user@1000.service/app.slice/ydotoold.service
└─2960 /home/dennis/.local/share/voxd/bin/ydotoold --socket-path=/home/dennis/.ydotool_socket --socket-own=1000:1000

Okt 16 11:29:12 fedora systemd[2902]: Started ydotoold.service - ydotool user daemon.
[setup:v] ydotool debug (socket):
fd_daemon_socket: 3
argc: 1
argv[0]: debug
[setup:v] ydotool key test (1:0)…
[setup:v] ydotool key test: OK
gtk-update-icon-cache: No theme index file.
[setup:v] llamacpp_server_path: /home/dennis/.local/share/voxd/bin/llama-server
[setup:v] llamacpp_default_model: /home/dennis/.local/share/voxd/llamacpp_models/qwen2.5-3b-instruct-q4_k_m.gguf
[setup] Per-user setup complete.

I downloaded the right package.

[jakovius]

this check did not uncover much. looks fine.
it might be you've had issues with audio device, like some other users.

a couple of related issues have been fixed since.
could you reinstall with the newest release, and then report what you see in terminal when runningvoxd --diagnose

make sure you set up your system shortcut hotkey with the command bash -c 'voxd --trigger-record'