Hacktoberfest 2026: le issue che i maintainer hanno segnato per ottobre, aperte e adatte ai principianti. Sfoglia le issue Hacktoberfest

[BUG] Windows 0.0.10: Startup at login registers python.exe instead of fluidvoice.exe

Aperta
  • Qualcosa non va?
#985 2 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
25/100
Tipo di issue
Bug
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Ambito
desktop

Direzione di ricerca

Start with the release README on the windows-main branch and inspect how the per-user FluidVoice value under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run relates to the installed fluidvoice.exe path. The issue says Windows source is not published, so there is no public implementation or regression test to work from; done would mean the startup entry launches the installed app with its correctly quoted path and that automatic launch is verified at sign-in.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

bug keep-open windows
Describe the bug

In FluidVoice for Windows 0.0.10, enabling Startup at login left a per-user Windows startup entry pointing to a bare Python interpreter instead of the installed FluidVoice executable. After restarting the PC and signing in, FluidVoice did not launch automatically.

Reproduction steps
  1. Install FluidVoice for Windows 0.0.10.
  2. Enable Startup at login in the app settings.
  3. Restart Windows and sign in to the same user account.
  4. Observe that FluidVoice does not open automatically.
  5. Inspect the FluidVoice value under HKEY_CURRENT_USER\Software\Microsoft\Windows\CurrentVersion\Run.

This describes the observed sequence on the affected installation; the setting has not been toggled again to independently reproduce the registry write.

Expected behavior

The startup entry launches the installed FluidVoice application at user sign-in, using its correctly quoted executable path.

Actual behavior

The FluidVoice registry value was:

"C:\Users\<USER>\AppData\Local\Programs\Python\Python312\python.exe"

There were no script arguments. The installed application executable, also confirmed from the running FluidVoice process, was:

"C:\Users\<USER>\AppData\Local\FluidVoice\fluidvoice.exe"

Win32_StartupCommand independently reported the same Python-only startup command. No FluidVoice scheduled task was found.

Paths above are sanitized; <USER> replaces the actual account name.

App Version

Windows 0.0.10 (confirmed from the installed application's uninstall registry metadata).

macOS Version

Not applicable — this report concerns the Windows build. Exact Windows version/build was not collected during this investigation.

Architecture

Unknown / not collected.

Workaround and verification status

Replaced only the per-user FluidVoice Run value with the quoted, existing fluidvoice.exe path. Read-back confirmed the saved value, and the executable's existence was verified.

Automatic launch at the next Windows sign-in has not yet been tested. This report does not claim that end-to-end verification has passed.

Suggested investigation

Please check how the packaged Windows build resolves the executable used for startup registration. The observed entry suggests it may be selecting a Python interpreter rather than the installed app launcher; the underlying implementation cause is not confirmed.

The public windows-main branch currently contains only a release README and says the Windows source is not published, so we cannot prepare a source-level fix or regression test. If a public contribution path becomes available, please point us to it.

This report was prepared with AI assistance from read-only diagnostics and verification of the narrowly scoped local registry workaround.

Lingua principale
Swift
Stelle
11.9k
Fork
863
Merge medio
1g 13h
PR unite (30g)
27

Preparare l'ambiente

Questo progetto non fornisce container di sviluppo, Dockerfile né guida per i contributori, quindi l'ambiente è a tuo carico: parti dal suo README e consulta la nostra guida al primo contributo per i passaggi generali.

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di altic-dev/FluidVoice

Tutte le issue di altic-dev/FluidVoice

Issue simili

Altre issue su Swift

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.